How to answer interview questions

In this article

1. Before you start
2. Why interviewers ask this
3. Answering interview questions from first principles
4. The Staff-level answer
5. The rubric
6. Three variants of this question
7. Common mistakes
8. Follow-up questions
9. Sources

Before you start

Why interviewers ask this

The way you answer matters as much as what you say, because an answer is the only evidence the interviewer gets. A rambling answer hides a good example; a tight one makes an ordinary example convincing. In the behavioral interview round of a structured interview, every candidate gets the same questions and a shared scoring scale. Google describes this as "using the uniform methods to assess candidates applying for the same job", and it scores answers against a written rubric with levels such as outstanding, solid, borderline and poor (Google re:Work, updated March 2026). A weak answer is long, vague and about the team; a strong one is short, specific and about what you did.

Answering interview questions from first principles

Answer-first

An answer-first reply is a spoken answer that states its conclusion in the first sentence and then supplies the evidence, so the interviewer can score it even if you are interrupted.

In plain words

Answering an interview question is like giving directions. Good directions start with the destination. They list the turns in order. They stop on arrival. Bad ones start with the history of the road.

The analogy breaks in one place. Directions can be impersonal. An answer must show your own decisions, because the interviewer scores you and not the team. The University of Cincinnati career guide says the same: focus on your individual contributions and use "I" instead of "we" (University of Cincinnati).

Precisely, a good answer is a short conclusion plus one specific first-person example. None of the sources below states an answer length. This page uses two minutes only as an illustrative upper bound.

1 · Classify2 · Answer first3 · Prove it4 · StopReplay

Step-by-step description

1. Decide what kind of question it is.
2. Say the conclusion in sentence one.
3. One STAR story, weighted to action.
4. End on the result and pause.

• Classify the question as behavioral, hypothetical or knowledge.
• The first sentence is the conclusion.
• The proof is one story told in the order situation, task, action, result.

Step 1: Classify the question

Classifying the question means deciding, in two seconds, which of three kinds you were asked, because each needs a different answer. (Two seconds is a suggestion, not a measured figure.) The input is the interviewer's sentence; the output is a label. A behavioral question asks about the past ("Tell me about a time you disagreed with a teammate").

A hypothetical question asks what you would do in a made-up case ("What would you do if two deadlines clashed?"); Google's guide separates the two the same way, with behavioral questions revealing "patterns of behavior" and hypothetical ones showing how you might handle something new (Google re:Work). A knowledge question asks what you know or think about a fact or an opinion. Only the first kind needs a STAR story. What you now know: the label tells you the shape of the answer.

Step 2: Answer in the first sentence

The first sentence is the conclusion, said before any story. For a behavioral question, it is a one-line claim about what you did and the outcome: "I settled a disagreement about launch priorities by comparing what breaks for a customer if each item slips." For a hypothetical, it is the decision you would make and your reason. For a knowledge question, it is the definition or the answer. The input is the question; the output is a sentence that could be scored on its own. If the interviewer stops you after it, you have still answered. What you now know: the interviewer holds your answer before the evidence arrives.

Step 3: Prove it with one story and budget the words

The proof is one example told in four parts, and the budget is what keeps it short. The University of Washington guide defines the parts: Situation sets the scene with background and context, Task describes what you took on, Action explains what you did and how, and Result explains how it ended, including what you learned if it went badly (University of Washington). The error to watch for is spending the words on the first part, as the weak sample below does.

MIT's Career Advising & Professional Development (CAPD) office gives a time split of Situation 20%, Task 10%, Action 60% and Result 10%, presented as a guide and not a rule (MIT CAPD, read 2026-10-24). It gives no answer length, so two minutes is only an illustration. Turning minutes into words needs a speaking rate, and the only dated measurement used here comes from telephone conversations, not interview answers: Yuan, Liberman and Cieri (2006) report 196 words per minute overall and 164 when counted turn by turn, a figure they say is lowered by overlapping speech, plus 193 in a second corpus (Yuan, Liberman and Cieri, 2006).

Using 164 to 196 gives an illustrative 328 to 392 words per two minutes; at any length, every sentence of background removes a sentence of evidence. The table in the worked example measures two answers against the MIT split.¹ What you now know: the action is where the score is made.

Step 4: Stop and check

Stopping means ending on the result, then pausing so the interviewer can choose the next question. The input is your finished result sentence; the output is silence of one or two seconds. Do not add a summary of what you just said and do not apologize for the length. If you are unsure you covered it, ask one short question: "Is that the level of detail you wanted, or shall I go further into the decision?" That hands the interviewer the steering wheel on your terms. Practice this out loud with a timer, so the pause becomes familiar. What you now know: the answer ends where the evidence ends.

Two answers side by side

The difference between a weak and a strong answer to the same question is where the words go. Both examples are illustrative composites written for this page, with no real person and no company. The question is "Tell me about a time you disagreed with a teammate."

The strong answer is the shorter one and still short of the MIT split: 46% on the action against 60%, so any extra words belong in what you did, not in background. Both counts are of the answers exactly as printed above.

Text description of the diagram

• The weak sample spends 63% of its words on the situation and 19% on the action.
• The strong sample spends 25% on the situation and 46% on the action.
• The MIT CAPD guide suggests 20% on the situation and 60% on the action.

The Staff-level answer

