How do you estimate work using story points?
Assesses fundamental understanding of Agile & Scrum conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Story points estimate relative size, not time. They combine effort, complexity and uncertainty compared with other backlog items.
I use planning poker. The team discusses each item, asks clarifying questions, and simultaneously reveals a card from a sequence such as Fibonacci. Disagreement is useful because it surfaces hidden assumptions, so I ask the highest and lowest estimators to explain their thinking. We re vote until we converge, without forcing false consensus.
I anchor estimates with a reference story the team agreed on. A three point story is roughly three times the size of a one point story, but that says nothing about hours.
Points are for the team's own forecasting, not for comparing teams or measuring individual productivity. Velocity is a rough guide for how much to take into a sprint, and it should never be used as a performance target.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.