Interview guide · Competencies
Problem-solving interview questions
In short
Problem solving interview questions should make candidates show their method: how they define the problem, gather facts, test causes, choose a fix and check it worked. This page gives 27 behavioral, situational and analytical questions with what each reveals, strong answer markers, red flags, sample answers and a scorecard you can use as is.
Almost every candidate says they are a good problem solver. The interview has to find out what that actually means for them. Some people are fast at spotting the obvious fix. Some are careful diagnosticians who dig for the root cause. Some only escalate. For a frontline role you mostly want the first type with a little of the second; for an analyst, supervisor or operations role you want much more of the second.
The questions below are grouped by what they test. Behavioral questions show what the candidate did in the past, situational questions show how they reason about your actual work, and a few analytical prompts let you watch them think out loud. Ask four to six, and keep probing until you hear the steps: what did you check first, what did you rule out, how did you know it was fixed.
What these questions assess
- Defining the problem before solving itStrong problem solvers restate the issue, separate symptom from cause and ask what success looks like. Weak ones start fixing the first thing they see.
- Using evidenceListen for data, logs, customer records, a quick test, or asking the person closest to the issue. Gut feel alone leads to repeat failures.
- Structured reasoningGood candidates break a messy situation into parts and work through them in order. You can hear it in how they tell the story.
- Judgment about when to escalateSolving everything alone is not the goal. Knowing your authority limits and bringing in the right person early saves time and risk.
- Checking the resultMany fixes fail silently. Candidates who describe confirming the outcome, or monitoring for recurrence, prevent the same problem from coming back.
- Learning and preventionThe best answers end with something changed: a checklist, a process tweak, a note in the knowledge base. That is what separates fixing from improving.
Problem solving behavioral interview questions
Tell me about the hardest work problem you have solved in the last year. Walk me through it step by step.
- Why ask it
- The anchor question. Gives you their method in their own words and the level of complexity they are used to.
- A strong answer
- Clear definition of the problem, how they gathered information, options considered, what they chose and why, and how they confirmed it worked.
- Red flags
- Jumps straight to the happy ending with no steps in the middle.
Describe a time the first fix you tried did not work. What did you do next?
- Why ask it
- Real problem solving involves dead ends. Shows persistence and whether they revise their thinking.
- A strong answer
- Recognized the failure quickly, went back to the evidence, changed the hypothesis and tried a different approach.
- Red flags
- Repeats the same fix harder, or gives up and hands it off without learning anything.
Tell me about a problem you noticed that nobody had asked you to fix.
- Why ask it
- Tests initiative and whether they see problems before they become complaints.
- A strong answer
- Spotted something specific, checked whether it was real, raised it or fixed it within their authority, and shows the result.
- Red flags
- Fixed it in a way that bypassed their manager or broke a process.
Give me an example of a problem you solved by finding the root cause rather than the symptom.
- Why ask it
- Separates surface fixers from people who prevent recurrence.
- A strong answer
- Describes a symptom, tracing it back (for example asking why several times), finding the underlying cause, and fixing that.
- Red flags
- Cannot explain the difference between the symptom and the cause in their own story.
Tell me about a time you had to solve a problem with incomplete information and a deadline.
- Why ask it
- Most real problems are like this. Shows how they balance speed and certainty.
- A strong answer
- Identified what they knew and did not know, made a reasonable call, stated their assumptions, and built in a way to adjust later.
- Red flags
- Waited for perfect information and missed the deadline, or guessed blindly.
Describe a time you used data or numbers to solve a work problem.
- Why ask it
- An analytical interview question that works for most roles, not only analysts.
- A strong answer
- Names the data source, what they looked for, what pattern they found and the decision it led to.
- Red flags
- Vague about the data, or the numbers did not actually change the decision.
Tell me about a problem you could not solve. What did you learn?
- Why ask it
- Tests honesty and reflection.
- A strong answer
- Owns the outcome, explains what blocked them, and names a concrete lesson they applied later.
- Red flags
- Blames others entirely or claims they have never failed to solve a problem.
Give me an example of a process you improved because it kept causing the same problem.
- Why ask it
- Shows systems thinking and whether they move from firefighting to prevention.
- A strong answer
- Quantifies the before and after (fewer errors, less rework, shorter wait) and explains how they got buy-in.
- Red flags
- Changed a process on their own with no consultation.
Tell me about a time you solved a problem by asking for help. Who did you go to and why them?
- Why ask it
- Shows they know how to use the people around them rather than struggling alone.
- A strong answer
- Picked the right person for a reason, came prepared with what they had tried, and learned enough to handle it next time.
- Red flags
- Either never asks for help or hands the whole problem to someone else.
Situational problem solving questions
You come in for your shift and the system you need to do your job is down. Nobody has said when it will be back. What do you do in the first 15 minutes?
- Why ask it
- A realistic frontline scenario. Tests calm, communication and workarounds.
- A strong answer
- Confirms it is not a local issue, reports it through the right channel, tells the supervisor, and starts a manual workaround or useful task.
- Red flags
- Waits silently for someone to notice.
A customer reports the same issue three times this month, and each time it was marked resolved. How would you approach it?
- Why ask it
- Tests root cause thinking in a service context.
- A strong answer
- Reviews the history, looks for what was actually done each time, tests a different cause and owns the case until confirmed fixed.
- Red flags
- Applies the same fix a fourth time.
Your team's error rate doubled this week and your manager asks you to find out why. Where do you start?
- Why ask it
- An analytical prompt that shows how they structure an investigation.
- A strong answer
- Breaks it down: which errors, which people, which shifts, what changed this week (new process, new hires, system update), then tests the most likely cause.
- Red flags
- Blames a person immediately before looking at data.
Two urgent problems land at the same time and you can only work on one. How do you decide?
- Why ask it
- Tests prioritization logic.
- A strong answer
- Weighs impact, number of people affected, safety or compliance risk and deadlines; tells the owner of the second problem when they will get attention.
- Red flags
- Picks whichever arrived first or whichever person is more senior.
You find a mistake in a report that has already been sent to a client. What do you do?
- Why ask it
- Tests integrity and problem containment.
- A strong answer
- Assesses impact, tells their manager quickly, proposes a correction, and checks how it slipped through.
- Red flags
- Hopes nobody notices.
A new process you rolled out is getting complaints from the team. How do you figure out whether the process is wrong or people just need time to adjust?
- Why ask it
- Shows they can separate change resistance from a real design flaw.
- A strong answer
- Collects specific complaints, observes the work, checks the results data, and adjusts or explains based on what they find.
- Red flags
- Dismisses all complaints or reverses the change at the first sign of pushback.
You are asked to cut the time it takes to complete a task by 20%. How would you approach it?
- Why ask it
- Tests structured improvement thinking.
- A strong answer
- Measures the current process, maps the steps, finds waste or waiting time, tests changes on a small scale and checks quality did not drop.
- Red flags
- Just tells people to work faster.
Analytical interview questions
Walk me through how you would estimate how many customer calls a 200-person company receives in a week.
- Why ask it
- An estimation prompt that shows how they break down an unknown into reasonable parts.
- A strong answer
- States assumptions, builds a simple model, sanity-checks the result and says what data would improve it.
- Red flags
- Refuses to estimate without data, or throws out a number with no logic.
Here is a short table of last month's daily sales. What stands out to you, and what would you check next?
- Why ask it
- A practical data read. Use real or anonymized numbers relevant to the role.
- A strong answer
- Spots trends and outliers, asks about context (holidays, stock outs), and proposes a next question rather than a conclusion.
- Red flags
- Draws a big conclusion from one data point.
How do you know when you have enough information to make a call?
- Why ask it
- Shows their personal rule for balancing analysis and action.
- A strong answer
- Relates it to the cost of being wrong and whether the decision can be reversed.
- Red flags
- Always wants more data, or never thinks about it.
Tell me about a time two sources of information contradicted each other. How did you figure out which was right?
- Why ask it
- Tests critical evaluation of evidence.
- A strong answer
- Checked how each source was produced, looked for a third source, or tested directly.
- Red flags
- Went with whichever source supported what they already believed.
What is a common assumption in your field that you think is wrong?
- Why ask it
- Shows independent thinking and depth in their domain.
- A strong answer
- A specific, reasoned view backed by experience or evidence, held with some humility.
- Red flags
- Cannot think of anything, or gives a contrarian take with no support.
How would you explain a complex problem you solved to someone with no background in it?
- Why ask it
- Problem solvers need to bring others along. Tests clarity.
- A strong answer
- Uses a plain analogy, focuses on the impact, and skips jargon.
- Red flags
- Cannot simplify, or talks down to the listener.
Questions for senior and lead candidates
Tell me about a problem that crossed several teams. How did you get people to agree on the cause?
- Why ask it
- Senior problems are rarely owned by one team. Tests influence and facilitation.
- A strong answer
- Brought data, set up a joint review, kept the focus on the process rather than blame, and agreed on owners for each fix.
- Red flags
- Solved it for their own team and left the rest.
How do you teach your team to solve problems on their own instead of bringing everything to you?
- Why ask it
- Shows whether they build capability or bottlenecks.
- A strong answer
- Asks questions instead of giving answers, sets clear authority limits, and reviews decisions afterward.
- Red flags
- Says it is faster to do it themselves.
Describe a time you chose not to fix a problem. Why?
- Why ask it
- Mature problem solvers know some problems are not worth the cost.
- A strong answer
- Weighed effort against impact, made a deliberate call and told the people affected.
- Red flags
- Has never made that call or ignored the problem without deciding.
Tell me about a time you had to undo a decision because your solution caused a new problem.
- Why ask it
- Tests accountability and adaptability at a higher level.
- A strong answer
- Spotted the side effect, owned it publicly, reversed or adjusted quickly, and explained what they would test earlier next time.
- Red flags
- Defended the original solution after the evidence turned against it.
What tools or frameworks do you use when a problem is messy and unclear?
- Why ask it
- Checks for a repeatable method, not a buzzword.
- A strong answer
- Names an approach such as five whys, a fishbone diagram, a simple decision matrix or a pilot test, and gives an example of using it.
- Red flags
- Lists framework names with no example of applying any.
Sample answers
I was a shift lead in a distribution center, and our mis-pick rate on one zone jumped from about 0.5% to 2% over three weeks. Everyone assumed it was the new hires. Before agreeing, I pulled the error log by picker, by shift and by product. The errors were spread across experienced and new people, but nearly all were on two aisles. I walked those aisles and found that a reslot had put two similar products with nearly identical labels side by side. I asked inventory control to separate them and added a color tag as a stopgap. Within a week the zone was back under 0.6%. I also asked that reslot changes get a quick label check before go-live, and that step is now on the checklist.
At a clinic front desk, patients kept arriving without the forms they were supposed to fill out online. My first fix was a stronger reminder text two days before. Completion barely moved. So I called five patients who had missed the forms and asked why. Three said the link opened a page that would not work on their phone. I tested it myself on two phones and they were right; the form was not mobile friendly. I brought that to the office manager with the patient quotes, and the vendor enabled the mobile version. Completion went from roughly half to most patients within a month. My lesson was to check the actual experience before assuming people just need another reminder.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Problem definition | 20% | Restates the problem, separates symptom from cause and defines what success looks like. | Starts solving immediately without clarifying the issue. |
| Use of evidence | 25% | Cites specific data, tests or sources and explains how they ruled options in or out. | Relies on assumptions or blames a person before checking facts. |
| Structured reasoning | 20% | Answers follow a clear sequence and break complex issues into parts. | Stories jump around with missing steps in the middle. |
| Judgment and escalation | 15% | Knows authority limits, involves the right people early, weighs cost against benefit. | Never escalates or escalates everything. |
| Verification and prevention | 20% | Confirms the fix worked and changes something so it does not recur. | Story ends at the fix with no check or follow-up change. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
How to run a problem solving interview
Problem solving is best tested with a mix of past behavior and live reasoning. A good 45 minute format for most roles: 25 minutes on three behavioral questions with deep follow-ups, 15 minutes on one situational case built from your own operation, and five minutes for the candidate's questions. For entry-level roles, cut it to two behavioral questions and one simple scenario.
The follow-ups do the real work. After the first answer, ask: what did you check first, what else could it have been, how did you know it was fixed, and what would you do differently. You are looking for the method, not the outcome. A candidate who solved a small problem with a clear method is usually a better bet than one who describes a big win with no visible reasoning.
These questions overlap with critical thinking interview questions, which focus more on evaluating arguments and evidence, and with decision-making interview questions, which focus on choosing between options under uncertainty. For a supervisor loop, take a couple from each rather than asking three versions of the same thing.
Add a work sample when the role is analytical
For analyst, coordinator, workforce planning or operations roles, a 20 to 30 minute work sample predicts more than another round of questions. Give the candidate a small, realistic dataset or case (a week of queue data, a scheduling conflict, a list of customer complaints) and ask them to talk through what they see and what they would do.
Keep it short and paid-time friendly; nobody should do a four-hour unpaid project for an hourly or junior role. Use the same case for every candidate and score with the same rubric. Structured skills assessments can run the first version of this at scale, with the live discussion saved for finalists.
Under the federal Uniform Guidelines on Employee Selection Procedures, any test that screens people out should be job-related and consistent with business necessity, and you should monitor whether it has adverse impact on protected groups. Puzzle questions and brainteasers unrelated to the work are hard to defend and predict little, so build your cases from real tasks. Rules vary by state and country.
Common mistakes when assessing problem solving
- Scoring the story instead of the method. Impressive outcomes are easy to borrow from a team. Ask what the candidate personally did and why.
- Using brainteasers. Questions like how many golf balls fit in a bus mostly measure whether the candidate has practiced brainteasers. A market-sizing estimate tied to your business is fine; abstract puzzles are not.
- Expecting the answer you would give. Candidates can reach a good solution by a different route. Score the reasoning against the rubric, not against your own preferred fix.
- Ignoring escalation. For many frontline jobs, the best problem solving answer includes knowing when to stop and call a supervisor. Do not penalize candidates for respecting authority limits.
- Letting one strong answer carry the interview. Score every question separately and average them, as you would in any well-run behavioral interview.
Frequently asked questions
What are good problem solving interview questions?
Strong ones ask for a specific past problem and the steps taken: tell me about the hardest problem you solved this year, describe a time your first fix did not work, give an example of finding a root cause, and tell me about a problem you could not solve. Add one situational case drawn from the actual job.
What are problem solving behavioral interview questions?
They ask what a candidate did in a real past situation rather than what they would do. Examples: tell me about a time you solved a problem with incomplete information, or describe a process you improved because it kept failing. Probe for each step of the method.
How do you answer problem solving interview questions?
Use a clear structure: the situation and what made it a problem, how you defined it, what information you gathered, the options you considered, what you did, how you confirmed it worked, and what you changed afterward. Be specific about your own part.
What are analytical interview questions?
Analytical questions test how a candidate works with data and logic: reading a table and spotting what matters, estimating an unknown from reasonable assumptions, or explaining how they resolved conflicting information. They are most useful for analyst, operations and supervisor roles.
How do you assess problem solving skills in an interview?
Combine two or three behavioral questions with deep follow-ups and one realistic case or work sample. Score each answer on problem definition, use of evidence, structured reasoning, judgment and verification, using a written rubric shared by all interviewers.
Should I use brainteasers to test problem solving?
Generally no. Brainteasers unrelated to the job are poor predictors of performance and frustrate candidates. Use cases built from real work, such as a staffing gap, a data anomaly or a recurring customer complaint.