INTERVIEWS

How to answer "Tell me about a time you solved a problem"

This question asks how you work through a problem. Tell one time in four parts: what the problem was, how you found the cause, what you did and what happened next. Spend most of the answer on the cause and what you did.

Use the answer to show how you think. A story where you looked into what was going wrong before you fixed it shows that better than one where the fix was obvious.

The common trap is a story that's mostly problem: a minute on what went wrong and ten seconds on the fix. The other trap is a story where the team solved it and your part is hard to find. Pick one where you can say what you did, and say "I" for it.

The structure: the problem, the cause, what you did, what happened next

Say what the problem was in two or three sentences, and what it was costing, like time, money, customers or a deadline. Then say how you found the cause: what you checked, who you asked and what you noticed. Then say what you did about it. End on what happened next, with something you can name, like a number, a date or what someone said later.

Aim for about a minute, and no more than two minutes. It's a version of the STAR method, with a step for finding the cause before the action. Write each part as a few words, then answer out loud from those notes.

The short answer

If they want it quick, two sentences will do: "[What kept going wrong] was costing us [what it cost]. I found that [the cause], so I [what you did], and [what happened]." Then stop and let them ask for more.

How to pick the story

Pick a problem that cost something you can name, like late orders, lost hours, a customer about to leave or a deadline about to slip.
Pick one where you found out why it happened, if you can. A fix that stopped it from coming back makes a stronger story than one that got you through the day. When there was no time to find the cause, say how you chose the fix.
Pick one where your part is clear. If a team solved it, you should still be able to say what you did.
Pick one you can explain to someone outside your field. If the problem needs jargon, say what it cost first, like "orders shipped a day late."
Pick one from the last few years. If you're a student or a new grad, a class project, a club or a part-time job all count.

Six sample answers

The people and companies below are made up. Read each answer out loud with a timer. Each runs about a minute. Then swap in your own story and keep the shape.

At work

"I coordinate shipping for a company that sells kitchen supplies online. Last spring, we were getting about 30 emails a week about late orders, and most were about orders placed on a Friday. I pulled two months of order times and found the pattern. Orders that came in after about noon on a Friday missed the carrier's 3 p.m. pickup, so they sat in the warehouse until Monday. Our packers worked oldest orders first, so the afternoon ones waited behind the morning's. I asked the carrier for a later Friday pickup, and they couldn't do it. So on Fridays, I had two packers start an hour early to clear the morning orders. Then they packed each new order as it came in. We also added a line at checkout saying when Friday orders would ship. Within a month, the late-order emails went from about 30 a week to about 10."

For a customer

"I work in customer service for an online furniture store. A customer's new dining table arrived missing one of its legs, and she was hosting her family for Thanksgiving that weekend. The replacement leg was back-ordered for six weeks. I asked our warehouse whether a table of the same model had been returned. One had, with a scratched top and four good legs. I asked my manager if we could send her one of those legs, and he said yes. I had it shipped overnight at our cost, and I called her to tell her it was on the way. She had the table set up two days before the dinner. She wrote a review that mentioned me by name, and my manager started a shelf in the warehouse for good parts from returned furniture."

Under pressure

"I coordinate events at a hotel. Forty minutes before a company's awards dinner, the projector in our ballroom stopped working. The whole program was a slide for each winner, and our AV technician was across town at another event. I called him, and he walked me through a restart over the phone. I gave it five minutes. When it didn't work, I stopped trying to fix it and looked for another screen. One of our meeting rooms had a large TV on a rolling cart. Two of our staff wheeled it to the front of the ballroom, and I connected the client's laptop to it. Then I told their host what had happened, so she wasn't surprised, and she asked the guests to move their chairs in a little. The dinner started on time, and the client booked the same room for next year before she left."

With limited information

"In my second month as an accounts payable clerk at a manufacturing company, our controller noticed we'd paid one supplier twice for the same invoice. No one knew how it had happened. I pulled six months of payments to that supplier and found three more doubles. Each time, the supplier had emailed the invoice and also mailed a paper copy, and two different people had entered them. I checked our other suppliers and found two more we'd paid twice the same way. I asked all three to send invoices by email only. I also asked our software administrator whether the system could warn us about a repeated invoice number. It turned out it had that warning, and it was switched off. Once it was on, a second entry of the same number got stopped. The suppliers paid back about $14,000, and in the eight months since, we haven't paid an invoice twice."

Creatively, with no budget

"I'm a receptionist at a veterinary clinic. On busy mornings, cats and dogs waited together in our small lobby, and cat owners kept telling us the barking upset their pets. We had no room for a second waiting area and no money to build one. I noticed that our last exam room usually sat empty until 10 a.m. I asked our practice manager if cat owners could wait in there in the mornings, and she agreed. I put a sign on the door that said 'Cats wait here.' I also added a line to our reminder texts saying cat owners could wait in their car, and we'd text them when their room was ready. Within a few weeks, we'd stopped hearing that complaint, and three of our reviews that spring mentioned the cat room."

A college student

"I was the treasurer of my college's hiking club. On most trips, three or four people dropped out the night before, and we'd already paid for their seats in the rented vans. I went through a semester of sign-ups and found that almost everyone who dropped out hadn't paid yet. People paid at the van, so signing up cost them nothing. I asked the other officers if we could collect payment at sign-up, with a full refund up to three days before the trip. They agreed, and I set it up through the payment app we already used for dues. The next semester, we averaged about one dropout a trip, and we stopped losing money on the vans."