A Staff-level answer (Staff is a senior-plus engineering level) adds the rule you took from the episode, because senior interviewers are scoring judgement that carries to the next case. It keeps the answer-first sentence, the single story and the action-heavy budget.

What makes it Staff-level: the conclusion comes first, the decision rule is stated, and the story ends with a habit that applies to the next disagreement.

The rubric

Three variants of this question

How to answer interview questions when you have no experience?

Use examples from outside paid work and say what they are. The University of Cincinnati guide suggests drawing on "work, volunteering, or another relevant experience" and varying the areas of life you draw from (University of Cincinnati). The University of Washington guide, which addresses candidates without much formal work experience, points to the same kinds of source: school and group projects, other jobs or volunteering, and personal achievements (University of Washington). A group project, a club role or a family responsibility has a situation, a task, an action and a result, so the structure works unchanged. Name the setting in your first sentence ("In a group project at university, I...") so the interviewer knows what kind of example to expect.

What if you do not understand the question?

Say what you understood and ask one clarifying question before answering. "Are you asking about a time the disagreement was with a peer or with a manager?" costs a few seconds and prevents a long answer to the wrong question. The University of Washington guide advises asking for clarification when you are unsure how to answer (University of Washington).

What if you freeze or need time to think?

Ask for a moment, and use the first sentence of the method as the thing to find. "Let me think of the best example" is a reasonable short pause; the University of Washington guide says you do not need to respond immediately and can take a moment to consider the question (University of Washington). Then give the conclusion in one sentence before you have the whole story, so you are committed to a direction and not improvising a middle.

Common mistakes

1. Starting with the background. (wrong) "So this was at my last job and there had been a reorganization." (right) "I settled a disagreement about launch priorities by comparing the cost of delay." The conclusion first lets the interviewer score you early.
2. Saying "we" for everything. (wrong) "We decided to put sign-up first." (right) "I proposed sign-up first and wrote the reasons." The interviewer is scoring you, and "we" hides your part.
3. Ending with "it went fine". (wrong) "It went fine and everyone was happy." (right) "We shipped on time and the dashboard followed four days later." A result you can name is evidence.
4. Using one story for every question. (wrong) "Let me tell you about the same launch project again." This is the sentence a candidate says when the one prepared story is reused for teamwork, conflict and failure. It shows one side of you. (right) "A different example shows this better: a time I..." Prepare a few stories that show different skills, as the University of Washington guide advises (University of Washington).
5. Letting the story run long. (wrong) "So, to give you the full background first..." followed by a 500-word story where most of the words are background. The interviewer cannot score what never arrives. (right) "In short, I did X and the result was Y; the key decision was Z." A story that stays under about two minutes (roughly 330 to 390 words at the conversation rates above, a ceiling and not a target; the strong sample is 112); cut context first.

Follow-up questions

How do you answer interview questions confidently?

Confidence is easier when the first sentence is ready, because you start from a decision and not from a blank. Decide the conclusion before you speak, say it plainly, then tell one example you know in detail. A story you can describe step by step is easier to deliver steadily than a general claim. Practice it out loud with a timer, as in Step 4.

How do you answer hard interview questions?

Classify the question first, as in Step 1. A hard behavioral question, such as one about a failure, still takes the same shape: a conclusion, one story and an honest result. For a hypothetical you have never faced, state the decision you would make and your reason. If you need time, say "Let me think of the best example" and then answer in one sentence.

How do you answer interview questions properly?

Answer the question that was asked, in order: conclusion, one specific example in the order situation, task, action, result, then stop. The MIT guide says most of the response should be the actions you took (MIT CAPD, read 2026-10-24). Practice opening lines like the one in tell me about yourself. Related pages: the wider interview loop, leadership interviews, the questions to ask the interviewer and salary negotiation.

How long should an answer to an interview question be?

No source used here states a length. As an illustration, two minutes is roughly 330 to 390 words at the conversation rates of 164 to 196 words per minute in Yuan, Liberman and Cieri (2006), measured on telephone speech and not interview answers. The strong sample on this page is shorter, 112 words or about 34 to 41 seconds; keep the split, and go longer only if the interviewer asks for depth.

Should I say I or we in an interview answer?

Say "I" for what you did and "we" only for what the team achieved. The University of Cincinnati guide asks you to focus on your individual contributions so the interviewer can see your own role (University of Cincinnati).

What if the result of my story was bad?

Tell it anyway, and make the last sentence what you changed. The University of Washington guide says that if the situation did not go as planned you should describe what happened and what you learned (University of Washington). A clear change in your behavior gives the interviewer a concrete result to score, which a vague success does not.

Sources

1. A guide to structured interviewing for better hiring practices (updated March 2026) — Google re:Work, 1 Mar 2026
2. Prepare for your university advancement interview using the STAR method (undated page, read 2026-10-24) — University of Washington, 24 Oct 2026
3. STAR method for behavioral interviews (undated page, read 2026-10-24) — University of Cincinnati career and co-op support, 24 Oct 2026
4. Using the STAR method for your next behavioral interview (MIT CAPD; date = read date) — MIT Career Advising & Professional Development, 24 Oct 2026
5. Towards an Integrated Understanding of Speaking Rate in Conversation — Interspeech 2006 (Yuan, Liberman, Cieri; University of Pennsylvania), 17 Sep 2006