Behavioral Interview Questions: Answer Them With the STAR Method
Behavioral interview questions ask for a real past example ("Tell me about a time when..."). Answer with the STAR method: briefly set the Situation and Task, spend most of the time on the Action you personally took, and finish with a Result. Prepare five reusable stories and you can answer most of them.
At a glance
- Behavioral questions assume past behaviour predicts future behaviour.
- STAR = Situation, Task, Action, Result. Roughly 10 / 10 / 60 / 20 percent of the answer.
- Use "I", not "we", for the Action. Interviewers need to know what you did.
- Give a result, even a small one, and what you learned.
- Prepare five stories and map each to several questions.
What is the STAR method?
| Letter | What to say | Target length |
|---|---|---|
| Situation | Where and when, in one or two sentences | 10 seconds |
| Task | What you were responsible for or what needed to happen | 10 seconds |
| Action | The specific steps you took, in order, and why | 45 seconds |
| Result | What changed, with a number if honest, plus what you learned | 20 seconds |
Some interviewers use STAR-L or CAR (Context, Action, Result). They are the same idea.
Worked example 1: conflict with a coworker
Question: "Tell me about a time you disagreed with a colleague."
Situation: "On a product launch last spring, our designer and I disagreed about whether to ship a checkout redesign before the holiday weekend. Task: I was the engineer responsible for the release, so the decision on timing affected my team's on-call load. Action: Rather than argue in the group chat, I asked her for 20 minutes. I listened first, and learned she was worried about a known confusing button, not about the date. I proposed we ship the redesign to 10% of users first, with that button fixed, and I wrote the rollback steps. I shared the plan with our manager so the trade-off was visible. Result: We shipped on schedule to the smaller group, fixed two issues the same day, and rolled out fully the following week. We also agreed to hold a short pre-launch review for every release after that. What I took from it is to find out what the other person is actually worried about before arguing about the solution."
Worked example 2: a mistake
Question: "Tell me about a time you made a mistake."
Situation: "In my second year as an account coordinator I sent a client a report with last quarter's figures in one chart. Task: I was responsible for the accuracy of the monthly report. Action: I noticed the error an hour after sending. I called the client the same afternoon rather than waiting for them to find it, sent a corrected report with the changed chart highlighted, and explained what had happened. Then I added a final-check step to my own routine: I compare every chart's date range against the data source before sending. Result: The client thanked me for the quick correction and the error caused no decision to change. I have kept that checklist step since."
Why it works: the error is real and modest, the person owned it, and the fix is a process, not an excuse.
What are 12 common behavioral interview questions?
Grouped by what they test, with the type of story to use.
| Theme | Question | Story type |
|---|---|---|
| Teamwork | Tell me about a time you worked on a team that struggled | Group project with friction |
| Conflict | Describe a disagreement with a manager | Respectful pushback |
| Leadership | Tell me about a time you led without authority | Initiative on a project |
| Failure | Describe a project that failed | Honest post-mortem |
| Pressure | Tell me about a tight deadline | Prioritisation |
| Adaptability | Tell me about a time priorities changed suddenly | Re-planning |
| Initiative | Describe something you improved without being asked | Process fix |
| Customer focus | Tell me about a difficult customer | De-escalation |
| Ethics | Tell me about a time you had to say no | Boundary |
| Learning | Tell me about a time you learned a skill quickly | Self-study |
| Influence | Describe persuading someone with data | Analysis to decision |
| Ownership | Tell me about a time you took responsibility for a mistake | See example 2 |
How do I build a story bank?
- Open a document and list 8 to 10 situations from the last five years of work, study or volunteering. Include wins and one or two things that went wrong.
- For each, write four lines: S, T, A, R.
- Add a "number" line: any figure you can honestly state, such as hours saved, people helped or time to complete. If you have no number, describe the change in plain words. Do not invent figures.
- Tag each story with the themes above it could answer. A good story fits three or four.
- Keep your five strongest and rehearse them aloud.
What are common STAR mistakes?
- Too much situation. If the setup takes over a minute, trim it.
- "We" throughout. Say what you did. Credit the team separately.
- No result. If you cannot say how it ended, interviewers will not know whether it worked.
- A perfect story. A story with no friction sounds rehearsed. Show a real trade-off.
- A story from 15 years ago. Use recent examples when you can.
- Blaming others. Describe the disagreement fairly.
What if I have no work examples?
Use school projects, volunteering, community or family responsibilities (for example, managing a budget for an event). Choose examples where you faced a problem and made decisions. Say plainly where they come from. Interviewers judge the behaviour, not the setting.
How do I handle a question I have no story for?
Be honest: "I haven't faced that exactly, but here is the closest example", and give it. Or answer hypothetically: "What I would do is...", labelled as such. Do not invent an event.
Frequently asked questions
How long should a STAR answer be? Between 90 seconds and two minutes. Under a minute usually lacks detail; over two minutes loses the interviewer. Practise with a timer and keep Action the longest part.
Can I use the same story twice in one interview? Rarely, and only if it truly fits. Prepare five stories so you have variety. If you must repeat, emphasise a different aspect and say "this also relates to the earlier example".
Should I use STAR for every question? No. Use it for "tell me about a time" and "give an example" questions. Direct questions such as "why this company?" need a straight answer, not a story.
Is it bad if my result was negative? Not if you show what you learned and changed. Interviewers often rate honest failure stories higher than polished successes, because they show self-awareness.
Next step
Draft your five stories, then run through the common interview questions and your self-introduction. If you are preparing for engineering roles, see software engineer interview questions.
This page is general career information.