Problem Solving Interview Questions: 20 With Sample Answers
Problem solving interview questions ask you to describe a real problem you solved ("Tell me about a time you fixed something that was broken") or to work through a hypothetical one on the spot ("What would you do if a key supplier missed a deadline?"). The interviewer is listening less for the fix than for how you got there: how you defined the problem, what options you weighed, why you chose one and how you checked it worked.
Below are 20 common problem solving interview questions in three groups: behavioral, situational and analytical. Each comes with what the interviewer is checking and either a sample answer or what a strong answer covers, followed by common mistakes and a timed practice routine.
What Interviewers Are Checking
Almost every problem solving question tests the same handful of things:
- You define the problem before fixing it. Strong candidates say what was actually wrong, in observable terms.
- You consider more than one option. Naming two or three paths you rejected, and why, shows a choice rather than a reflex.
- You find causes, not just symptoms. Interviewers want to hear how you worked out why something was happening.
- You decide with incomplete information. Saying what you didn't know and how you handled it is a plus.
- You check the result. An answer that ends with "and it worked" is weaker than one that says how you knew.
- You work with people. Showing how you brought others along counts.
The four-move pattern behind all of this (define, generate, choose, test) is the same one used in the worked problem solving examples post. If you can name each move in your answer, you're covering what the interviewer wants.
How to Answer Problem Solving Interview Questions
Use a different structure for each type of question.
For behavioral questions ("Tell me about a time..."), use STAR:
- Situation: one or two sentences of context. Who, where, what was at stake.
- Task: what you were responsible for.
- Action: what you did, step by step. This is the longest part. Include how you found the cause and which options you rejected.
- Result: what changed, as specifically as you honestly can, and what you'd do differently or what you put in place so the problem didn't come back.
Aim for about two minutes. Spend most of it on Action.
For situational questions ("What would you do if..."), think out loud in four steps:
- Clarify. Ask one or two questions, or state your assumptions: "I'll assume the client hasn't been told yet."
- Options. Name two or three ways you could respond.
- Choose. Pick one and give the reason, plus the main risk.
- Check. Say what you'd do first and how you'd know it was working.
For analytical questions (estimates, logic, "how would you approach..."), narrate your reasoning. Break the problem into parts, say each assumption aloud, and sanity-check the final answer.
Behavioral Problem Solving Interview Questions
These ask about a real problem from your past. Prepare three or four true stories before the interview and you can adapt them to most of the questions below.
1. Tell me about a time you solved a difficult problem at work.
- What they're checking: the full process, start to finish, and how hard a problem you consider "difficult."
- Structure: STAR, with the Action split into define, options, choice and test.
- Sample answer: "Our monthly invoice run kept producing about a dozen errors that took a day to fix. I was asked to find out why. I pulled the last three months of errors and sorted them by type, and almost all of them came from customers whose billing address had changed mid-month. Rather than adding a manual review step, which would have slowed everyone down, I asked the developers to flag any address change in the week before the run. The next two runs had one error between them, and the flag is now part of the standard process."
2. Describe a time you had to solve a problem without all the information you needed.
- What they're checking: comfort with uncertainty and how you decide when waiting isn't an option.
- Structure: STAR. In Action, name what you didn't know, what you assumed, and how you limited the risk of being wrong.
- Sample answer: "A customer threatened to cancel because an order hadn't arrived, and the carrier's tracking had stopped updating. I couldn't confirm where the package was, so I offered to ship a replacement that day and asked the customer to refuse the first box if it turned up. The original package arrived two days later and came back to us. We kept the customer, and I wrote up the case so support had a standard answer for stalled tracking."
3. Tell me about a time you identified a problem before anyone else noticed.
- What they're checking: initiative and attention to patterns.
- Structure: STAR, with extra weight on how you spotted the signal.
- Sample answer: "I noticed that new hires in two of our five offices were waiting more than a week for laptop access, and each office thought that was normal. I compared the request process across offices and found those two routed requests through a shared inbox nobody owned. I suggested sending them straight to IT like the others. After the change, every new hire in those offices had a working laptop on day one."
4. Give an example of a time a solution you tried didn't work. What did you do next?
- What they're checking: honesty, and whether you learn and adjust instead of defending the first idea.
- Structure: STAR, but the Result has two parts: what failed and what you changed.
- Sample answer: "Our team kept missing handoff details between shifts, so I introduced a written handoff form. Within two weeks people were filling it in with 'same as yesterday.' The form wasn't the problem; nobody read it. I replaced it with a five-minute standing handoff at shift change where the outgoing person names the top two open issues. That stuck, and missed handoffs dropped to almost none."
5. Tell me about a time you had to solve a problem with a tight deadline.
- What they're checking: prioritization under pressure and whether you cut the right corners.
- Structure: STAR. In Action, say what you deliberately left out and why.
- Sample answer: "Two days before a trade show, we learned our printed brochures had the wrong product prices. Reprinting would take a week. I weighed stickers, a QR code and a printed insert. Stickers looked sloppy and few visitors would scan a code, so a local shop printed corrected price inserts overnight. Nobody at the show raised a pricing question."
6. Describe a problem you solved by working with a difficult person or team.
- What they're checking: whether you can solve the people side of a problem, not just the technical side.
- Structure: STAR. Show that you understood the other side's goal before proposing a fix.
- Sample answer: "The sales team kept promising custom features our product team couldn't build in time, and both sides blamed each other. I sat in on three sales calls and saw that customers wanted a result, not a specific feature, so I helped one sales lead list existing features that met the most common requests. Sales started offering those first, and custom requests reaching the product team fell sharply."
7. Tell me about a time you used data to solve a problem.
- What they're checking: whether you let evidence change your mind.
- Structure: STAR. In Action, say what you expected to find and whether the data agreed.
- Sample answer: "I assumed our newsletter sign-ups had dropped because of a design change. Before reverting it, I checked the sign-ups by traffic source and found they had held steady everywhere except one partner site that had removed our link. The design wasn't the cause. I contacted the partner, the link went back up, and sign-ups recovered the next month."
8. What's the most creative solution you've come up with for a problem?
- What they're checking: whether you can look past the obvious fix.
- Structure: STAR. Mention the obvious solution first, then why you went beyond it.
- Sample answer: "Our office meeting rooms were always booked but often empty. Instead of a stricter booking policy, I suggested releasing any room automatically if nobody checked in within ten minutes. It took no extra admin, and rooms became easier to find within a week."
If your stories keep stalling on the Action line, read the problem solving skills post for the specific moves that make up that line.
Situational Problem Solving Interview Questions
These are hypothetical, so the interviewer is judging your reasoning. Use the clarify, options, choose, check structure.
9. What would you do if you were given a project with an unrealistic deadline?
- What they're checking: whether you push back with options rather than complaints.
- Strong answer covers: clarifying what "done" means and which parts are fixed, offering two or three trade-offs (smaller scope, more people, a later date for part of it), choosing one with the manager, and flagging risks early rather than at the deadline.
10. How would you handle a customer who is angry about a problem you didn't cause?
- What they're checking: ownership and calm.
- Strong answer covers: listening fully before explaining, separating the immediate fix for this customer from the underlying cause, taking responsibility for the next step even if the cause was elsewhere, and following up to confirm the customer was satisfied.
11. Imagine two teammates disagree about how to solve a problem and ask you to decide. What do you do?
- What they're checking: fairness and whether you decide on criteria rather than on who argues hardest.
- Strong answer covers: asking each person to state the goal and their reasoning, agreeing on what a good outcome looks like, checking whether a small test could settle it, and explaining the decision so both understand why.
12. What would you do if you noticed a mistake in work that had already been sent to a client?
- What they're checking: integrity and speed.
- Strong answer covers: confirming the mistake and its impact, telling your manager quickly, proposing the correction and how to communicate it, and adding a check so it doesn't happen again.
13. You start a new job and find that a key process is slow and frustrating. What do you do?
- What they're checking: whether you learn before you change things.
- Strong answer covers: asking why the process exists (it may solve a problem you can't see), measuring where the time goes, suggesting one small change to test, and bringing the people who use the process into the fix.
14. A tool your team depends on stops working an hour before an important deadline. Walk me through what you'd do.
- What they're checking: triage under pressure.
- Strong answer covers: deciding what absolutely must be delivered, finding a workaround for that part only, telling the people affected early, and reporting the outage so someone works on the root cause after the deadline.
For more hypotheticals in this format, including workplace ones with notes on what a strong answer includes, see the problem solving scenarios post.
Analytical Problem Solving Questions
Some interviews include a short reasoning problem. Narrate every step and say each assumption aloud.
15. How would you figure out why sales dropped last month?
- What they're checking: structured diagnosis.
- Strong answer covers: confirming the drop is real (not a reporting change), breaking sales into parts such as number of customers times average order, checking which part fell, then looking for what changed at the same time: prices, a competitor, a season, a website change.
16. How many coffee cups does a busy café use in a day?
- What they're checking: whether you can break an unknown into estimable pieces.
- Strong answer covers: stating assumptions (opening hours, customers per hour at peak and quiet times, share of takeaway orders), multiplying through, and sanity-checking the total against what a single counter could realistically serve.
17. If you had to cut a team's costs by a tenth without layoffs, where would you start?
- What they're checking: prioritization and second-order thinking.
- Strong answer covers: listing the biggest cost categories first, picking cuts with the least effect on customers, and naming what each cut might cause later, such as slower service or lower morale. The second-order thinking post covers that last habit in detail.
18. A process has five steps and the output is often wrong. How would you find which step causes it?
- What they're checking: methodical isolation of a cause.
- Strong answer covers: checking the output after each step instead of only at the end, starting in the middle to halve the search, and testing a fix on that step alone before changing anything else.
19. How would you decide between two solutions that both seem reasonable?
- What they're checking: decision criteria.
- Strong answer covers: naming the criteria that matter (cost, time, risk, reversibility), favoring the option that's cheaper to undo when the evidence is close, and running a small test of either when possible.
20. What questions would you ask before solving a problem you've just been handed?
- What they're checking: problem definition, the step most candidates skip.
- Strong answer covers: what "solved" looks like, who is affected, what has already been tried, what constraints are fixed, and when it needs to be done. If you want more questions in this style, the critical thinking questions post groups them by purpose.
Problem Solving Questions for Interviewers to Ask
If you're hiring, the questions above work from your side of the table too, with a few habits:
- Ask for a specific example, then probe. "What did you try first?" and "How did you know it worked?" separate real stories from rehearsed ones.
- Ask what they would do differently.
- Use one hypothetical from your actual work. A real problem your team faced last quarter tells you more than a generic brainteaser.
- Score the process, not the answer. Before the interview, write down what a strong answer covers (like the notes above) and score against that list.
Mistakes That Weaken a Good Answer
- Starting with the solution. If the first sentence is what you did, the interviewer can't judge whether it was the right thing to do.
- Saying "we" for every step. Teamwork matters, but the interviewer is hiring you. Say which part you did.
- Picking a problem that was too easy. Choose one with a real trade-off.
- Leaving out the result. End with what changed. If you don't have a number, describe the change plainly.
- Inventing details. Follow-up questions expose made-up stories fast. Use real ones, even if they're smaller.
- Skipping the clarifying question on hypotheticals. One good question at the start often makes the rest of the answer easier.
How to Practice Problem Solving Interview Questions
Practice out loud and on a timer.
- Build a story bank (30 minutes, once). Write down four real problems you've solved: one with a tight deadline, one that involved a difficult person, one where your first fix failed, and one you're proud of. For each, write one line per STAR step.
- Match stories to questions (10 minutes). Go through the 20 questions above and note which story you'd use for each. Most stories cover three or four questions.
- Answer aloud with a two-minute timer (10 minutes a day). Pick three questions at random. Record yourself if you can. Check that each answer defines the problem, names at least one option you rejected, and ends with a result.
- Do one hypothetical cold each day. Read a situational question and answer it immediately using clarify, options, choose, check.
To train the thinking behind the answers, try the Creative Problem Solving drill. It walks you through one challenge in timed steps: reframe the problem three different ways, list bold solution ideas, then pick your favorites, weigh pros and cons and refine one into a plan. That's the same sequence interviewers listen for. If you tend to fixate on the first framing of a problem, the problem reframing post has more techniques for that first step.
Frequently Asked Questions
What are problem solving interview questions? They are questions that ask you to describe how you solved a real problem in the past, or how you would handle a hypothetical one. Interviewers use them to see how you define a problem, weigh options, make a decision and check the result.
How do you answer "Tell me about a time you solved a problem"? Use STAR: Situation, Task, Action, Result. Spend most of the answer on the Action: how you found the cause, which options you considered and why you chose one. End with a specific result.
What is the best answer to a problem solving interview question? There isn't one best answer. The strongest answers are true, specific and show the full process: a clearly defined problem, more than one option, a reasoned choice and a checked result. An honest story about a modest problem beats an impressive one you can't explain under follow-up questions.
What is the difference between behavioral and situational problem solving questions? Behavioral questions ask about something you actually did ("Tell me about a time..."). Situational questions ask what you would do in a hypothetical case ("What would you do if..."). Answer behavioral questions with STAR, and situational ones by clarifying, listing options, choosing one and saying how you'd check it.
How long should an answer to a problem solving question be? About two minutes. That's long enough to show your reasoning and leaves time for follow-up questions.
How can I get better at problem solving questions before an interview? Prepare three or four real stories in STAR form, practice answering aloud with a two-minute timer, and answer one hypothetical question cold each day.
Ready to train your creativity? Try science-backed exercises that measure and improve your creative thinking. Start a Free Exercise