Practise your job interview answers (with a scored example)

Written by Toby Sinclair

Updated

Key takeaways

Use a structure the interviewer can score: situation, task, action, result.

When they ask you to be specific, give a name, a number, and a decision.

Composure under the follow-up is part of the answer.

Vague stories that sound fluent still fail the probe.

Watch a 2-minute example of practise your job interview answers — then see how it is scored.
Practise this conversation now

No sign-up · about 5 minutes · you’ll need a mic

Answer in a structure the interviewer can score: situation, task, action, result. Lead with the result when the story is long. When they ask you to be specific, give a name, a number, and a decision you made — not another adjective. Composure is part of the answer. A precise story told calmly beats a dramatic story that collapses under a follow-up.

1. Structure is how interviewers listen

Competency interviews are not conversations about your personality. They are scoring exercises. The interviewer has a rubric: did you own a problem, what did you do, what changed. STAR is not a slogan. It is the shortest path to those ticks. Situation in one sentence. Task in one sentence. Action as the body — what you did, not what “we” did. Result with a number or a visible change. If you cannot fit the story into that shape in practice, the live interview will turn into a ramble and the probe will come: can you be specific?

2. Specificity is the whole game once they lean in

Vague answers invite the same follow-up from every decent hiring manager. “We improved the process.” Which process. By how much. What did you personally change. “I am a collaborative leader.” Give the meeting, the disagreement, and the decision. Practise naming artefacts: the deck, the ticket, the customer, the week. You do not need to invent classified detail. You need enough concrete that a stranger can see you in the room. When the avatar asks you to be specific, that is the test — not the first polished paragraph.

3. Composure under probing is a skill, not a mood

People who interview well in the shower often freeze when the follow-up arrives. They fill silence, they restart the story, they apologise. Hold the pause. Repeat the question in a shorter form if you need a second. Then give one example, not three. If you do not have a perfect story, say what you did have and what you would do next time. Interviewers punish invention more than an honest gap. What they cannot score is fog.

4. Prepare bones, not speeches

Pick five or six stories that can stretch: a delivery under pressure, a conflict, a miss, a time you changed someone’s mind, a time you did not have the data. For each one, write four lines only — situation, your task, the action that was yours, the result with a number. That is the whole prep. If a story needs a slide deck to make sense, it is too fat for an interview. Practise saying the four lines out loud, then practise the follow-up: “what did you personally do?” If you cannot answer that in one breath, the story still belongs to “we.”

5. After a sticky interview, write the probe you failed

The useful debrief is not “I was nervous.” It is the exact follow-up that landed and the sentence you did not have. Write that probe down. Rebuild the story so the action and the result arrive before the two-minute mark. Then practise that one story again, not your whole catalogue. Interviews are lost on the second question, not the first. People who only polish openings keep failing the same probe. If you froze, practise the pause: repeat the question in a shorter form, then give one example. Filling silence with a second story is how you sound fluent and still fail the rubric.

6. Stop when the answer is done

A short answer they can probe is more useful than a monologue they cannot. Ninety seconds is plenty for the first pass. Then stop. Let them ask. Stopping is a signal that you trust the story. People who keep talking after the result are usually hiding from the next question. Practise the stop in the room until it feels rude. It is not rude. It is how interviewers get to the part they can score.

Mistakes that sound fluent and score poorly

Starting with your childhood. Using “we” until your own actions disappear. Answering a competency question with a hypothetical. Talking for three minutes before the result appears. Getting sharper when they probe — irritation reads as fragility. Getting smaller — whispering, hedging, “I guess” — reads as unprepared. Practise the boring version: short structure, one number, one decision, then stop. Let them ask the next question. Stopping is a signal that you trust the answer.

What to say

A scored shape for “tell me about a time you unstuck a team.” Swap in your artefacts. Keep the result in the first pass.

You

Last quarter we were six days behind a release because engineering and ops were not aligned on the blockers.

You

My job was to get a decision in the room, not another status meeting.

You

I ran one session, made each lead pick a must-solve item that day, and owned the follow-up list.

You

By the next standup three blockers were gone and we shipped a week ahead of the rescheduled plan.

If they say this

They say

You say you led it — what did you actually do?

You say

I set the agenda, I stopped the tour of complaints, and I made each lead leave with one named action they owned that day. The list was mine to chase.

This is the probe that kills “we.” Answer with verbs that only you could have done.

They say

Can you be more specific?

You say

The meeting was Tuesday. The artefact was a twelve-line blocker list in the shared channel. I assigned the three that sat between engineering and ops.

Specific means a day, an artefact, and a decision — not a stronger adjective.

They say

What would you do differently?

You say

I would have named the decision-maker before the session so we did not spend twenty minutes rediscovering who could say yes.

