[NO-JIRA] Update the address validation assignment (#67)

AddressValidation.md

@@ -3,13 +3,13 @@
 # Paidy's Take-Home Technical Product Manager Exercise: Address validation engine
 
 ## What to expect?
-As a next step of our interview process, we’d like you to prepare a technical challenge that is aimed to check your abilities in regards to business and system analysis, as well as utilizing available technical documentation to define a scope of a feature and prioritize its implementation. This assignment should also be a good opportunity for you to experience and see the type of work you’ll be asked to complete in this role at Paidy!
+As the next step in our interview process, we’d like you to complete a technical challenge designed to assess your abilities in business and system analysis, and your proficiency in using technical documentation to define the scope of a feature and prioritize its implementation. This assignment is also an opportunity for you to experience the type of work you'll be doing at Paidy as a Technical Product Manager.
 
-Take time to get familiar with it and submit your answers once you’ve completed it. In the next interview, you will be asked to present your proposal and the session will be used as a practice for grooming the feature.
+Once finished, please submit your answers, and in the next interview, you’ll present your proposal. This session will simulate a project kick-off meeting where you’ll onboard senior management, other technical product managers, engineers, and analysts into the project. You will walk them through your assumptions, decisions, and the requirements you’ve outlined, just as you would in a real-world project setting.
 
-Please be mindful that there is not really a right or wrong answer as long as you can justify your choices and reasoning. Please make as many assumptions and hypotheses as you need and/or see fit to complete the assignment. Please don’t hesitate to reach out to us if you have any questions or if anything is unclear regarding the assignment.
+There isn’t a right or wrong answer—what matters most is your reasoning and ability to justify your decisions. Feel free to make any assumptions and hypotheses that you believe are necessary to complete the assignment. If anything is unclear or you have any questions, don't hesitate to reach out.
 
-We appreciate your efforts and hope you’ll have fun doing this homework assignment! :) 
+We appreciate your time and effort and hope you enjoy working through this challenge!
 
 ## What we are looking for?
 **Keep it simple**. Read the requirements and restrictions carefully and focus on solving the problem.
@@ -20,27 +20,40 @@ We appreciate your efforts and hope you’ll have fun doing this homework assign
 Please include all the work requested under the [guidance section](./AddressValidation.md#guidance) in a PDF file and email it to the Paidy talent acquisition team.
 
 ## The Follow-Up Interview
-During the follow-up interview, you'll have the opportunity to meet more members of our team. You'll be asked to present your submission and the requirements that you wrote in the style of a project kick off meeting. We would like to hear about the decisions you made, explain the reasoning behind them, and review the requirements and the scope that you outlined.
 
-## Requirements: Address validation engine
+In the follow-up interview, you’ll meet additional members of our team and present your submission as if you were conducting a project kick-off meeting. This will simulate a real-world scenario where you’ll onboard senior management, other technical product managers, engineers, and analysts into the project. You will walk them through the assumptions, decisions, and requirements you’ve outlined, giving them a clear understanding of your approach.
+
+We’d like to hear about:
+- The decisions you made and why you made them
+- An explanation of the requirements you wrote
+- How you balanced business needs with technical constraints
+- Any assumptions or trade-offs you made throughout the process
+
+We’ll treat this interview as a collaborative session, similar to a project meeting where you’d gather input from key stakeholders. Be prepared to answer questions, justify your choices, and potentially adapt your solution based on feedback. This will give us insight into how you manage discussions and adjust plans in a dynamic team environment.
+
+## Requirements: Address Validation Engine
+
 ### Context
 
-When a consumer makes a transaction at a merchant using Paidy, we receive via API some key information about the transaction. One of these key information is the shipping address entered by the consumer on the checkout page of the merchant. Address validity is a key topic not only for marketing and logistics reasons but also for fraud. For fraudsters, a mailing address offers a lot of payment fraud and account take over opportunities. 
+When a consumer makes a transaction at a merchant using Paidy, we receive key information about the transaction via API, including the shipping address entered on the merchant’s checkout page. Ensuring the validity of this address is critical—not only for marketing and logistics but also to combat fraud. Fraudsters often exploit mailing addresses for payment fraud and account takeover opportunities.
 
-Imagine you’re a Risk TPM at Paidy trying to implement an address verification system to catch fraudulent transactions before they cause significant harm to Paidy’s business. How would you go about designing and implementing such a system at Paidy using a third party address validation vendor?
+As a Risk Technical Product Manager (TPM) at Paidy, your task is to design and implement an address validation system that can catch fraudulent transactions before they harm Paidy’s business. You will be using a third-party address validation vendor to accomplish this.
 
-_Notes: the shipping address is entered on the merchant website and is communicated to Paidy via API [checkout documentation here](https://paidy.com/docs/api/en/#1-introduction). Assume that we cannot change the UI of the merchant website to prompt the consumer to correct the address. The shipping address is communicated as it was shared with the merchant so we are only thinking about implementing further checks once Paidy receives the payment information._
+_Notes: The shipping address is entered on the merchant’s website and is communicated to Paidy via API [check the documentation here](https://paidy.com/docs/api/en/#1-introduction). Assume that we cannot change the UI of the merchant website to prompt the consumer to correct the address. Therefore, we will only implement further checks once Paidy receives the payment information._
 
 ### Guidance
 
-* Please look at the below list of possible vendors to integrate with. Look at them and select one vendor you would like to integrate with and explain your thought process about why you selected that vendor.
-  * https://www.smarty.com/products/international-address-verification
-  * https://www.egon.com/
-  * https://developers.google.com/maps/documentation/address-validation/requests-validate-address
-  * https://www.postgrid.com/address-verification/
-* What KPIs would you use to measure the performance of your new system?
-* Write the Request for Comments document with the requirements for this feature and break it down in actionable small steps
-* In the next session, you will be asked to present the feature and scope proposal to Engineering lead and other product managers in a grooming session. Prepare how you want to present and communicate the user stories in this grooming session [You can choose whatever format you want]
+1. **Vendor Selection**: Review the following list of potential vendors for integration. Select one vendor you would like to integrate with and explain your reasoning for this choice.
+   - [Smarty](https://www.smarty.com/products/international-address-verification)
+   - [Egon](https://www.egon.com/)
+   - [Google Maps](https://developers.google.com/maps/documentation/address-validation/requests-validate-address)
+   - [Postgrid](https://www.postgrid.com/address-verification/)
+
+2. **Key Performance Indicators (KPIs)**: Identify the KPIs or metrics you would use to measure the performance of your new system and the business impact.
+
+3. **Product Requirement Document (PRD)**: Write a PRD that outlines the requirements for this feature. Break down the implementation into actionable, small steps.
+
+4. **Presentation Preparation**: In the next interview, you will present the feature and scope proposal to the Engineering Lead and other product managers during a project kick-off meeting. Choose a format that you believe will effectively communicate the user stories and how the feature will be implemented.
 
 ## F.A.Q.
 [Please click here for the F.A.Q.](./README.md#faq)