Behavioural · UK 2026
How to answer "Tell me about a challenge you overcame"
Interviewers also phrase it as:
- "Describe a difficult situation at work"
- "Tell me about a time you faced a setback"
- "Walk me through a tough problem you solved"
Why interviewers ask
Behavioural question testing problem-solving, resilience, and self-awareness. Interviewers use STAR (Situation, Task, Action, Result) to score these answers. Strong answers spend most of the time on Action (what you specifically did) and Result (with quantified outcomes). Weak answers spend most of the time on Situation (extended scene-setting) and dilute the Action with team-vs-individual ambiguity.
Model answer
About [time period] ago at [current/previous company], we ran into [specific challenge — concrete enough to be vivid]. The reason it was difficult was [non-obvious complicating factor — political, technical, time-pressured]. My role specifically was to [your accountability]. I [specific actions you took, in sequence]. The outcome was [specific quantified result] within [timeframe]. The lesson I took from it was [self-aware reflection on what you'd do differently].
What to avoid (common bad answer)
We had a really tough project last year where the deadline was tight and the team was stretched. We all worked really hard and pulled together and managed to deliver. (Vague situation, vague action, vague outcome — STAR violation.) Or: A few years ago I had to [extended setup for 2 minutes] and then... the result was good. (Action and Result compressed into nothing.) Both fail.
Structure of a good answer
- 1 Situation: 15-20 seconds — what was happening and why it was hard
- 2 Task: 10 seconds — what you specifically were responsible for
- 3 Action: 50-60% of the answer — what you specifically did, step by step
- 4 Result: 15-20 seconds — quantified outcome and timing
- 5 Optional reflection: 10 seconds — what you learned
Common mistakes
- ✗ Spending 80% on Situation and rushing the Action — common STAR failure
- ✗ Using 'we' instead of 'I' for the Action — interviewers want individual contribution
- ✗ No quantified result — flags story without substance
- ✗ Picking a challenge that's too small to be impressive
- ✗ Picking a challenge where the resolution wasn't really yours
Recruiter pro tip
Prepare 4-6 STAR stories before any interview, each demonstrating a different competency: leadership, conflict resolution, technical depth, ambiguity tolerance, stakeholder management, customer focus. Most behavioural questions can be answered with one of these. The candidates who land behavioural questions well aren't generating answers from scratch — they're matching prepared stories to the question being asked.
FAQ
How long should each STAR answer be? ▼
90 seconds to 2 minutes maximum. Past 2 minutes and you've lost the structure.
Should the challenge be technical or interpersonal? ▼
Match the role. Technical challenges for engineering interviews, interpersonal/political for management interviews. Mixed for senior IC roles.
Can I use a challenge I didn't fully solve? ▼
Yes, if you handled it well even though the outcome wasn't ideal. Be honest: 'The result was X — not what we wanted, but the lesson I took was...'