how to answer tell me about a time you solved a difficult problem

by Wistkey · 13 august 2026 · 6 min read

this question is not really asking whether the problem disappeared. it is asking whether you can think clearly when the answer is not obvious. a strong response makes your judgement visible: what you noticed, how you found the cause, why you chose one route and what changed afterwards.

what the interviewer wants to hear

problem solving is more than reacting quickly. the interviewer wants evidence that you can understand an unclear situation, separate symptoms from causes, weigh up options and take useful action. your result matters, but the route to that result is the part that reveals how you work.

this is why a vague line such as we had an issue, so i spoke to the team and fixed it feels thin. it hides the decisions. instead, show what information you gathered, which constraint mattered most and why your solution made sense.

the civil service behaviours guidance describes effective decisions as using evidence and knowledge while considering options, implications and risks. that is a useful checklist even when you are not applying for a civil service role.

choose a problem with a real decision inside it

pick an example where the answer was not obvious at the start. the problem does not need to be dramatic. a missed handover, a recurring customer error, an unreliable process or a project blocked by incomplete information can all work well if your thinking changed the outcome.

look for an example with four ingredients:

• a clear consequence — what could have been delayed, lost or made harder?
• some uncertainty — what did you need to discover before acting?
• your own judgement — which choice did you make, and why?
• a checkable result — how did you know the fix worked?

if you have little paid experience, use a genuine example from study, volunteering, caring responsibilities or a personal project. the national careers service says examples can come from outside work when you do not have much work history. what matters is that the story is relevant and truthful.

structure it as problem, evidence, choice, result

the star method is useful, but a problem-solving answer needs extra detail in the middle. use these four beats to keep that detail focused:

• problem — give just enough context to explain what was wrong and why it mattered.
• evidence — show how you investigated. mention the data, observations or conversations that helped you find the real cause.
• choice — explain the options you considered, the trade-off you made and the action you personally took.
• result — state what changed, how you checked it and what you learnt or improved for next time.

keep the problem short enough that most of your answer is about evidence and choice. saying i checked the last four handovers and noticed every delay began when one field was left blank shows more problem-solving ability than spending a minute describing how frustrating the delays were.

make your individual contribution easy to hear

you can describe a team problem without claiming the whole solution. use we for the shared goal, then switch to i for your investigation, recommendation or action. name the people you consulted and what their input changed. that shows collaboration without making your role disappear.

avoid unexplained technical detail. an interviewer outside your specialism still needs to follow the logic. the university of cambridge careers service recommends a context, action, results structure for competency questions and stresses that how you say something can matter as much as the content. translate the problem into plain language, then lead the listener through one decision at a time.

an adaptable example answer

adapt this shape to a real experience; do not learn the wording as a script.

"during a community event project, registrations were being confirmed late, which meant volunteers did not know how many people to prepare for. i first compared the registration list with the confirmation emails and found that entries from one form were being copied across manually. i considered adding another person to the task, but that would still leave the same source of error. instead, i created a simple shared checklist, made one person responsible for the final check each day and tested the process on the next batch. confirmations went out on time for the remaining sessions, and the checklist was kept for future events. i learnt to test the process before assuming the problem is a lack of effort."

notice that the example does not pretend to be heroic. it shows a consequence, an investigation, a rejected option, a reasoned action and a result. replace each detail with evidence from your own experience.

practise the reasoning, not a script

write the four headings on a page and put two or three prompt words under each. then answer aloud without reading full sentences. aim for roughly two minutes, but let the complexity of the example decide the exact length.

listen for the point where your explanation becomes hard to follow. if you spend too long setting the scene, cut context. if the solution seems to appear by magic, add the evidence that led you there. if you say we throughout, clarify your contribution. the national careers service interview guidance recommends preparing examples and practising answers with the star method; speaking the answer aloud also helps you hear whether the logic is clear.

finish with proof and reflection

do not end at and then we solved it. give the interviewer a sign that the result held: fewer repeat errors, an agreed deadline met, a process adopted or positive feedback from the people affected. use a number only when it is real and you can explain it.

add one brief reflection. perhaps you learnt to verify assumptions earlier, involve a specialist sooner or test a small change before rolling it out. reflection turns a tidy success story into evidence that your problem-solving approach keeps improving.