Behavioral question

Can you please create requirements and acceptance criteria for this page https://www.apple.com/shop/buy-watch/apple-watch to be implemented by engineering team?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Whether you can translate a live webpage into precise, engineer-ready requirements and testable acceptance criteria.

Open and walk the actual page's flow: product options like case size, band, and connectivity, price display, and the add-to-bag action.
Write functional requirements for each interactive element: selecting a size updates price and image, selecting an unavailable combination disables add-to-bag.
Write acceptance criteria in a testable, given-when-then style, such as given a size is selected, when an incompatible band is chosen, then show an inline warning.
Cover edge cases: out-of-stock combinations, price changes with add-ons like engraving, and accessibility for keyboard-only navigation.
Note explicitly what would be confirmed with a real stakeholder, like exact copy for error states or specific accessibility standards to meet.
Keep requirements scoped to this page's flow, not the full checkout process beyond add-to-bag, unless asked to extend further.

Writes acceptance criteria in a testable given-when-then format engineers can directly turn into test cases.
Covers concrete edge cases actually visible on the page, like incompatible size and band combinations.
Separates functional requirements, what the page does, from acceptance criteria, how to verify it's correct.
States explicitly what needs stakeholder confirmation, like exact error copy, instead of inventing details.

Writing vague requirements like the page should work well instead of specific, testable statements.
Ignoring edge cases like out-of-stock variants or incompatible option combinations.

How would you prioritize which edge cases get covered in the first release?
What would you do if engineering said one requirement wasn't technically feasible?