Two candidates with the same experience give completely different interviews, and the difference is rarely confidence. It is granularity. One talks in categories — collaborative, detail-oriented, passionate about the mission — and the interviewer has nothing to hold onto ninety minutes later. The other talks in events, with names and numbers and one thing that went wrong, and the interviewer can still repeat the story in the debrief.
Everything below is about producing the second kind of answer without turning into someone who recites.
What is usually going on
You are describing yourself rather than reporting what happened. Adjectives are self-assessment, and the interviewer discounts self-assessment automatically because everybody claims the same six. Events cannot be discounted the same way. The move is mechanical: every time you are about to say a quality, say the incident that would make someone else use that word.
You have no numbers, so nothing has scale. I improved the process could mean twenty minutes a month or two headcount. Even a rough figure — roughly a third, about eight hours a week, from four days to one — changes the answer from a claim to a measurement. Most people have these numbers and have never bothered to look them up.
You are hiding the part where it was hard. Interviews that consist only of successes read as either junior or evasive. The answer that lands includes the constraint, the thing that nearly failed, and what you changed — not as a confession, as evidence that you were actually in the room rather than adjacent to it.
You are answering the question about your weakness with a strength in costume. I care too much. I work too hard. Interviewers have heard it several thousand times and it reads as a small refusal to engage. A real limitation, named plainly with what you do about it, is one of the few chances in the conversation to sound like an adult.
You cannot describe how you work, because nobody has ever asked. Most people know what they have done and have no vocabulary for their method — whether they plan or start, whether they need the whole picture or the first step, whether they think out loud or arrive with a draft. This is the question that produces the longest silence, and it is entirely preparable.
What to do before the interview
- Choose five stories, not fifteen. Five events that between them cover a hard technical call, a conflict with a person, a failure, something you built from nothing, and something you improved. Almost any question can be answered with one of five well-chosen stories, and five is a number you can actually remember while nervous.
- Put a number in each one. Go and find it. An hour in old documents buys you the thing that separates your answer from the next candidate's.
- Write your method in two sentences, in your own words. Not I am detail-oriented — something like I start by writing the thing nobody has written down yet, then I take it to the person most likely to hate it. That sentence is worth more than any adjective on your CV.
- Prepare the weakness honestly and pick one that is true and survivable. What you have done about it is the entire answer; the weakness is just the setup.
- Practise out loud, once, badly. Silently rehearsing is a different motor skill from speaking, which is why people who feel well prepared still hear themselves ramble in the first answer.
What it depends on
The description of how you work is the hardest part to invent under pressure and the easiest to prepare in advance, because it does not change between interviews. The work style test returns percentiles on structure, pace, autonomy and collaboration and then writes your profile the way you might say it in a room — which is the point of it here. Someone who scores high on structure and low on collaboration is not worse than the reverse; they are a specific kind of hire, and saying so plainly is far more persuasive than trying to sound like every kind. If the interviews keep going well and the offers do not come, the mismatch may be further upstream, in what kind of work you are aiming at rather than how you describe it.