The short answer: when an interviewer asks about a time you overcame an obstacle, a setback or a time things didn’t go to plan, they want to know how you respond when work gets hard: whether you stay calm, take ownership, find a way forward and learn from it. Pick a real, work-relevant obstacle with a clear result, tell it with the STAR method (situation, task, action, result), spend most of your time on what you did, and finish with what you learned or changed. Keep it to about two minutes.
Sample answers are illustrations, not quotes from real candidates.
Why interviewers ask about resilience
Employers rank resilience highly. In the World Economic Forum’s Future of Jobs Report 2025, “resilience, flexibility and agility” was the second most important core skill for workers, after analytical thinking: 67% of employers surveyed considered it a core skill. It’s also among the skills employers expect to grow in importance through 2030.
In an interview, resilience questions check four things:
- Composure: do you stay steady under pressure?
- Ownership: do you take responsibility instead of blaming others?
- Problem-solving: do you find a practical way forward?
- Learning: do you come out of it better?
Common resilience interview questions
- “Tell me about a time you overcame an obstacle.”
- “Tell me about a setback and how you handled it.”
- “Describe a time you faced a major challenge at work.”
- “Tell me about a time you failed.” (See our guide to answering “Tell me about a time you failed”.)
- “How do you handle pressure?” or “How do you handle stress?” (See how to answer “How do you handle stress?”.)
- “Tell me about a time a project didn’t go as planned.”
- “How do you bounce back from rejection?”
- “Describe the most difficult period in your career so far.”
How to choose your story
A good obstacle story has:
- A real obstacle: a tight deadline with a key person out, a lost client, a failed launch, a budget cut, a skill you had to learn fast. Small and real beats big and vague.
- Your actions at the center: what you did, not just what the team did.
- A result: ideally measurable, or at least clear.
- Relevance: pressure the job you want will also involve.
Be careful with very personal stories (illness, bereavement, family crises). They can show resilience, but you don’t have to share them, and if you do, keep the focus on how you handled your work and keep the details brief.
How to structure your answer (STAR + learning)
| Step | What to say | Time |
|---|---|---|
| Situation | The context and the obstacle, in two or three sentences | 15 to 20 seconds |
| Task | What you were responsible for | 10 seconds |
| Action | What you did, step by step, including how you kept going | 60 seconds |
| Result | The outcome, with a number if possible | 15 to 20 seconds |
| Learning | What you learned or now do differently | 10 to 15 seconds |
Our STAR method guide goes deeper.
Example answers
1. A project obstacle
“Two weeks before a product launch, our lead engineer left the company. I was the project manager, and the launch was tied to a contract renewal. I met the remaining engineers the same day to list what was left, cut two non-essential features with the client’s agreement, brought in a contractor for the integration work, and set up a 15-minute daily check-in to catch blockers early. We launched four days late but with the core features working, and the client renewed. Since then, I make sure every critical area of a project has a second person who knows it.”
2. Losing a big client
“In my second year in sales, I lost my largest account, about 30% of my quota, when they were acquired. My task was to still hit my annual target. I went back to my pipeline, ranked accounts by likelihood and size, asked my manager to review my approach to two stalled deals, and doubled my weekly outreach. I finished the year at 104% of quota, and I now keep any single client below a fifth of my book where I can.”
3. A rejection or setback
“I applied for a team lead role internally and didn’t get it. The feedback was that I hadn’t shown I could coach others. I asked my manager for two junior analysts to mentor, ran our team’s onboarding for new hires, and asked for feedback every quarter. Ten months later I was promoted to lead when the next role opened. The rejection was useful because it told me exactly what to work on.”
4. Learning something fast
“Our team moved to a new data platform with a one-month deadline, and I had never used it. I did the vendor’s training in the first week, rebuilt one of our smaller reports as a test, and paired with a colleague from another team who already used it. I migrated all twelve of my reports on time and wrote a short guide that the rest of the team used.” For more, see our adaptability interview questions guide.
5. Student or new graduate
“In my final year, my group’s research participant pool fell through three weeks before our deadline. I was coordinating the project. I contacted two student societies and a local community center, rewrote our recruitment message to take five minutes to read instead of fifteen, and split the interviews across all four of us. We reached 40 participants instead of the planned 50, explained the limitation in our report, and got an A.”
6. Career changer
“Moving from teaching into instructional design, I was turned down for my first eight applications because I had no corporate portfolio. I built three sample courses for real problems, including one for a local nonprofit’s volunteer training, and asked designers on LinkedIn for feedback. My ninth application turned into an offer, and the nonprofit course was the main thing the hiring manager asked about.”
7. Leading a team through a hard period
“After a reorganization cut our team from eight to five, morale dropped and our backlog grew. As the manager, I met everyone one to one to hear their concerns, agreed with leadership which projects to pause, and set a clear priority list so people weren’t trying to do everything. Within two months our backlog was back under control, and no one else left that year.”
Mistakes to avoid
- Blaming others: describe the obstacle factually, even if someone else caused it.
- A story with no result: always say how it ended.
- A trivial obstacle: “My printer broke before a meeting” doesn’t show much.
- An unresolved crisis: choose something you’ve come through, not something you’re still struggling with.
- Making yourself the hero of everything: credit the team, but be clear about your part.
- Skipping the learning: the last line is what makes the story about growth.
How to prepare
- Write down three or four obstacle stories: a project problem, a setback or rejection, learning something fast, and a team challenge.
- Add numbers: time, money, percentages, people.
- Practice out loud until each one is about two minutes. For more examples of challenge stories, see how to describe a challenging project.
Frequently asked questions
How do you answer "Tell me about a time you overcame an obstacle"?
What are resilience interview questions?
What is a good example of overcoming an obstacle at work?
Can I use a personal challenge as a resilience example?
Why do employers ask about resilience?
Sources
- World Economic Forum, The Future of Jobs Report 2025 (PDF), January 2025. Read on 2 October 2026.
