Problem-solving interviews are typically retrospective. You ask someone to describe a problem they solved, they describe one, you hear about how they solved it. The problem is you're hearing a story crafted after the fact, by someone who knows it turned out fine. You're not seeing how they actually think when they're faced with something they don't immediately know the answer to.
This matters more for problem-solving than for almost any other competency. A lot of what makes someone a genuinely good problem-solver is what happens in the first few minutes of encountering something they haven't seen before — how they frame it, what they try first, whether they get stuck or adapt. None of that is observable in an interview where the candidate has had days or weeks to prepare their best example.
That said, behavioural questions about real problem-solving experiences can still reveal useful things — particularly about process, persistence, and how someone handles the frustration of not having an obvious path forward. The key is asking about genuinely novel problems, not the kind that had a textbook answer.
5 problem-solving interview questions
These questions are designed to surface candidates' actual thinking processes, not just their outcomes. Push for specifics about what they tried, what didn't work, and how they adjusted. A candidate who can only describe problems with neat solutions is showing you a polished story. A candidate who can describe what it felt like not to know the answer, and how they worked through that, is showing you something more useful.
"Tell me about a time when you had to break down a complex problem when there was no obvious starting point."
This is about structure under uncertainty. When faced with something genuinely complex and unresolved, good problem-solvers don't wait for clarity to arrive — they impose enough structure to start moving. They identify what they do and don't know, separate the parts of the problem they can work on from those they can't yet, and begin somewhere sensible. Strong answers will describe this process in real terms, not as a methodology but as actual thinking. What did they know? What did they not know? Where did they start, and why?
Answers that go straight to "I sat down with the team and we brainstormed" without any description of how the candidate personally engaged with the problem are worth following up on. What did they bring to the process, not just facilitate?
Probing questions
- What made it feel complex — was it the volume of information, the number of unknowns, or something else?
- Where did you decide to start, and why that rather than somewhere else?
- What did you have to abandon or revisit as you went further into it?
"Describe a time when the straightforward approach wasn't available to you and you had to find another way."
Genuine problem-solving often means working around constraints — time, resources, access, information. This question is specifically about adaptability within the problem-solving process: what do you do when the obvious route is blocked? Strong candidates will describe real constraints and explain how they thought around them. They'll show some creativity in identifying alternatives, and they'll be honest about what the constraints meant for the quality or speed of the solution.
Watch for candidates who can't really say what made the straightforward approach unavailable, or who describe a situation where they simply asked a senior person for help. That's not problem-solving, that's escalation — which is sometimes the right answer, but isn't what this question is asking about.
Probing questions
- What was the constraint that made the obvious approach unavailable?
- How did you generate the alternative you went with — was it something you'd seen before, or did you work it out from scratch?
- What did you have to accept or trade off by going that route?
"Give me an example of a time you used limited resources or incomplete information to solve something that initially seemed unsolvable."
This question is about resourcefulness and tolerance for ambiguity. A lot of real-world problems arrive without enough data, with constraints on what you can do, and with timelines that don't leave room for getting everything you need before you start. Strong answers will show someone who was comfortable enough with that uncertainty to act anyway, who made reasonable assumptions explicitly rather than pretending they had more information than they did, and who found ways to work with what was available.
Probing questions
- What information or resources did you not have that you would have wanted?
- How did you decide when you had enough to move forward, rather than waiting for more?
- What would you have done differently if you'd had access to everything you needed?
"Tell me about a time you identified the root cause of a recurring problem rather than just treating the symptoms."
Recurring problems are one of the clearest tests of analytical depth. Surface-level problem-solvers fix what's in front of them and move on. Deeper thinkers notice the pattern, ask why it keeps happening, and work back to what's actually causing it. Strong candidates will describe how they recognised the pattern, what process they used to trace it to a cause (not just a guess), and what happened when they addressed it at source rather than at surface level.
This question also tells you something about initiative and intellectual curiosity — the willingness to spend time on something that isn't strictly your job but that you've noticed needs fixing properly.
Probing questions
- How did you recognise that this was a recurring pattern rather than a one-off?
- What process did you use to trace it back to the root cause?
- What changed after you addressed the root cause, and how did you verify that it had actually worked?
"Describe a time you solved a problem in a way that others hadn't tried before."
This is the creativity question within problem-solving — it specifically asks about doing something genuinely different. Strong answers here will describe what the existing approaches were, why they weren't working, and how the candidate arrived at something new. The interesting part is usually how they got the idea: was it by analogy from a different domain, by questioning an assumption everyone else was making, by combining things that hadn't been combined before? Candidates who can explain their creative process are more likely to be able to repeat it.
Probing questions
- What approaches had already been tried, and why weren't they working?
- How did you arrive at the new approach — where did the idea come from?
- How was the new approach received, and did it actually work as expected?
Why interviews aren't the best tool for this
The core issue is that problem-solving is fundamentally a live, active process, and interviews are retrospective by nature. When you ask someone to describe a problem they solved, they're telling you about something they've already worked through — the uncertainty has been resolved, the steps are clear in hindsight, and the outcome is known. That's a very different cognitive experience from actually facing something unknown in real time.
Candidates also curate which problems they describe. They'll naturally select examples where they performed well, where the solution worked, where they look capable and decisive. Problems where they got stuck for a long time, went down the wrong path, or had help from others in ways that were more central than they'll admit — those stories tend not to get volunteered. You're hearing a best-case portfolio, not a representative sample.
There's also a real risk of confusing the ability to narrate a problem-solving process with the ability to actually execute one. A candidate who has read enough about structured thinking can describe their approach using the right language — "I first identified the key variables," "I broke the problem into components" — without that reflecting how they actually behave when they're in the middle of something genuinely difficult. Articulate answers about problem-solving are not the same as demonstrated problem-solving capability.
Interviews are also late in the process to be discovering someone isn't who you thought they were. By the time you're at final-stage interview, a lot of time has already been invested. Finding out at that point that someone's analytical capability doesn't match their interview performance means starting again. Measuring problem-solving earlier, before interviews, changes the shape of that risk considerably.
What actually works for measuring problem-solving
You don't have to rely on interviews for this. Cognitive ability assessments can measure problem-solving directly before you've even scheduled an interview. Specifically, logical reasoning and numerical reasoning tests give candidates actual problems to solve rather than asking them to describe problems they've solved before.
The research on this is unusually clear. Schmidt, Oh and Schaffer's (2016) meta-analysis found general mental ability has a validity coefficient of around 0.65 with job performance, making it one of the strongest predictors available across the whole of selection research. You're measuring how someone actually thinks — their processing speed, their ability to identify patterns, their capacity to work through abstract problems — not how well they can reconstruct a past success in a way that sounds impressive.
We cover this in much more depth in our article on how to assess soft skills, but the core idea is straightforward: measure cognitive ability early so that by the time you're interviewing, you're already confident about the analytical foundation and you're using the conversation to explore domain knowledge, context, and fit rather than trying to infer raw problem-solving capability from a story.
Conclusion and next steps
The questions above will surface more useful information than generic problem-solving prompts — they push candidates towards real examples, real constraints, and real thinking rather than polished accounts of successful outcomes. But they can't show you how someone thinks in real time, and that's the heart of what problem-solving actually is.
If you want a more reliable read, our aptitude assessments are designed by business psychologists and validated against job performance data. They measure the reasoning ability that actually predicts problem-solving performance on the job, not just the ability to describe it well.
Ben Schwencke
Chief psychologist at Test Partnership. MSc in Organisational Psychology with over ten years experience in psychometric testing.
