They asked about the project. They're scoring your decisions.

Asked about leading a project, most engineers describe the project — architecture, stack, team structure, timeline, challenges. Five minutes later the interviewer knows the system well and the candidate not at all. This is system narration: technically rich, personally empty. It is especially common among engineers from service companies and architecture-heavy roles, where presenting the system is the professional habit. But the question was never about the system. It was about the moments you exercised judgment.

A leadership answer is a sequence of decision points: the moment you scoped, the moment something went wrong, the call you made, the disagreement you resolved, the tradeoff you chose. US interviewers listen for 'I decided', 'I prioritized', 'I pushed back', 'I cut'. The project is just the stage. Structure the answer as situation (15 seconds), the 2-3 decisions you made and why (the core), and the quantified result. If your answer has no moment where you could have chosen differently, you have not described leadership.

The strong version names two decisions, the reasoning, the cost ('unpopular', 'three weeks late'), and an honest comparative result. Imperfect outcomes told with ownership score higher than perfect outcomes told without it.

Arpan gives you the feedback that solo practice can't. The free Diagnostic scores your answers across Ownership Language, Quantified Impact, STAR Structure, Conciseness, Engagement, and Professional Tone — the exact dimensions US hiring managers evaluate — and delivers word-for-word rewrites of every answer so you can see the gap clearly. Pro turns that into a practice loop: every answer rewritten across 25 voice interviews and 5 on camera over 90 days, pattern detection that surfaces which habits are costing you points, and your Cultural Readiness Score™ after every session, so you can see where the score moves.