What is an example of a strong STAR answer?

A strong STAR answer names a specific, checkable situation (company, timeframe, stakes), claims a clear personal task, walks through the candidate's own decisions in the action, and closes with a measured result — including honest mixed outcomes. Example skeleton: 'Last year our biggest client threatened to churn (S). Retention was my number (T). I rebuilt the onboarding in three weeks and called the client weekly myself (A). They renewed at a 10% discount and referred two accounts; the discount taught us to fix onboarding before renewal season (R).'

How should interviewers score STAR answers?

Component by component against the role's scorecard: was the situation real and specific, was the candidate's own responsibility clear, did the action contain their decisions (not the team's activities), and was the result measurable? Red flags: 'we' throughout, adjective-actions ('I drove alignment'), numberless results, and stories that always end in triumph. Consistent teams require quoted evidence for each rating.

How many STAR questions should one interview include?

Four to six, with two or three follow-ups each. Depth beats coverage: a rehearsed story survives one question but rarely survives a third follow-up about names, numbers, and sequence from the candidate's own life.

35 STAR Interview Questions (With Sample Answers and Scoring)

Q: What are STAR interview questions?

STAR interview questions are behavioral prompts — 'tell me about a time when…', 'describe a situation where…' — designed to be answered in Situation-Task-Action-Result structure. They ask for a real event from the candidate's history rather than a hypothetical, because examined past behavior is the strongest predictor of future performance.

By the Topgrading AI team · Last updated October 20, 2026

Thirty-five STAR interview questions organized by competency, each group with a model STAR-structured sample answer — and the part other guides skip: how an interviewer actually scores the answer. Use it from either side of the table.

Quick refresher before the list: STAR answers cover Situation, Task, Action, Result — a real event, the candidate's own responsibility, their specific decisions, and a measurable outcome. The full mechanics (including the AI-rehearsal problem and follow-up strategy) live in our complete STAR Method guide; this page is the question bank.

Problem-solving (questions 1–6)

Tell me about the hardest problem you solved in the past year.
Describe a time you found the root cause of something everyone else misread.
Walk me through a decision you made with incomplete information.
Tell me about a time your first solution failed. What did you do next?
Describe a problem you solved with far fewer resources than you needed.
Tell me about a time you had to choose between two bad options.

Sample answer (question 4)

"Our checkout error rate doubled after a release (S). I owned payments reliability, so the rollback call was mine (T). My first fix — reverting the release — didn't clear it, which told me the trigger was data, not code. I traced it to a currency edge case from a new market, wrote the patch, and added that market's test cases to CI (A). Error rate back to baseline in two days; the test suite caught the same class of bug twice in the next quarter (R)."

How an interviewer scores this: the failed first attempt is a feature, not a flaw — it shows diagnosis under pressure. Score up: specific trigger, personal ownership of the rollback call, a prevention step with later proof. Follow up with: "which market, and who found it first — you or support?"

Ownership & accountability (7–12)

Tell me about a goal you missed. What happened next?
Describe a time you took responsibility for a failure that wasn't entirely yours.
Tell me about a commitment you made that you couldn't keep.
Describe the project you're proudest of owning end to end.
Tell me about a time you caught your own mistake before anyone else did.
When did you last do work that was nobody's job?

Sample answer (question 7)

"I committed to migrating 40 enterprise accounts by Q3 (S). The number was mine — I'd scoped it (T). By July we were at 19, and the blocker was my own scoping: I'd assumed self-serve migration for accounts that needed hand-holding. I told my VP before she asked, re-forecast at 28, and built a white-glove track for the ten biggest (A). We landed 27 — a miss against 40, honest against 28, and zero churned accounts during migration (R)."

How an interviewer scores this: self-reported misses with the candidate's own error named are the highest-trust answers in an interview. Score up: proactive escalation, a re-forecast they then hit, a retained-customer result. Red flag in this category: candidates whose misses are always someone else's fault.

Teamwork & conflict (13–18)

Tell me about your most serious disagreement with a colleague. How did it end?
Describe a time you were wrong in a team debate.
Tell me about working with someone whose style clashed with yours.
Describe a time you had to deliver hard feedback to a peer.
Tell me about a team decision you disagreed with but had to execute.
When did you last change a teammate's mind without authority over them?

Sample answer (question 17)

"Leadership chose to sunset a feature my team built and my biggest customer used (S). I was the one who had to make it happen and keep the account (T). I argued my case in the decision meeting, lost on the data — the feature served 3% of revenue and ate 15% of support load — and then executed like it was my idea: I called the customer personally, built their migration plan, and never mentioned I'd opposed it (A). Account renewed; my team saw that losing a debate doesn't mean sulking through execution (R)."

How an interviewer scores this: "disagree and commit" stories separate operators from politicians. Score up: argued with data, lost gracefully, executed fully, protected the team's morale. Follow up: "what would have had to be true for you to escalate instead?"

Communication & influence (19–24)

Tell me about a time you had to explain something complex to a skeptical audience.
Describe a time you delivered news nobody wanted to hear.
Tell me about persuading a senior stakeholder to reverse a decision.
Describe a misunderstanding that cost your team time. What caused it?
Tell me about tailoring the same message to two very different audiences.
When did you last choose NOT to communicate something, and why?

Sample answer (question 20)

"Three weeks before launch I found our headline feature wouldn't ship (S). As the PM, the announcement was mine to make (T). I wrote a one-pager first — what broke, three options, my recommendation to cut scope rather than slip the date — and presented it to sales and the exec team the same morning so nobody heard it secondhand (A). We shipped on time minus the feature, sales had honest talking points a day later, and the feature landed six weeks after with zero lost deals we could trace (R)."

How an interviewer scores this: bad news delivered fast, with options, to everyone at once — that's the whole competency. Score up: the one-pager (structure under stress), same-day delivery, a recommendation rather than a menu. Red flag: answers where the hard message got softened into mush.

Adaptability & pressure (25–30)

Tell me about a time priorities changed overnight.
Describe the most pressure you've worked under. What did it change in your behavior?
Tell me about learning a skill quickly because the job demanded it.
Describe a time a project was cancelled after you'd invested heavily.
Tell me about performing well outside your comfort zone.
When did a sudden constraint actually improve your work?

Sample answer (question 25)

"Monday we lost our biggest reseller; by Wednesday leadership pivoted the quarter to direct sales (S). My onboarding roadmap was suddenly irrelevant — my new job was a direct-signup flow in six weeks (T). I killed three projects publicly so my team didn't try to do everything, moved our best engineer to the signup flow, and set a weekly demo so the pivot stayed visible (A). The flow shipped in five weeks; direct signups covered 60% of the reseller gap by quarter-end (R)."

How an interviewer scores this: adaptability isn't enthusiasm — it's what you stopped doing. Score up: killing projects explicitly, resource reallocation, a cadence that kept the team oriented. Follow up: "which three projects, and who pushed back?"

Leadership & initiative (31–35)

Tell me about a time you led without formal authority.
Describe spotting a problem early that others dismissed.
Tell me about developing someone who went on to outgrow the role.
Describe starting something from nothing that still exists today.
What's a standard you raised that outlasted your tenure?

Sample answer (question 32)

"In February I flagged that our two biggest customers' usage had quietly dropped 30% (S). Nobody owned 'usage watching' — I did it off the side of my desk (T). I built a five-line weekly report, took it to the account team, and pushed for check-in calls that surfaced a pricing complaint we'd never heard (A). Both accounts renewed after a plan restructure; the usage report became the CS team's standard dashboard and still runs (R)."

How an interviewer scores this: initiative that becomes infrastructure is the strongest version of this competency. Score up: unprompted detection, a lightweight artifact, an outcome that survived them. For leadership roles, pair this bank with our 50+ leadership interview questions.

Using this bank well

Interviewers: pick 4–6 questions mapped to the role's scorecard, drill each with two or three follow-ups, and score components against the same written bar for every candidate — the mechanics are in the STAR guide's scoring section and the panel interview guide. Rehearsed answers (human- or AI-written) survive one question, not three follow-ups.
Candidates: don't script 35 answers. Bank 6–8 real events deeply enough to answer any follow-up honestly — every sample above works because it's specific, checkable, and owns a flaw.

Frequently asked questions

What are STAR interview questions?

Behavioral prompts ("tell me about a time when…") designed to be answered in Situation-Task-Action-Result structure — real events from the candidate's history, because examined past behavior is the strongest predictor of future performance.

What makes a STAR answer strong?

A checkable situation, a clearly owned task, decisions (not activities) in the action, and a measured result — including honest mixed outcomes. Specificity is the signal; polish isn't.

How do interviewers score STAR answers?

Component by component against the role's scorecard, with quoted evidence per rating. Red flags: "we" throughout, adjective-actions, numberless results, perfect endings everywhere.

How many STAR questions per interview?

Four to six with follow-ups beats fifteen asked once. Depth produces signal; coverage produces transcripts.

Ask from this bank. Score with the same bar.

Topgrading AI generates scorecard-driven questions per candidate and scores every transcript with verbatim evidence.

See your first scorecard free

10 free credits · no card required · read the full STAR guide