What are the components of a well-written user story?

WHAT THIS TESTS: This question assesses your understanding of core agile principles. The interviewer is checking if you view a user story as a "promise of a conversation" rather than a rigid, upfront specification. They want to see that you prioritize collaboration, shared understanding, and iterative development over a waterfall-style requirements document. It's a test of your process maturity and ability to work effectively in an agile team.

A GOOD ANSWER COVERS: A strong answer typically addresses four key areas. First, the "Three C's" framework: the Card (the written story), the Conversation (the collaborative discussion to flesh out details), and the Confirmation (the acceptance criteria that prove it's done). Second, the INVEST model for story quality: Independent, Negotiable, Valuable, Estimable, Small, and Testable. Third, the standard "As a [persona], I want [goal], so that [value]" template, explaining its role in providing context. Finally, the role of Acceptance Criteria (ACs), ideally using the "Given-When-Then" format to define specific, testable outcomes without dictating implementation.

COMMON WRONG ANSWERS: A major red flag is treating the user story as a comprehensive spec sheet. Candidates who only recite the "As a..." template without discussing the conversation or confirmation parts are missing the point. Another common mistake is writing acceptance criteria that are implementation-focused ("The save_user method is called") instead of user-observable ("The user's profile is updated and a success message is shown"). Finally, creating stories that are not valuable to an end-user (e.g., "As a developer, I want to refactor the database schema") is a smell; these are better framed as technical tasks.

LIKELY FOLLOW-UPS: Be prepared for questions like: "How do you split a story that's too large to fit in a sprint?", "What's the difference between a user story and a technical task?", and "Who is responsible for writing user stories and acceptance criteria?" (Answer: The whole team, collaboratively, with the Product Owner having the final say on priority).

ONE CONCRETE EXAMPLE: Story: "As a registered user, I want to log in with my email and password so that I can access my secure account information." Acceptance Criteria: 1. Given I am on the login page, when I enter valid credentials and click 'Log In', then I am redirected to my dashboard. 2. Given I am on the login page, when I enter an invalid password, then I see an error message "Invalid email or password."