What to work through
Work through a multi-step form as a spoken system design interview. Start by clarifying the scope, sketch a working design and explain the trade-offs behind your choices.
- Walk through several pages of questions, forward and back, with progress shown
- Keep answers across pages, reloads and a break of hours
- Check each field as the person goes, and again on the server
- Review everything, then submit once, even if the button is pressed twice or the network drops
- Show pages that depend on earlier answers, such as the type of business
Constraints to discuss
- A press of Next or Submit answers within 200 milliseconds
- Answers survive at least 20 hours with no activity
- A repeated final submit never creates a second account
- Usable with a keyboard and a screen reader, each page change announced
- Information already given is filled in or offered, never asked for again (WCAG 2.2, 3.3.7, level A)
Need a starting point?
Watch for these common gaps as you prepare:
- Losing answers on Back or on a reload
- Checking fields only on the final submit
- Relying on a disabled button to stop a second submit
- Making a new submit key for each retry, so the retry creates a second account
- Keeping the step only in component state, so the browser Back button leaves the flow
- Saving card or identity numbers in the browser
- Moving to the next page without moving focus or changing the title
Why this question is in the collection
These sources connect the problem to company interview reports or preparation guides. They do not guarantee what a company will ask you.
- Stripe: A frontend engineer in the United States, March 2022, with an offer, reports a frontend system design round on a real Stripe page: break it into components with their APIs and state, keep it accessible, and allow for future changes. Those were part of the task as described, not follow-ups, and the page does not say which Stripe page it was.
- Stripe: The Front End Interview Handbook lists, with no date and no candidate report behind it, a multi-page frontend flow with shared form state, and how retries, duplicate submissions and server-confirmed outcomes affect the interface. A February 2026 tip names a one-hour Full Stack Design round for a full-stack developer, but not its question.