It is the first question in almost every interview, it is not small talk, and the rest of the conversation is made of follow-ups to whatever you say.
If you have come from nursing, teaching, law, retail or admin, you have two problems with it. You have never run a software project, and the honest answer feels like it will end the interview.
It will not, if you do it in this order.
The wrong instinct
The wrong instinct is to stretch something. To describe a rota change as a delivery project, or to let the interviewer assume the practice project was paid work by simply not mentioning that it was not.
That second one is the dangerous version, because it is passive. You did not say anything untrue. You just let them believe something, and when it comes apart in the second interview, it comes apart completely.
The other wrong instinct is to apologise. To open with “well, I have not really had a proper project, but”. Everything after that sentence is heard as an excuse.
The shape of an answer that works
Every good answer to this question has five things in it. If one is missing, you can feel the answer sag.
- A situation with edges. A named project, a named story, a specific sprint. Not “in my experience”.
- Your own decision. Something you chose, where choosing differently was possible. Most people describe what happened to them rather than what they decided.
- A cost you name. A sprint missed, a story slipped, somebody unhappy. An answer where nothing cost anything sounds like marketing.
- An outcome at the right size. What actually happened, not what it proved about you.
- Something that outlived it. A retrospective action, a rule that stuck. This is what separates having an experience from learning from it.
Where the disclosure goes
One sentence, early, level voice, no apology:
This is a simulated delivery I built to work through a full cycle end to end.
Put it near the front, not at the end. At the end it reads like a confession you were hoping to avoid. Near the front it reads like somebody who is straightforward about their evidence, and every sentence afterwards is trusted more, not less.
Then do not repeat it in every subsequent answer. Said once, clearly, it covers the conversation.
The trap is specific. The blocker question is the one you will rehearse most, and if the interviewer opens with it rather than with “tell me about a project”, your rehearsed answer has no disclosure in it. Rehearse that one twice: once as it stands, once with the sentence at the front.
A worked answer
Ninety seconds. Rehearsed until it stops sounding rehearsed.
I built a practice delivery to work through a full cycle end to end. It is a returns overhaul for a clothing retailer with 40 stores and an online shop. Customers could only send online orders back by post, refunds took about two weeks, and a third of the contact centre’s calls were people asking where their money was.
Four epics, twelve stories, three sprints, 61 points. Self-service returns, in-store returns for online orders, automatic refunds, and enough reporting to tell whether it worked.
The part I learned most from was a three point story showing the customer when their refund would arrive. It blocked for six days, and not for a technical reason. Customer services had been telling people fourteen days from posting. Finance had been working to thirty days from receipt. Both had been saying it to real customers for two years and nobody had noticed.
I raised it on day two, escalated on day five with the cost stated, and got a decision on day eight. By then there were two days left, so I carried it rather than rush it, and we missed the sprint by three points. The retrospective action was that any story resting on a policy nobody has written down gets confirmed before it enters a sprint.
Nothing shipped, because it is simulated. What is real is the thinking and the artefacts, and I am happy to be asked about any of it.
Why that scores
There is a named project and a named story. There is a decision, carry it rather than rush it, and the alternative is visible. The cost is three points and a missed sprint. The outcome is stated at practice-project size. The retrospective action outlived the sprint.
And notice what it does not do. It does not rescue the sprint with a clever move. Answers where the candidate’s quick thinking saves everything sound invented, because in real delivery they usually do not.
What most people say instead
“I worked on a returns project where we improved the customer experience and reduced call volumes significantly.”
No specifics, no decision, no cost, and a claimed result the project cannot support. That last word, significantly, invites the one follow-up you cannot answer: how did you measure it.
If you genuinely have no project yet
Then build one before you interview, because this question is not avoidable and there is no verbal trick that covers for having nothing.
It does not need to be large. Four epics, twelve stories, three sprints, and one thing that went wrong for a boring reason. The thing that went wrong is the part you will actually be asked about.
How to practise it
Record yourself answering it cold, before you read any model answer. Then score what you said against the five things above. Then answer once more and stop.
Recording is the step everybody skips and it is the one that works, because you cannot hear your own filler words in real time. You will hear them on playback, along with the pause where you realised you had no ending.
Leave it a week. Answer cold again. If it survived the week, it is yours. If it collapsed, you memorised it instead of understanding it, and the fix is to go back to the project rather than to the script.
The part a file cannot do
The Interview-Ready Toolkit has twenty questions with worked answers across all four roles, a rubric specific enough that scoring your own recording is not just marking your own homework, a second practice project so you are not telling the same story twice, the CV and LinkedIn rewrite, and the ceremony scripts.
What it still cannot do is hear the pause where you lost your thread. For that you need a person listening. See the mentorship
Not sure which of the four you are aiming at?
The Role Fit Diagnostic is sixteen statements. You tick the ones that are true of you now, count your ticks by letter, and read the page for whichever role you already work like. Ten pages, printable, free, about six minutes.