What are the 5 STAR interview questions?
There is no official list of five STAR questions. STAR is a way to structure an answer, not a set of questions. But five categories cover most of what interviewers actually ask. Prepare one story for each and you have covered most of a behavioral round. Those five are challenge, conflict, leadership, change, and improvement.
Quick Overview
| The question | What the interviewer is recording |
|---|---|
| A time you faced a major challenge | Whether you diagnosed the real cause |
| A time you worked with a difficult colleague | Whether you addressed it directly |
| A time you showed leadership | Whether you moved people without authority |
| A time you adapted to a big change | Whether you helped others adapt too |
| A time you improved a process | Whether you measured the improvement |
What STAR stands for
Situation, Task, Action, Result. You give the context, then your specific responsibility, then what you did, then what changed.
Most candidates spend too long on Situation and run out of time before Result. Aim for two sentences of context, one of responsibility, and four or five on your actions. Finish with one that has a number in it. The number is what makes the answer usable. The interviewer writes a summary afterwards and needs something concrete to record.
1. Tell me about a time you faced a major challenge
They want to know whether you found the real cause or just the first thing you saw.
Sample answer. Our checkout API started dropping requests during a holiday traffic spike. We were losing about 4 percent of orders at peak. I owned the payments service, so I took the investigation. The obvious answer was to add servers, but the error pattern did not match load. I traced it to connection pool exhaustion in the database client. I raised the pool size and added a circuit breaker, so a slow database could no longer take checkout down. We got the drop rate to 0.1 percent before the next spike, and it stayed there.
2. Describe a time you worked with a difficult team member
They are checking whether you handled it or waited for someone else to.
Sample answer. A senior engineer was holding my pull requests for about six days each. That was stalling a release we had committed to. I asked for a thirty minute call instead of arguing in review comments. It turned out he disagreed with a naming convention nobody had written down. We wrote it down, agreed on it, and circulated it to the team. Review turnaround dropped to under a day, and it stayed under a day for the rest of the project.
3. Tell me about a time you demonstrated leadership
Leadership here does not mean a title. They want to see you move people who do not report to you.
Sample answer. We had four months to migrate off an authentication service that was being retired. The work touched three teams, and none of them reported to me. I split it into three phases so each team could move independently. I wrote the migration guide and ran a fifteen minute check-in every week. We finished in nine weeks against a fourteen week estimate, with no authentication outages during the cutover.
4. Describe a time you had to adapt to a significant change
The weak version of this answer is that you accepted the change. The strong version is that you helped other people through it.
Sample answer. My team moved from quarterly releases to weekly ones, and the first month produced two failed releases. I volunteered to own the rollback path. I wrote a runbook and automated the smoke tests, so a bad release surfaced in about four minutes instead of a day. Then I walked each engineer through one rollback themselves. We had no failed releases in the following five months.
5. Tell me about a time you improved a process
This is the easiest of the five to answer well, because the result is usually already a number.
Sample answer. Our test suite took forty-seven minutes. Engineers stopped running it before pushing, so we caught failures late. I profiled it and found that two integration tests accounted for most of the time. I parallelized the suite and replaced those two with faster fakes. It came down to eleven minutes. That gave the team back roughly twenty engineer-hours a week, and moved failures back to before the merge.
Why STAR answers usually fail
- No number in the Result. "The project was a success" gives the interviewer nothing to write down.
- "We" instead of "I". The interviewer is scoring one person and cannot score a team.
- A hypothetical instead of an incident. "I would usually..." is not a story.
- Running out of time. Three minutes of context leaves no room for what you actually did.
How to Prepare
Write one story for each of the five categories. Each needs a specific situation, your own actions, and a result with a number. How to prepare for the behavioral interview walks through the process and is free to read.
Understand how the answer is graded. Your interviewer is assigned two or three named criteria and writes a summary afterwards. How behavioral interviews are scored explains what gets recorded.
Prepare for the follow-up. Every good STAR answer attracts one, usually about a tradeoff you made. See the hardest behavioral interview questions.
Know what sinks an answer. What you should not say in a behavioral interview covers the mistakes that cost the most.
Expect more than five questions. How many questions are asked in a behavioral interview sets the right expectation for a full round.
For the full treatment, Grokking Modern Behavioral Interview works through 30 questions with written sample answers and the follow-up each one attracts.
GET YOUR FREE
Coding Questions Catalog
$123
$197
$72
