Problem-solving interview questions: show how you think, not just what you decided.
Problem-solving questions ask you to describe a problem you solved, or to work through one on the spot. In both cases, the reasoning matters as much as the answer: how you defined the problem, what information you gathered and how you chose between options.
Answer problem-solving questions by making your thinking visible: define the problem, explain how you found its cause, list the options you considered, say why you chose one, and describe the result and what you would do differently. Use a real example where you can. For a live puzzle or case, think out loud, state your assumptions and check your answer before you finish.
Five steps to talk through any problem
- Define the problem. Say what was actually wrong, and how you knew. A clear definition is often the most impressive part of the answer.
- Find the cause. Explain what information you gathered and how you narrowed it down, rather than jumping to a fix.
- Consider options. Name two or three possible solutions and the trade-offs between them: time, cost, risk, people.
- Decide and act. Say which option you chose, why, and what you did to put it in place.
- Check and learn. Describe how you confirmed it worked and what you would do differently next time.
Two kinds of problem-solving question
- Past problems. “Tell me about a difficult problem you solved.” Use a real story, with the five steps as the backbone.
- Live problems. A scenario, estimate or case to work through in the interview. Think out loud, ask clarifying questions and state assumptions. Getting a reasonable structure matters more than a perfect number.
- Technical problems. For technical roles, the problem may be specific to the field. The same habits apply: clarify, structure, check.
Choosing a good problem story
| A good story has | Why it helps | Avoid |
|---|---|---|
| A problem that mattered | Shows judgement about what is worth solving | Trivial problems with obvious answers |
| A cause that was not obvious | Lets you show your investigation | Stories where the fix was handed to you |
| More than one possible solution | Lets you show how you weighed options | Stories with only one path |
| A clear result | Shows the outcome of your thinking | Stories that end before anything changed |
| A lesson | Shows reflection | Claiming everything went perfectly |
Illustrative answers to adapt
Illustrative: these answers were written by TryHired to show structure. They are not real candidates' answers and were not given in any real interview. Every name, employer, number and result is fictional or a bracketed placeholder: replace each bracket with your own true details, and never claim an achievement you did not have.
Problem story template
When to use: “Tell me about a problem you solved.”
At [Employer or school], [the problem, in one sentence, and how you noticed it]. To find the cause, I [what you checked or asked], and it turned out [the cause]. I considered [option one] and [option two]; I chose [the option] because [the trade-off]. I [what you did], and [the result you can prove]. Next time I'd [what you would change].
“Tell me about a problem you solved.” (weak)
What it shows: Jumps to the fix with no reasoning.
There was a problem with our system once, so I fixed it. I'm good at solving problems because I think outside the box and I don't give up.
“Tell me about a problem you solved.” (stronger)
What it shows: Thinking made visible.
At [Employer], customers kept receiving [the wrong item or information], and complaints were rising. I pulled the recent cases and noticed they all came through [one channel or step]. I could either add a manual check or fix the [form or process] that caused it; the manual check was faster but wouldn't last, so I proposed the fix and added the check as a stopgap. After the change, [result you can prove]. I'd now involve the [team that owns the process] earlier.
Why the stronger answer works: The weak answer names a problem and a fix and nothing in between, so the interviewer learns nothing about how the speaker thinks. The stronger answer defines the problem, shows the investigation, weighs two options and explains the choice. The answers are illustrative; use your own case and results.
Disclosure: TryHired makes HIRED, a paid job-search program, so we have a conflict of interest when we mention it. Every sample on this page is free to use without buying anything.
General practice questions
General practice questions, not a prediction of what any employer will ask.
| Practice question | What it explores |
|---|---|
| Tell me about a difficult problem you solved. | Reasoning |
| Describe a time you found the root cause of a recurring issue. | Investigation |
| Tell me about a decision you made with incomplete information. | Judgement |
| How do you approach a problem you have never seen before? | Method |
| Describe a time your first solution didn't work. | Resilience |
| Tell me about a time you simplified a process. | Improvement |
Mistakes to avoid
- Jumping straight to the solution without explaining the problem.
- Describing a problem someone else solved.
- Ignoring the trade-offs of your choice.
- Staying silent while you think through a live problem.
- Using clichés such as “I think outside the box” instead of evidence.
Prepare with your own facts
Questions people ask
What are problem-solving interview questions?
How do I answer problem-solving questions?
What if I get a puzzle or case in the interview?
Can I use an example from outside work?
How this page is built
Written by Maid Dizdarevic, a career coach and 8x LinkedIn Top Voice. Advice is labelled as advice. Every sample answer was written by TryHired to show structure: none is a real candidate's answer, and every employer, number and result is a bracketed placeholder for your own true details. Question lists are general practice, not a prediction of what any employer will ask.
- What a specific employer will ask: no one can know that in advance, so read the posting and prepare your own evidence.
- Your results: we never invent numbers, and you should never claim a result you did not achieve.
- Outcomes: no guide, answer or program can promise an interview or a job offer.
- TryHired editorial guidance by Maid Dizdarevic, career coach, Nov 4, 2026.