What makes a strong interview answer
Last updated
A strong interview answer has five things: detail only you could give, a story that gets to the end, a result someone measured, a length that fits the question, and a clear account of what you did yourself. This guide takes each one in turn, with weak and stronger examples for behavioral, situational and technical questions.
The five traits are this site's own synthesis of common interviewer guidance, not a study of user answers. They rest on how structured interviews work: every candidate gets the same questions and each answer is rated on the same scale against standards for an acceptable answer.[1] All example answers below are made up for illustration.
Be specific
A vague answer could have come from any candidate. “I improved the process and made the team more efficient” tells the interviewer nothing they can check or ask about. Specific answers name the system, the decision, the people involved and what was hard about it, the kind of detail you only know if you were there.
Asked about a time you improved a process, compare these two openings.
“I’m always looking for ways to improve things. At my last job I streamlined how we handled requests and it made a big difference.”
“Support tickets about billing were landing in a shared inbox, and three of us were answering the same ones twice. I set up a rule in Zendesk that tagged anything mentioning an invoice and sent it to one queue with a named owner each day.”
The second version gives the interviewer something to follow up on, which is usually what they want. Naming a tool helps. Saying why you chose it, or what you tried first, helps more.
Give it a structure
For behavioral questions (“tell me about a time…”) the usual frame is situation, task, action, result. Set the scene in a sentence or two, say what you were responsible for, spend most of the answer on what you did, and finish with what happened. MIT Career Advising suggests roughly 20% situation, 10% task, 60% action and 10% result, and presents it as a guide.[2] Prospects adds a fifth step, reflection, for what you learned.[3] The behavioral interview guide covers the frame in more depth.
An easy mistake is to stop early. Candidates describe the situation at length, mention an action, and never say how it turned out. If your answer has no ending, the interviewer has to ask for one, and that costs you the point.
Technical questions have their own shape: the problem, your approach and why you chose it, then the solution and its trade-offs. “I’d use a queue” is an answer; “the writes come in bursts the database can’t absorb, so I’d put a queue in front and accept a few seconds of delay on the dashboard” is a stronger one, because it shows the reasoning.
Answer a what-would-you-do question
Not every question asks for a story. OPM describes structured interviews as asking about past experiences and about proposed behaviour in hypothetical situations.[1] A situational question gives you a scenario and asks what you would do, so you have no result to report yet. Say what you would check, what you would do and how you would know it worked.
The question: “A teammate misses a deadline that blocks your work. What would you do?”
“I would talk to them. Deadlines slip sometimes and I would try to be understanding.”
“First I would ask them directly what is blocking them, because the cause decides what I do next. If it is a dependency I can help with, I would offer to take that piece. If the new date is later than I can absorb, I would tell our lead the same day and propose reordering my work around it, with the dates. Afterwards I would check whether the deadline was realistic in the first place, so it does not repeat.”
The first answer is polite but names no step. The second shows ownership, a sequence and a way to check the outcome. Because the result is projected, it says what would be checked afterwards instead of claiming a number.
What a rating scale rewards
When every candidate gets the same question and the same scale, each answer is judged on the evidence it gives for that question.[1] A story that does not match the question scores low however good it is, and a modest story that fits the question can score well. Read the question for the skill it targets: Prospects notes each question in a competency-based interview focuses on one skill, with prompts such as “Tell us about a time when…”.[3]
Put a number in the result
“It went really well” and “the team was happy” are outcomes nobody can weigh. A measured result is one the interviewer can picture: response time on billing tickets went from two days to same-day, page load fell from 2.3 seconds to 400 milliseconds, the launch shipped a week before the deadline.
The number does not have to be impressive, and it can be an estimate if you say so. What matters is that you knew how to tell whether your work helped. If nothing was measured, describe the change you could see and how you noticed it.
Fit the length to the question
A two-sentence reply to “tell me about a conflict with a colleague” almost always skips the action or the result. At the other end, a five-minute story usually means the setup has taken over.
A quick follow-up or a definition needs a few sentences. A behavioral story usually needs a minute or two spoken. A system design question can take much longer, but you should check in with the interviewer as you go. A short answer that is precise and has a measured result still beats a long one that wanders.
Say what you did
Interviewers are hiring you, so they need to hear your part. Answers that stay with “we” the whole way through (“we decided to migrate, we rewrote the service, we hit the deadline”) leave them unable to tell whether you led the work or watched it.
Credit the team where it is due, then switch to “I” for the decisions you made, the code you wrote, the conversation you had. “The team agreed to migrate; I wrote the plan for moving the data without downtime and ran the cutover” is honest about both.
One answer, rewritten
The question: “Tell me about a time you fixed a problem under pressure.” The incident below is invented to show the structure and is not a real case or a statistic.
“We had an outage once and the whole team worked hard to fix it. I helped with the debugging and we got everything back up. It taught me to stay calm under pressure.”
It is vague (which outage, what was wrong), it has no real action or result, and “I helped” hides what the speaker did. Here is the same story told well:
“Last spring I was on call when checkout started failing for about a third of our users on a Friday evening. I was the only engineer online, so the job of finding it was mine. The error logs pointed at the payment client timing out, and I saw the timeout had been cut from ten seconds to one in that afternoon’s release. I rolled back that one config change rather than the whole release, watched the error rate for ten minutes, then posted a summary in the incident channel. Checkout was working again within 40 minutes of the first alert. On Monday I added an alert on that timeout so a repeat would page us within five minutes.”
The situation and the task take two sentences. Most of the answer is the action, in the first person, with the reasoning behind each step. The result has a number, and the last line shows what changed afterwards.
A check before you answer
- Does the answer name something only you would know?
- Does it reach the result, or stop at the action?
- Is there a number, or at least a before and after?
- Is the length right for this question?
- Can the interviewer tell which part was yours?
The five traits overlap with the relevance, depth, clarity dimensions on which practice answers are scored: being specific maps to depth, structure to clarity and answering the question asked to relevance. The methodology page explains the scoring. You can rehearse the five out loud in a practice behavioral interview, and the interview best practices guide and glossary cover the wider format. Prospects advises practising answers with someone you trust or recording yourself.[4]
Questions
How long should an interview answer be?
As long as the question needs. A definition or a yes-or-no follow-up takes a few sentences. A behavioral story usually takes a minute or two spoken, enough for the situation, what you did and the result. If you finish in two sentences, you have probably left out the action or the outcome.
Do I have to use the STAR method?
No. STAR (situation, task, action, result) is one way to make sure a story has a beginning, your part and an ending. Any order works if the interviewer can follow what happened, what you did and how it turned out. For technical questions, problem, approach and solution does the same job.
What if I do not have a number for the result?
Use the best measure you can defend: time saved, a deadline met, the number of people or customers affected, a before and after. An honest estimate stated as one ("about a week faster") is better than "it went really well". If nothing was measured, say what changed and how you knew.
Should I memorise my answers?
Memorise the facts of each story and leave the wording loose. MIT Career Advising presents its STAR proportions as a guide, and Prospects advises practising answers with someone you trust or recording yourself. Rehearsing out loud makes the story flow, while a script breaks as soon as the question is phrased differently.
What if I use the wrong example?
Say so briefly and switch. If halfway through you see the story does not fit the question, one sentence such as "a closer example is..." is better than finishing it. Interviewers rate how well the evidence answers the question, so a fitting story told second still counts.
Is it wrong to say "we" in an interview?
Saying "we" for the team’s work is fine. The interviewer still needs to hear what you did, so switch to "I" for your own decisions and actions. An answer that never separates your part from the group’s leaves the interviewer guessing.
Sources
The studies, statutes and primary pages this guide relies on. Numbers in square brackets in the text link here; where a claim has no number, it is our own guidance from running practice interviews.
- Structured Interviews. US Office of Personnel Management
- The STAR Method for Behavioral Interviews. MIT Career Advising & Professional Development
- Competency-based interviews. Prospects (Jisc)
- How to prepare for an interview. Prospects (Jisc)