“Tell me about a time” interview questions are behavioral questions that ask you to describe one specific thing you did in the past, so the interviewer can judge how you are likely to act in the job. The 40 below are the versions that come up most often, grouped by the skill they test; with 8 to 10 well-prepared stories you can answer nearly all of them.
Each question comes with what it really tests and a one-line STAR hint (Situation, Task, Action, Result). Most of them link to a full answer guide with three example answers we wrote. If STAR is new to you, start with our plain-English explanation of the STAR method, then come back to this list.
Why do interviewers ask “tell me about a time” questions?
Because past behavior is easier to check than promises. The US Office of Personnel Management's guidance on structured interviews describes behavioral questions as asking applicants “to describe a past behavior,” on the principle that “past behavior is the best predictor of future behavior.” The same page notes that interviews with more structure show higher validity, which is why many employers ask every candidate the same set of questions and score the answers against a guide.
In practice, that means three things for you:
- The interviewer wants one real event, not a habit. “I usually stay calm under pressure” does not answer “tell me about a time you were under pressure.” A specific Tuesday in March does.
- They are listening for your actions. Many scoring guides rate what you personally did, so “we decided” earns less credit than “I proposed, and the team agreed.”
- Follow-up questions are part of the question. Expect “what would you do differently?” or “how did you measure that?” after almost every story.
The STAR format itself has a long history in hiring. The consulting firm DDI says it introduced the STAR method in 1974 as part of its Targeted Selection interviewing system, and the structure is now standard advice from employers and career services alike.
How do you answer a “tell me about a time” question?
Use the same five-step frame for every question in this list:
- Pick a story that matches the skill, not just the words. A “difficult situation” question is testing composure and judgment, so choose a story where those were visible.
- Set the scene in two sentences. Your role, the team, what was at stake. Skip company history.
- Spend most of your time on the Action. Three or four specific steps you took, in order, with the reasoning behind each.
- Close with a measurable Result. A number, a date, a before-and-after, or a concrete change someone else noticed.
- Add one line on what you learned or would repeat, then stop and let the interviewer follow up.
Aim for roughly 1.5 to 2 minutes per answer; our guide on how long a STAR answer should be breaks that down by section. Some employers state an upper limit: Amazon's article on common interview mistakes says “Responses should be four minutes or less” (as of October 2026). To draft each story quickly, use our fill-in STAR method template.
The 40 most common “tell me about a time” questions
The groups below follow the competencies employers most often name in job descriptions and interview guides. The question wording varies (“describe a situation when…”, “give me an example of…”), but the skill being tested stays the same.
Problem solving and judgment (questions 1–7)
| Question | What it tests | STAR hint |
|---|---|---|
| 1. Tell me about a time you solved a difficult problem | How you diagnose, not just how you fix | Spend the Action on what you ruled out and why; end with the metric that recovered. |
| 2. Tell me about a time you made a difficult decision | Weighing trade-offs with incomplete information | Name the two options, the criteria you used and what you gave up. |
| 3. Tell me about a time you made an unpopular decision | Conviction plus bringing people along | Show you heard the objections, explained your reasoning and checked the result later. Use the difficult-decision guide above. |
| 4. Tell me about a time you used data to make a decision | Analytical rigor and honesty about limits | State the source, the method, one limitation and the decision the data changed. |
| 5. Tell me about a time you dealt with ambiguity | Making progress without full information | Clarify what you could, state your assumptions, test small, then adjust. |
| 6. Tell me about a time you were creative | Original thinking applied to a practical problem | Contrast the obvious approach with yours and show why yours worked better. |
| 7. Tell me about a time you took a risk | Calculated versus reckless risk | Show how you sized the downside and limited it before you acted. |
Ownership and drive (questions 8–14)
| Question | What it tests | STAR hint |
|---|---|---|
| 8. Tell me about a time you showed initiative | Spotting work nobody assigned | Explain how you noticed the gap and how you got buy-in before you started. |
| 9. Tell me about a time you went above and beyond | Impact beyond your role, and judgment about where extra effort matters | Lead with the outcome for the customer or team, not the hours you put in. |
| 10. Tell me about a time you improved a process | Continuous improvement | Give a before-and-after number and credit the people who adopted the change. |
| 11. Tell me about a time you set a goal and achieved it | Planning and follow-through | Make the goal measurable, name the milestones and show one adjustment you made midway. |
| 12. Tell me about a time you worked independently | Autonomy and keeping others informed | Show what you decided alone and how you kept stakeholders up to date. |
| 13. Tell me about a time you worked with limited resources | Resourcefulness and prioritizing | Say what you cut, what you reused and what the constraint pushed you to do better. |
| 14. Tell me about a time you had to learn something quickly | Learning speed and method | Describe your learning plan and the first real piece of work you delivered with the new skill. |
Resilience and accountability (questions 15–21)
| Question | What it tests | STAR hint |
|---|---|---|
| 15. Tell me about a time you failed | Ownership and growth | Own your decision in one sentence, then spend most of the time on what you changed. |
| 16. Tell me about a time you made a mistake | Honesty and speed of correction | Say how fast you raised it, how you fixed it and what safeguard you added. |
| 17. Tell me about a time you missed a deadline | Accountability and early warning | Show when you flagged the slip and what you did to limit the impact. |
| 18. Tell me about a time you received critical feedback | Coachability | Restate the feedback fairly, then show the change someone else noticed. |
| 19. Tell me about a time you handled a difficult situation | Composure and judgment | Pick a situation with real stakes and show the order in which you acted. |
| 20. Tell me about a time you worked under pressure | Performance when the stakes rise | Show how you triaged and protected quality, not just how hard you worked. |
| 21. Tell me about a time you adapted to change | Flexibility without resentment | Describe the change neutrally and show how quickly you were productive again. |
Prioritization and time management (questions 22–24)
| Question | What it tests | STAR hint |
|---|---|---|
| 22. Tell me about a time you met a tight deadline | Planning under time limits | Show what you cut or resequenced and how you protected quality. |
| 23. Tell me about a time you managed competing priorities | Prioritization logic | Name the method you used (impact versus effort, urgent versus important) and who you told about the trade-off. |
| 24. Tell me about a time you had to say no to a request | Protecting priorities without damaging the relationship | Explain the trade-off you shared and the alternative or later date you offered. The competing-priorities guide covers this. |
Communication and influence (questions 25–30)
| Question | What it tests | STAR hint |
|---|---|---|
| 25. Tell me about a time you persuaded someone | Influence without authority | Pair evidence with what the other person cared about. |
| 26. Tell me about a time you explained something complex | Audience awareness | Show the analogy or visual you used and how you checked they understood. |
| 27. Tell me about a time you presented to senior leaders | Brevity and decision-focused framing | Lead with the decision you needed and keep the detail for questions. Use the explaining-something-complex guide. |
| 28. Tell me about a time you delivered bad news | Candor and timing | Deliver it early, own your part and bring options, not just the problem. |
| 29. Tell me about a time you managed stakeholder expectations | Scope control and trust | Show how you set expectations up front and raised a change before it became a surprise. |
| 30. Tell me about a time you disagreed with your manager | Respectful pushback | Disagree with evidence, in private, then commit to the final decision. |
Teamwork and customers (questions 31–34)
| Question | What it tests | STAR hint |
|---|---|---|
| 31. Tell me about a conflict with a coworker | Resolving friction directly | Describe the other person fairly and focus on the conversation that resolved it. |
| 32. Tell me about a time you worked with someone whose style was different from yours | Flexibility and self-awareness | Name the specific difference and what you changed in your own approach. The coworker-conflict guide applies. |
| 33. Tell me about a time you worked with people from different backgrounds | Inclusion and collaboration | Show how different perspectives changed the outcome, without stereotyping anyone. |
| 34. Tell me about a time you handled a difficult customer | De-escalation and service | Acknowledge, find the real need, offer options, then follow up. |
Leadership and developing people (questions 35–39)
| Question | What it tests | STAR hint |
|---|---|---|
| 35. Tell me about a time you showed leadership | Leading people toward a goal | Show how you aligned people, not just that you were in charge. |
| 36. Tell me about a time you mentored someone | Developing others | Show coaching rather than doing it for them, and the mentee’s measurable growth. |
| 37. Tell me about a time you gave difficult feedback | Candor with care | Describe the specific behavior and its impact, then show what changed afterward. |
| 38. Tell me about a time you delegated a task | Trust and follow-up | Explain why that person, how you set them up and how you checked in without hovering. |
| 39. Tell me about a time you motivated a team | Purpose and energy | Tie the work to a goal the team cared about and show the result in output, not mood. Use the leadership guide. |
Integrity (question 40)
| Question | What it tests | STAR hint |
|---|---|---|
| 40. Tell me about a time you faced an ethical dilemma | Integrity and judgment about escalation | Show you used the right channel and keep confidential details out of the story. |
Which stories cover the most questions?
You do not need 40 stories. Most people can cover this list with 8 to 10, because one strong story usually answers two or three questions from different angles. A delayed launch you rescued can be a pressure story, a missed-deadline story or a stakeholder story depending on which part you emphasize.
| Story type to prepare | Questions it can answer |
|---|---|
| A project that went wrong and you recovered it | 15, 16, 17, 19, 20, 28 |
| Something you fixed or built that nobody asked for | 8, 9, 10, 6, 12 |
| A disagreement you resolved with a peer or manager | 25, 30, 31, 32 |
| A decision you made with incomplete data | 2, 3, 4, 5, 7 |
| A time you led or developed someone | 35, 36, 37, 38, 39 |
| A crunch with too much work and too little time | 13, 20, 22, 23, 24 |
| A hard conversation with a customer or stakeholder | 26, 28, 29, 34 |
| Something new you had to learn fast | 11, 14, 21 |
Write each story once in full, then note which question numbers it answers. Our interactive STAR story builder helps you draft a story section by section, and our guide to building a STAR story bank with AI shows prompts for mining your résumé for stories you have forgotten. For eight fully written stories across the core competencies, see our behavioral interview STAR examples.
What separates a weak answer from a strong one?
The same story can score very differently depending on how you tell it. These are the patterns that show up across every question in the list.
| Weak answer | Strong answer |
|---|---|
| Describes a habit: “I always communicate proactively.” | Describes one event: “In the second week of the migration, I noticed…” |
| Uses “we” throughout | Says what you did, and credits the team where it is due |
| Spends a minute on background | Sets the scene in two sentences and moves to the Action |
| Ends with “it went well” | Ends with a number, a date or a visible change |
| Picks a story with no real stakes | Picks a story where the outcome could have gone the other way |
| Blames a colleague or a previous employer | Describes others fairly and owns your part |
| Runs four or five minutes without a pause | Finishes in about two minutes and invites follow-up |
If you tend to run long, our guide on how to stop rambling in interviews has drills for tightening an answer. For the wider question set that sits alongside these (“tell me about yourself,” “why this company”), see common interview questions and answers.
How should you prepare in the week before the interview?
A focused week is enough for most candidates. Here is a schedule that works around a full-time job:
- Day 1: Read the job description and circle the 4–6 skills it stresses. Match each one to a group above.
- Day 2: List 10–12 candidate stories from your last few years of work. Do not write them yet; just name them.
- Day 3: Pick the best 8 and write each one in STAR form. Keep each to about 250–300 words.
- Day 4: Map the stories to question numbers using the story-type table. Fill any gaps.
- Day 5: Say each story out loud with a timer. Cut anything past two minutes.
- Day 6: Practice the likely follow-ups: “what would you do differently?”, “what was the hardest part?”, “how did you measure it?”
- Day 7: A full mock run with someone (or something) that interrupts you with follow-ups.
For a broader plan covering research, logistics and the questions you ask, see how to prepare for a behavioral interview.
Practice it
Reading a list builds recognition; answering out loud builds recall. Rehearse with an AI mock interview built from your résumé and the job description: CoPilot Interview's desktop AI interview assistant reads each behavioral question aloud, listens to your spoken answer and scores it out of 10 with what worked, what to fix and a model answer, then gives you a report card at the end. Pick 5 questions from the groups that match your target role and run them until every score holds steady.
The free plan gives you 15 minutes a day with no account and no credit card. Use AI to prepare beforehand, and follow each employer's rules about AI use in the interview itself.
Rehearse your “tell me about a time” stories out loud
Answer real behavioral questions, get each answer scored out of 10 with what to fix, and see a model answer. Nothing to install.
Try a free AI mock interviewFAQ
How many “tell me about a time” stories should I prepare?
Prepare 8 to 10 well-practiced stories. One strong story can usually answer two or three different questions, so that set covers nearly all of the 40 questions on this list. Keep two stories for the skills the job description stresses most.
Can I use the same story for more than one question?
Yes, as long as you emphasize the part that matches the question. A rescued project can show pressure handling in one answer and stakeholder management in another. Avoid telling the identical story to the same interviewer twice.
What if I do not have an example for a question?
Say you will take a moment, then choose the closest real example, including school, volunteer or side-project work if needed. If you truly have none, explain briefly how you would approach it and what similar experience you do have. Never invent a story.
Are “tell me about a time” and “describe a situation when” the same question?
Yes. Both are behavioral questions asking for a specific past event, and the STAR structure works for both. “What would you do if” is different: it is a situational question about a hypothetical future event.
How long should each answer be?
About 1.5 to 2 minutes is common guidance, which leaves time for follow-up questions. Amazon's published interview advice sets an upper limit of four minutes per response.
Should I memorize my STAR answers word for word?
No. Memorize the structure and the key facts, such as the numbers and the order of your actions, but say it in fresh words each time. Word-for-word answers tend to sound rehearsed and fall apart when the interviewer interrupts with a follow-up.