System design round -
You have product page where you can view the details of a product (eg . a washing machine or a geyser). Design reviews feature for it.

Some questions asked by the interviewer :

Do you notice any ambiguities in the question? - I could not find any.
If a customer posts a review, it gets disconnected, the customer thinks that the review is not posted (however, in Amazon back-end, it is stored) and tries to post again. It results in a duplicate post. How do you avoid it ?
Which id is better to store orderId s in amazon - numeric or UUID ? Why?
How do you store the reviews ?
What will be your API URL and the structure of the request?
Where will you store user information - URL or Headers or request body ? Why?
Answers to these questions are highly appreciated as I struggled to answer most of them. However, that is not all. You need to present a complete System design for this feature.