In this article
How to use this list
The answers use the situation, task, action, result (STAR) structure explained below. Read the questions in order, then say each answer aloud in your own words with your own example. The wider behavioral interview guide places these questions inside a full loop, and how to answer interview questions covers the general routine.
Answers here are written as advice: a strong answer shows the points listed. They do not describe how any particular company scores answers.
The structure behind every answer
Behavioral questions rest on one premise: how you handled specific situations in the past is evidence of how you will work. The U.S. Office of Personnel Management describes structured interviews that include behavioral questions about past job situations.
One common way to structure such an answer is the STAR method. As a pointer for the definition, Wikipedia's entry on the method says the STAR method is an interviewing technique that employers use to evaluate candidates by how they respond to behavioral and situational questions. It suits open-ended questions that ask you to describe your involvement in a specific situation. The four parts answer four questions: what was the situation, what were you required to achieve, what did you do, and what was the outcome.
The same Wikipedia article says the interviewer looks for what you did, why you did it and what the alternatives were. For problem-solving questions, that means your action part should state the options you considered, not only the one you picked.
Text description of the diagram
- The four parts answer what the situation was, what you were required to achieve, what you did and what the outcome was.
- For problem-solving questions, your action part should state the options you considered.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →Analyzing a problem
Tell me about a time you solved a difficult problem.
Pick a problem that was hard because of its causes, not just its size. State the situation and your task briefly, then spend most of your time on the action: how you narrowed down the cause, which options you weighed, and why you chose one. Close with the result and what you would do differently. Use "I" for your own steps and name teammates only where they mattered.
Why it is asked: it shows how you reason when the path is not given. Read the full explanation: how to answer interview questions.
Tell me about a time you had to solve a problem with incomplete information.
Say what was missing and why you could not wait for it. A strong answer shows how you separated what you knew from what you assumed, made the assumptions explicit, chose a step that was easy to reverse, and checked it once new facts arrived. Finish with how the gap closed and whether your assumptions held.
Why it is asked: real work rarely arrives complete, so interviewers want to see calibrated judgment. Read the full explanation: decision making questions.
Tell me about a time you spotted a problem before anyone else did.
Explain what you noticed, how you confirmed it was real and not noise, and whom you told. A strong answer shows evidence rather than a hunch, a proposed fix rather than only a warning, and respect for whoever owned the area. Describe what happened after you raised it, including any pushback.
Why it is asked: it separates people who wait for instructions from people who watch the system. Read the full explanation: the behavioral interview guide.
Tell me about a time you made a decision using data.
Name the decision, the question the data had to answer, and where it came from. Show that you checked its quality, noticed what it could not tell you, and still reached a clear choice. Describe the outcome honestly, including a case where the data pointed one way and judgment another.
Why it is asked: it tests whether you use evidence in a disciplined way rather than for decoration. Read the full explanation: decision making questions.
Tell me about a time you had to make a decision under pressure.
Show a real decision made with little time and say how you kept it sound. A strong answer shows what you knew and what you assumed, why you chose that option over the others, and how you checked the outcome afterward. Pick a case where the pressure was real, and name the option you set aside.
Why it is asked: it shows judgment when time is short. Read the full explanation: decision making questions.
Describe the most complex problem you have solved.
Choose a problem that was complex because of interacting causes or many people, not only because of its size. A strong answer breaks the problem into parts, says which part you owned, explains the options you weighed, and ends with the result and a lesson. Keep technical detail to what the interviewer can follow.
Why it is asked: it shows how you handle difficulty and explain it. Read the full explanation: how to answer interview questions.
Priorities and change
How do you handle competing priorities?
Show how you compared two tasks and what you chose to delay. A strong answer weighs impact and deadline, consults the people affected and accepts a trade-off rather than claiming to have done everything. Illustrative example: a project coordinator had two requests due the same day; she asked both owners which deadline was firm, delivered the firm one first and told the other owner the new date.
Why it is asked: it reveals how you decide what not to do. Read the full explanation: decision making questions.
Tell me about a time requirements changed in the middle of a project.
Show that you clarified the new goal first, then replanned. A strong answer reuses what still holds and communicates the revised scope and risk. Illustrative example: a team lead learned the client wanted a different report format; he confirmed the new goal, kept the data work already done, rebuilt only the layout and sent the client a revised timeline.
Why it is asked: it checks flexibility without panic. Read the full explanation: how to answer interview questions.
Tell me about a time you missed a deadline or were about to.
Choose a case you can discuss honestly. A strong answer shows when you realized the date was at risk, how quickly you said so, which options you offered, and what you changed afterward. Do not blame others; describe the early warning you now give.
Why it is asked: it tests ownership and communication under pressure. Read the full explanation: common interview questions.
Working with other people
Tell me about a time you disagreed with a coworker.
Describe a real disagreement about a work decision, not a personality clash. A strong answer shows that you understood the other view first, brought evidence, and either compromised or committed to the final decision. Illustrative example: two engineers disagreed about release timing; one asked for the other's risks, compared them with the test results, proposed a smaller first release, and both agreed.
Why it is asked: it shows how you handle friction without damage. Read the full explanation: answering a teamwork question with the STAR method.
Tell me about a time you worked with another team to solve a problem.
Show how you aligned two teams around a common goal. A strong answer shows that you learned the other team's constraints, split the work clearly and credited others honestly. Illustrative example: a developer and a data team needed the same report; he asked what the data team could deliver, agreed one shared definition, and drove the integration work himself.
Why it is asked: many problems sit between teams. Read the full explanation: answering a teamwork question with the STAR method.
Tell me about a time you convinced people who did not report to you.
Explain what you wanted changed and why people had no obligation to follow. A strong answer shows that you listened to their incentives, built a case around their goals, and let them shape the plan. Give the result and how you knew you had persuaded rather than pressured.
Why it is asked: it tests influence without formal power. Read the full explanation: influence without authority.
Tell me about a time you accepted critical feedback from your manager.
Show that you listened, changed one thing and saw the effect. Illustrative example: a junior analyst was told her updates were too long; she asked for an example of a good one, cut her next updates to the key points, and her manager later said they were easier to use. Avoid feedback that is a disguised compliment.
Why it is asked: it shows whether you can improve a way of working. Read the full explanation: what is your greatest weakness.
When the solution did not work
Tell me about a time your solution failed.
Choose a failure you owned, with real stakes but not a disaster. Explain what you tried, how you found out it was not working, and what you did next. A strong answer shows quick detection, honest ownership and a changed habit, such as a check you now run before releasing anything.
Why it is asked: it separates reflection from excuses. Read the full explanation: common interview questions.
Tell me about a mistake you made and how you fixed it.
Name the mistake plainly in one sentence. Then show the repair: how you limited the damage, who you told, how you fixed the cause and not only the symptom, and what you changed so it would not repeat. The fix is the real content of this answer, so give it the most time.
Why it is asked: it shows how you behave when you are wrong. Read the full explanation: what is your greatest weakness.
Tell me about a time you had to learn something quickly to solve a problem.
Say what you did not know and why it was urgent. A strong answer shows how you chose what to learn first, who you asked, how you tested your understanding on a small case, and how you applied it. Then give the result and what stayed with you afterward.
Why it is asked: it tests learning speed under a real constraint. Read the full explanation: the behavioral interview guide.
Initiative and improvement
Tell me about a time you took the initiative.
Describe something you started unasked and show that it helped. A strong answer shows that you checked it was not someone else's job, made a small first step and measured the effect. Illustrative example: a support analyst noticed repeated questions, drafted one help article, asked her lead to review it, and then saw fewer repeat tickets.
Why it is asked: it shows whether you act on what you see. Read the full explanation: the behavioral interview guide.
Tell me about a time you improved a process.
State what was slow or error-prone and who felt it. A strong answer shows how you observed the current process, proposed a change, tested it on a small scale, and handled resistance. Report the result in terms the interviewer can picture, and say if you only know it informally.
Why it is asked: it tests whether you fix causes rather than work around them. Read the full explanation: how to answer interview questions.
Follow-up questions
How do you answer behavioral interview questions about problem solving?
Choose a real example, state the situation and task in a sentence or two, and spend most of your time on the action, including options you rejected and why. Close with the result. Practice saying it aloud so it sounds like your own account, not a script.
How long should a STAR answer be?
Give the action part, the part about you, the most time, and keep the situation and task to a sentence or two each. A useful test is whether you can stop as soon as the point is made; rehearse aloud and cut anything the interviewer does not need to follow the story.
Can I use an example from outside work?
Many candidates with little work history draw on school, volunteering or personal projects, and the method only needs a specific situation you were involved in. Pick one where the stakes and your own decisions are clear, and say plainly where it took place.
What if my result was not a success?
Say so. A clear account of what happened, what you learned and what you changed is usually stronger than an inflated result. Stay with facts you can defend if the interviewer asks a follow-up about alternatives.
- Answer with a real, specific case, using the situation, task, action, result structure.
- Spend most of the answer on what you did, why, and which alternatives you weighed.
- For priorities and change, show the trade-off you accepted and how you communicated it.
- For failures and feedback, name the cause plainly and the change you made afterward.
- Rehearse each answer aloud so it reads as your own account.
Sources
- Structured interviews — U.S. Office of Personnel Management, 26 Oct 2026
- Situation, task, action, result — Wikipedia, 12 Oct 2026
- Assessment and selection: other assessment methods — U.S. Office of Personnel Management, 26 Oct 2026