What to leave out

A problem anyone would have fixed the same way in a few minutes. If the fix was obvious, the story doesn't show much.
A long setup. Two or three sentences on the problem is enough.
System names and jargon the interviewer may not know. Say what the problem cost instead.
Blame. Say what went wrong, and leave out whose fault it was.
An ending with no result. If you can't measure it, say what changed or what someone said.
Private details, like a customer's name, anyone's health or numbers your company keeps private.

How to tell it

A problem story can turn into a list of everything that went wrong. Keep the problem short and the steps easy to follow.

Say the problem in plain words, then what it was costing. "Friday orders were shipping on Monday" is easier to follow than how the warehouse system works.
When you explain how you found the cause, mark the steps out loud: "First, I pulled the order times. Then I checked when the carrier came." Words like "first" and "then" tell the listener where you are in the story.
Slow down for the cause. It's the part that shows how you think.
Say "I" for what you did and "we" for what the team did, so it's clear which part was yours.
Pause before the result, then say it plainly. If your answers tend to run long, see how to stop rambling.

If they ask how you solve problems

"How do you approach problem solving?" and "How do you solve problems at work?" ask for your approach first. Say it in one sentence, like "I look for the cause before I fix anything, and I check afterward that it stayed fixed." Then tell one short story that shows it. Anyone can describe a good approach, so the story is what makes yours believable.

The same question in other words

"Describe a time you solved a problem", "Tell me about a time you had to solve a problem", "Tell me about a recent problem you solved" and "Give an example of a problem you solved at work" all ask the same thing. Answer them the same way.

"Tell me about a difficult problem you solved" and "Tell me about a time you solved a complex problem" ask for a harder story, so pick one where the cause took some finding, like the accounts payable answer. "...under pressure" and "...quickly" ask about a deadline, so say how much time you had, as in the hotel answer. "...with limited information" asks what you did when nobody knew the cause. "...creatively" asks for a fix nobody had tried, like the cat room. "...for a customer" asks about someone outside the company, so end on what changed for them. If the customer was upset with you, see how to answer "Tell me about a time you dealt with a difficult customer". "Describe a time you solved a problem without being asked" asks whether you spotted it yourself, so say how you noticed it and who you told before you acted. For more stories like that, see how to answer "Tell me about a time you took initiative".

"Tell me about a difficult situation and how you handled it" is close, but it asks what you did while things were going wrong, more than how you found the cause. It has six sample answers of its own in how to answer "Tell me about a difficult situation and how you handled it".

Practice it out loud

A chatbot can tidy up the story. You still have to get through the problem fast enough that the fix gets most of the time, and that's hard to judge until you hear yourself. So practice the way you'll give it: out loud and on a timer.

Write the four parts: the problem, the cause, what you did and what happened next. A few words each.
Answer from your notes into your phone's voice recorder, and time it.
Play it back and note when you reach the cause. If it's past the halfway mark, cut the problem down.
Listen to the steps of how you found the cause. If they run together, start each one with "first" or "then."
The next day, answer without the notes. Then have a friend ask the usual follow-ups: "How did you know it worked?" and "What would you do differently?"

For the rest of the interview, there's a 15-minute routine in how to practice for an interview by yourself. The other common questions are in how to answer interview questions.

Practice it with an AI coach in Charisma Lab

Charisma Lab is a speaking coach on your iPhone. In Speak, tap INTERVIEW under PRACTICING FOR. Then tap the center, say what the job is and tell the coach you're practicing "Tell me about a time you solved a problem." Tell your story one part at a time, since a pause of about two seconds ends a take. You hear each take played back. When something is off, the coach says what to fix, then the mic opens again.

To mark the steps of how you found the cause, try Train's Structure Your Points. It's open from the start in the Clarity track. It gives you a line like "We need to understand the problem, then identify solutions, then execute." and you say it again with structure words. A take passes when its transcript has at least two of the twelve words and phrases the app checks for, such as "first", "then" and "finally". That line already has "then", and saying it twice still counts once. Add another, like "first". Setup is free. If you tap MAYBE LATER when it shows the price, then SKIP FOR NOW when it asks you to sign in, setup goes on to a short live session with the coach. After setup, the app needs Pro, which is $14.99 a month in the US. See pricing.

Get the app

FAQ

How long should my answer be?

About a minute, and no more than two minutes. Keep the problem to two or three sentences, and spend most of the rest on the cause and what you did.

What if I can't think of a problem I solved?

Think smaller: a task that wasted time every week, a form people kept filling in wrong, a schedule that kept clashing or a customer with an odd request. Students can use a class project, a club or a part-time job.

What if the problem isn't fully solved yet?

Say what you've done so far, what has changed and what's left. A partial fix you can measure still makes a good answer.

Can I use a problem I caused?

Yes, if you say so in a sentence and spend the time on the fix. If the story is mostly about the mistake, see how to answer "Tell me about a time you made a mistake".

Should I use a technical problem?

If the job is technical, yes. Start with what it cost, like "the app froze for one in ten people at checkout." Then go as deep as they ask.

More practice guides

Updated November 4, 2026.