An honest gap scores. Inventing a perfect story after the probe does not.

Thank-you note after the interview

Optional, and only useful if it adds a concrete. Do not re-pitch your personality.

Hi Rachel,

Thank you for the time today. You asked what I personally did to break the gridlock on that release — I wanted to leave the artefact clear: the Tuesday blocker list, three owned actions, and a ship date a week ahead of the rescheduled plan.

Happy to go deeper on any of the examples.

Alex

Example attempt transcript

A scored example of this conversation — with what worked, and a mistake that is not recommended.

Rachel Bennett

Morning. Sorry to keep you waiting — let’s get started. Tell me about a time you got a cross-functional team unstuck under pressure.

Candidate

Last quarter, I led a release at my last company where engineering and ops weren’t aligned — we were six days behind target.

A common mistake

I'm a collaborative leader who thrives under pressure and always finds a way to get teams aligned.

That’s not recommended. Situation without the move is a story, not an answer. She already asked what you did. “We were behind” sets the scene and then stops. The probe was waiting because the action and the result were missing.

Rachel Bennett

You say you led it, but what did you actually do to break that gridlock? That’s the bit I need to hear.

Candidate

We mapped the blockers in one session so everyone saw the same priorities — I made each lead pick a must-solve item before the end of the day.

Rachel Bennett

Okay, and what changed after you had that session?

Candidate

By the next standup, three blockers were resolved and we shipped a week ahead of the rescheduled plan.

What worked

The result is what she can score. A number, a time frame, and a visible change. That is the tick on the rubric. The earlier fog cleared the moment the outcome showed up.

Rachel Bennett

Fine — that’s clearer. Thanks.

This example scored 74 / 100.

Try this exact scenario

No sign-up · about 5 minutes · you’ll need a mic

Frequently asked questions

How many stories should I prepare?
Five or six that can stretch across leadership, conflict, failure, delivery, and working with incomplete information. Depth beats a catalogue of thin anecdotes.
What if I do not have a perfect example?
Use a smaller true story and be explicit about scope. A real decision in a messy situation scores higher than a polished fiction.
Should I memorise scripts?
Memorise the bones: context, your action, the result. Scripted sentences crack when the interviewer interrupts. Structure survives interruption.
How long should an answer be?
Ninety seconds is plenty for the first pass. If they want more, they will ask. A short answer they can probe is more useful than a monologue they cannot.
Should I use STAR out loud?
Use the shape, not the acronym. Saying “situation, task, action, result” in the room sounds like a course. Let them hear a story that happens to be scorable.

Career

How to ask for a pay rise

Name the number, show the value, and leave with a dated next step.

Career

How to tell your boss you're resigning

Resign in one clear sentence, hold it, and offer a transition.

Career

How to negotiate salary

Name a counter, hold the “fixed band,” and leave with a written revision.

Career

Questions to ask in an interview

Ask sharp questions and follow up when the answers go vague.

Career

How to answer what are your weaknesses

Name a real weakness, show the change, and survive the follow-up.

Career

How to answer tell me about yourself

A 90-second present-past-future pitch aimed at this role.

Career

How to ask for a promotion

Name the next role, show you are already doing it, and get a date.

Career

How to ask for flexible working

Name the pattern, show coverage, and get a written decision date.

Manager

How to tell an employee they're not getting promoted

Deliver a clear no, honest reasons, and a path — then hold it.

Compliance

How to talk to a vulnerable customer

Spot hardship mid-call, leave the script, and offer a real next step.

Manager

How to give feedback to a colleague

Give peer feedback that stays specific when they call it an attack.

Manager

How to give negative feedback to an employee

Name the slip with examples, keep the message intact, agree dated actions.

Commercial

How to respond when a customer says a competitor is cheaper

Hold price under a real cheaper quote without panic-discounting.

Manager

How to talk to an employee about personal hygiene

Raise body odour privately, directly, and with a practical next step.

Compliance

How to respond when a colleague discloses harassment

Listen, refuse a secrecy promise, and signpost the real route.

Manager

How to fire someone

Lead with the decision, stay human, and do not reopen the case.

Commercial

How to handle an angry customer

Let them finish, name the miss, and offer a fix you can keep.

Manager

How to put someone on a PIP

Name the plan, the measures, and the review — without pretending it is casual.

Manager

How to tell someone they're being made redundant

The role is gone. Say that, stay human, and do not fake a promise.

Explore more conversations

Reading about it is the theory test. Practising it is the driving test.

Practise this conversation now

No sign-up · about 5 minutes · you’ll need a mic

Written by Toby Sinclair, founder of Real Talk Studio. Updated 15 August 2026.

Practise this conversation now

No sign-up · about 5 minutes · you’ll need a mic