A strong answer to “Tell me about a time you solved a problem” shows how you think, not just that the problem went away. Interviewers want to hear how you worked out what was really wrong, what options you considered, why you chose one, and how you checked it worked. Use the checklist below to build and test your story, then compare it with the annotated example.
What the question is measuring
Problem solving is near the top of most employers’ lists. The World Economic Forum’s Future of Jobs Report 2025 found that analytical thinking “remains the most sought-after core skill among employers”, with seven in ten companies considering it essential in 2025. NACE, the US body that defines career-readiness competencies for graduates, describes critical thinking as the ability to “identify and respond to needs based upon an understanding of situational context and logical analysis of relevant information”.
A useful way to think about what interviewers listen for comes from ASQ, the quality professionals’ association. It describes problem solving in four steps: “Define the problem”, “Diagnose the root cause”, “Identify and implement a solution” and “Sustain the results”. Most weak answers jump straight to step three.
Checklist 1: Choosing your example
Tick at least four of these before you commit to a story.
- The problem was real and had a cost: lost time, money, customers, accuracy or safety.
- The cause was not obvious at first. You had to investigate.
- You personally did the diagnosis or proposed the fix.
- You considered more than one option.
- You can describe a measurable before and after, even roughly.
- The problem is relevant to the job you want (technical for technical roles, customer-facing for service roles).
- You can tell it without blaming a named colleague.
Avoid problems that were solved by working longer hours, or that someone else diagnosed and you only carried out the instructions. If your best story is about a sudden emergency, it may suit a crisis question better; if it is about making a working routine faster, it may suit a process-improvement question. For this question, choose one where finding the cause was the hard part.
Checklist 2: Defining the problem
- State the problem in one sentence, in terms of its effect. “Customer refunds were taking twelve days instead of five” is better than “The refund system was bad.”
- Say who was affected and how you found out.
- Mention any early assumption that turned out to be wrong. It shows you tested your thinking.
Checklist 3: Diagnosing the cause
This is where most marks are won. ASQ advises problem solvers to “discover underlying causes so the focus is on the problem, not just its symptoms”. The Lean Enterprise Institute describes the “5 Whys” practice of asking why repeatedly to get past the symptom, citing an example given by Taiichi Ohno.
- Describe what information you gathered: records, logs, conversations with the people involved, observation.
- Name the tool or method if you used one (a spreadsheet analysis, a fault log, a 5 Whys exercise, a customer survey) but don’t let the jargon replace the story.
- Explain how you ruled out at least one plausible cause.
- Say what the actual cause turned out to be.
Checklist 4: Choosing and applying the solution
- Mention the alternatives. ASQ recommends that you “postpone selecting one solution until several alternatives have been proposed”. Interviewers notice when a candidate weighed options.
- Give your reason for the choice: cost, speed, risk, or what the people affected could realistically adopt.
- Say who you needed to involve and how you got their agreement.
- If you tested on a small scale first, say so.
Checklist 5: Results and follow-through
- Give a number if you have one. If you don’t, describe a clear observable change.
- Explain how the fix was made to last: a new check, a changed form, an updated procedure, training.
- End with one line about what you learned or would do differently.
The National Careers Service’s STAR guidance describes the result as “what happened as a result of your action and what you learned from the experience”. Both halves count.
An annotated example
The answer below is illustrative, written for a customer service or operations role. The notes in brackets map it to the four ASQ steps.
“I worked in the customer support team of an online retailer. Over about six weeks, our complaints about late refunds roughly doubled. My team leader assumed we were short-staffed, and the first suggestion was to add overtime. [Define: the effect, and an assumption to test.]
Before we did that, I asked if I could look at the refund records. I exported two months of refund tickets and sorted them by how long each stage took. Our team was processing refunds within two days, so staffing wasn’t the issue. The delay was at the warehouse stage: returns were sitting for over a week before being marked as received. I visited the returns desk and found that parcels without a printed return label had to be matched manually, and those were being left until the end of the week. [Diagnose: data, observation, and a cause ruled out.]
We looked at three options: adding staff to the returns desk, changing the matching process, or making it harder to send a return without a label. I suggested the third, because it fixed the cause rather than the backlog. I worked with the website team to add a clear step in the returns email asking customers to include the label, and the warehouse supervisor agreed to process unlabelled returns daily instead of weekly. [Identify and implement: alternatives, a reason for the choice, agreement from other teams.]
Within the next month, average refund time came back under our five-day target, and complaints dropped to their earlier level. I set up a weekly check of the refund report so we would see the next problem earlier. What I learned was to look at the data before accepting the first explanation. [Sustain: result, a lasting check, and a lesson.]“
Adapting the answer to your field
| Role type | Good problem to use | Evidence that impresses |
|---|---|---|
| IT support | An intermittent fault affecting several users | How you reproduced it, logs checked, what you ruled out |
| Finance | A recurring reconciliation difference | Tracing the entries, the control you added |
| Engineering or site work | A recurring defect or delay | Inspection findings, the fix, and safety considerations |
| Teaching | A class or pupil not progressing | What the assessment data showed, what you changed |
| Sales or marketing | A drop in conversion or leads | Where in the funnel the drop appeared, the test you ran |
Role-specific examples also strengthen your CV. Browse resume examples to see how problem-solving achievements are phrased for different jobs, or start from one of the resume builders by role.
Last check before the interview
- Can you say the problem in one sentence?
- Does at least half the answer cover diagnosis and choice?
- Have you mentioned an alternative you rejected?
- Is there a result and a way it was sustained?
- Can you tell it in under two minutes?
- Are you ready for “What would you have done if that hadn’t worked?”
Frequently asked questions
Does the problem have to be technical?
No. A scheduling clash, a customer misunderstanding or a recurring error on a form can all work. What matters is that you can show the reasoning steps.
What if the solution was a team effort?
Say so, then focus on your part. Use “I” for your own actions, such as gathering the data or proposing the option, and “we” for what the group did.
Can I use a problem I didn’t fully solve?
Yes, if your diagnosis was sound and you can explain what limited the result. Be honest about it, and say what you would do next.
Should I mention formal methods like root cause analysis?
If you used them, briefly. Interviewers care more about the thinking than the label, so describe what you actually did.
Sources
- The Future of Jobs Report 2025: Digest, World Economic Forum (checked 2026-11-03)
- Career Readiness Defined, National Association of Colleges and Employers (NACE) (checked 2026-11-03)
- What is Problem Solving? Steps, Process and Techniques, ASQ (checked 2026-11-03)
- 5 Whys, Lean Enterprise Institute (checked 2026-11-03)
- The STAR method, National Careers Service (checked 2026-11-03)