The first 10 minutes of any frontend design: turn a vague prompt into functional and quantified non-functional requirements, define scope, and make trade-offs explicit.
"Design a photo-sharing app" can mean an MVP for 1,000 users or Instagram. Without clarifying, you'll either over-engineer (offline sync and CDN sharding for a prototype) or under-engineer (no pagination for a feed with millions of items).
Senior engineers and architects are judged less on knowing technologies and more on asking the questions that change the design. In an interview, it's the clearest signal of seniority. At work, it's what prevents months of building the wrong thing.
A reliable framework for the first minutes:
Write them down where everyone can see them, and refer back to them for every later decision: "We chose virtualization because of the 'smooth after 30 minutes of scrolling' requirement."