Requirements

Requirements work reduces ambiguity before code: who the user is, what outcome matters, which constraints apply, which edge states must be handled, and how "done" is verified. Interviewers reward questions that expose hidden assumptions—not premature framework choices.

Subtopics: clarifying questions, edge cases, acceptance criteria.

On interviews: walk through turning "add export" into users, formats, permissions, empty data, errors, and measurable acceptance tests.

Common pitfalls: solution-first brainstorming; missing unauthorized or slow paths; acceptance criteria that are not observable.

The trade-off is time spent in discovery versus rework when production surprises appear in edge states.

Checklist:

• Ask about users, goals, and success metrics.
• Enumerate empty, error, permission, and concurrency cases.
• Write observable acceptance criteria.
• Link criteria to tests or analytics.