25 Behavioral Interview Questions and How to Answer Them

Behavioural questions rarely sit in their own dedicated round. They are spread through a normal hiring process, with each stage taking a different slice.

1. Recruiter or phone screen (20–30 minutes). One or two behavioural questions at most, usually about motivation, notice period and a recent piece of work. This stage tests basic fit and whether you can describe your own job clearly.
2. Hiring manager interview (45–60 minutes). The heaviest behavioural round. Questions map directly onto the job description, and the manager is checking whether you have done the work before or something close to it.
3. Panel or interview loop. Several interviewers, each assigned different competencies so they are not all asking the same thing. SHRM advises employers to use the same set of core questions and criteria for every candidate, both for consistency and to avoid legal problems (SHRM, undated), so expect scripted stems and note-taking.
4. Task, presentation or work sample. Not always used. Where it is, the follow-up discussion is usually behavioural: why you made that choice, what you would do differently.
5. Final conversation. Often a senior leader or a values-focused interview, testing judgement and how you handle disagreement.

Seniority changes the questions more than the structure. Early-career candidates get simpler stems and are usually allowed to draw on classes, class projects and volunteer work; CareerOneStop recommends exactly that for candidates without extensive work history (CareerOneStop, 2023). Senior candidates get asked about scope, ambiguity, conflict with peers and organisation-level results. Number of rounds and how long the process takes vary widely by employer, sector and country — ask the recruiter at the screen.

Behavioural interviewing exists to measure past behaviour as a predictor of future performance (MIT Career Advising & Professional Development, 2023). These are the competencies most often behind the questions.

• Achievement and effort — shows up as "tell me about a goal you set" and probes into what you personally did versus what the team did. O\NET lists Achievement/Effort among the 21 Work Styles variables in its Content Model (O\NET Resource Center, undated).
• Stress tolerance — O\NET defines this as a tendency to remain calm and composed and to manage emotions effectively in response to criticism or difficult situations at work (O\NET OnLine, undated). It appears as deadline, criticism and crisis questions. CareerOneStop calls describing how you handle deadlines and high-stress situations the most common behavioural question (CareerOneStop, 2023).
• Judgement and decision-making — tested by questions about incomplete information, trade-offs and decisions you would now make differently. Listening, speaking and decision-making skills appear in the BLS profile for human resources specialists, who do much of this interviewing (BLS, undated).
• Collaboration and influence — questions about difficult colleagues, cross-team work and persuading people you do not manage. O\NET's Soft Skills tool treats Negotiation, Persuasion and Social Perceptiveness as distinct skills (O\NET OnLine, undated).
• Accountability and learning — failure and mistake questions. CareerOneStop's practice question "Describe a major failure at work, and how you dealt with it" comes with the advice to emphasise what you learned and what you did to avoid a repeat (CareerOneStop, undated).
• Communication — assessed continuously, not by a specific question: whether your answer has a clear situation, a clear action and a clear result, or wanders.

Behavioural questions typically open with stems such as "Tell me about a time when…" or "Give me an example of when…" (Northwestern University Career Advancement, undated). Here are 25 you should be ready for.

General

• Tell me about yourself and the work you do now.
• Why this role, and why now?
• What are you looking for in your next manager and team?
• Tell me about a time you set a goal and reached it.
• Tell me about a time you had to learn something quickly.
• Give me an example of feedback that changed how you work.
• What kind of work drains you, and how do you handle it?
• Tell me about a time you asked for help.

Experience

• Tell me about a time you worked under a tight deadline.
• Describe a project you owned end to end.
• Tell me about a time you disagreed with your manager.
• Give me an example of working with a difficult colleague.
• Tell me about a mistake of yours that affected someone else.
• Describe a time you had to juggle competing priorities.
• Tell me about a time you improved a process or removed a step.
• Give me an example of delivering bad news to a customer or stakeholder.
• Tell me about a time you persuaded someone you had no authority over.

In-depth

• Describe a major failure at work and how you dealt with it.
• Tell me about a decision you made without all the information you wanted.
• Tell me about the harshest criticism you have received and what you did next.
• Describe a time you pushed back on a request from someone senior.
• Tell me about a time you changed your mind after new data.
• Give me an example of choosing the slower, more thorough option.
• Tell me about managing your own workload through a sustained period of pressure.
• Describe a time you inherited a problem you did not create.

Tell me about a time you worked under a tight deadline

Why they ask: stress tolerance and prioritisation. CareerOneStop describes deadline and high-stress questions as the most common behavioural question of all (CareerOneStop, 2023), so this is the one to have polished.

How to approach it: name the deadline, say what made it tight, then spend most of your answer on the choices you made — what you cut, who you told, what you checked. Finish with whether the deadline was met and at what cost.

Payroll coordinator, manufacturing company, about 380 employees

Our payroll provider changed its import file format four working days before the monthly run. I mapped the old fields to the new ones in a spreadsheet, tested with a batch of 20 records, and found two deductions importing to the wrong column. I told my manager the same morning rather than waiting until I had a fix, and asked finance to delay a separate reporting request by a week so I had clear days. I re-ran the full file twice and checked 30 records by hand against the previous month. Payroll went out on the scheduled date with no corrections needed afterwards, and I wrote a one-page mapping note so the next person would not start from scratch.

Mistake to avoid: saying you "worked late and got it done", which tells them nothing about judgement. Fix: name one thing you deliberately dropped or delayed to protect the deadline.

Describe a major failure at work and how you dealt with it

Why they ask: accountability and learning. CareerOneStop's own guidance to candidates on this question is to emphasise what you learned and what you did to avoid a repeat (CareerOneStop, undated) — which is exactly what the interviewer is scoring.

How to approach it: pick a real failure with a visible consequence, own your part in the first sentence, and spend half the answer on the fix and the change that outlasted it. Do not choose something that questions your basic honesty.

Marketing executive, subscription software business

I sent a renewal discount email to the wrong segment — roughly 12,000 contacts, including people already on an annual plan. I spotted it from the reply volume within 20 minutes. I paused the campaign, told my manager and the support lead immediately so they had an answer ready, and drafted a short correction email that went out the same afternoon honouring the discount for anyone who had already clicked. That cost us a small amount of revenue but no complaints escalated. The root cause was that I had duplicated an old segment instead of building a new one. I added a two-person check on any send over 1,000 contacts and a test-send to an internal list, and we have not repeated it.

Mistake to avoid: choosing a failure that was really someone else's. Fix: use the words "I" and "my decision" at least twice in the first three sentences.

Tell me about a time you disagreed with your manager

Why they ask: judgement and professional courage — whether you can challenge a decision without damaging the relationship or the work.

How to approach it: show the disagreement was about evidence, not preference. Say how you raised it, what you would have done if you had lost, and then say clearly what actually happened, including if you were overruled.

Software engineer, five-person product team

My manager wanted a payments change released on the Friday to hit a sprint commitment. I thought the rollback path was untested, which on a payments flow meant a real risk of failed transactions over the weekend with no one on call. I asked for ten minutes before standup, showed him the two test cases we had not covered and offered an alternative: release behind a feature flag on Friday, enable it for 5% of traffic on Monday morning. He agreed to the flag. We enabled it Monday, found a currency-rounding bug at 5% affecting a handful of transactions, and fixed it before full rollout. If he had said ship it anyway, I would have shipped it and written the risk down in the release notes.

Mistake to avoid: telling a story where you were right and your manager looks foolish. Fix: include one thing their position had going for it.

Give me an example of when you persuaded someone you had no authority over

Why they ask: influence and persuasion, which O\NET treats as a distinct social skill alongside Negotiation and Social Perceptiveness (O\NET OnLine, undated).

How to approach it: name the person's actual incentive, not just your own case. Show what evidence you brought and what you conceded to get the decision.

Customer support team lead, consumer app

Roughly 90 tickets a week came from one broken password-reset flow, but engineering had it ranked low. I tagged three months of tickets in Jira so I could show the volume, then worked out the handling time — about 12 hours of support time a week — and framed it as engineering time versus support time rather than as a complaint. I also offered something: if they fixed it, my team would write the help-centre article and handle the comms so it cost them nothing beyond the code. The tech lead took it into the next sprint. Tickets from that flow dropped to under 30 a week, and I kept the tagging going so I had the same evidence ready for the next argument.

Mistake to avoid: describing persuasion as "I explained it again more clearly". Fix: name the thing you offered or gave up.

Tell me about a time you made a decision without all the information you wanted

Why they ask: decision-making under ambiguity. Decision-making skills are listed among the key qualities for human resources specialists, the people often running these interviews (BLS, undated), and they are looking for the same thing in you.

How to approach it: state what you did not know and why you could not wait. Explain the assumption you made, how you limited the downside, and how you checked afterwards.

Operations team leader, retail distribution site

A supplier confirmed a delivery slot but could not tell us the case count until the truck arrived. I had to book agency staff 48 hours ahead. With no figure, I used the average of the last six deliveries, rounded up by 10%, and booked four agency workers instead of the six a full load would need — with an agreement that I could call two more in for a four-hour block if needed. The load came in heavier than average, I called the extra two at 7am, and we cleared the bay by the end of the shift. I also started logging actual case counts per supplier in a shared sheet so the next person had real numbers rather than a guess.

Mistake to avoid: implying you always wait for full data. Fix: say plainly what the cost of waiting would have been.

Tell me about the harshest criticism you have received and what you did next

Why they ask: stress tolerance, defined by O\NET as remaining calm and composed and managing emotions effectively in response to criticism or difficult situations at work (O\NET OnLine, undated).

How to approach it: quote the criticism roughly as it was given, including that it stung. Then move quickly to what you checked, what you changed and how you know it changed.

Graduate civil engineer, consultancy

A senior engineer returned my drainage drawings in front of two colleagues and said they were not checkable — inconsistent levels, no revision history. That was hard to hear. I asked him afterwards to show me two specific pages he would consider acceptable, and I rebuilt my set against them. I also started using the practice's drawing checklist properly instead of from memory, and self-checked against it before every submission. On the next three packages he raised 4 comments in total, down from 20-odd on the first. He later asked me to check a junior's drawings, which I took as the real answer.

Mistake to avoid: picking criticism so mild it is really a humblebrag. Fix: choose feedback you can still remember the wording of.

Describe a time you had to juggle competing priorities

Why they ask: prioritisation and stakeholder management — whether you decide, or just absorb pressure until something breaks.

How to approach it: show that you made the conflict visible to someone rather than silently choosing. Name the criteria you used to rank the work.

Project coordinator, engineering services firm

In one week three managers asked for the same two days of my time: a tender submission with a fixed Thursday deadline, an internal dashboard rebuild, and a client site visit. I put all three in a list with the deadline, who was blocked and what happened if it slipped, and took it to my line manager for 15 minutes. The tender was the only hard deadline with money attached, so that won. The site visit moved to the following Tuesday after I called the client myself, and I agreed a two-week extension on the dashboard. The tender went in a day early. I kept that list running in Trello afterwards so the trade-offs were visible before people asked, not after.

Mistake to avoid: saying you "managed to do all three". Fix: name the one that moved and who you told.

Tell me about a time you improved a process

Why they ask: initiative and innovation — O\NET includes Innovation among its Work Styles variables (O\NET Resource Center, undated). They want evidence you change things rather than just complete them.

How to approach it: start with the measurable irritation, not the idea. Show you measured before and after, and that the change stuck once you stopped pushing it.

Clinic administrator, three-site GP practice

We were losing around 40 appointment slots a month to no-shows. I checked a month of them by hand and found most were appointments booked more than two weeks ahead. I asked for a small trial: an SMS reminder 48 hours before, sent from the booking system we already paid for, plus a one-line script for reception to confirm the mobile number at booking. I ran it at one site for six weeks and compared it with the other two. No-shows at the trial site fell by about half; the others were flat. I wrote a one-page procedure, trained the four reception staff, and it rolled out to all three sites. It still runs now that I have moved on.

Mistake to avoid: describing the idea and skipping the adoption. Fix: say who you trained and how you know they kept doing it.

Give me an example of delivering bad news to a customer or stakeholder

Why they ask: communication and composure under pressure, plus honesty when there is an incentive to soften the truth.

How to approach it: say what the bad news was in one sentence, as you said it to them. Then cover what you offered, what you did not promise, and where the relationship ended up.

Account manager, digital agency

Two weeks before a client's campaign launch, our developer went on long-term sick leave and I knew we would miss the date by about ten days. I called the client the same afternoon rather than emailing, told her the launch would slip to the 24th, and said plainly that it was our resourcing problem, not a scope issue. I brought two options: a reduced launch on the original date with two of the five landing pages, or the full launch ten days later. She took the reduced launch. I sent a written recovery plan with named owners and dates within two hours, and gave her a weekly Friday update she had not asked for. We delivered the remaining pages on the 24th and she renewed the retainer that quarter.

Mistake to avoid: delaying the call until you have a full solution. Fix: tell them the date you know, then follow with the plan the same day.

Describe a time you inherited a problem you did not create

Why they ask: ownership. Interviewers use this to separate people who fix things from people who document whose fault it was.

How to approach it: acknowledge the history in one line and then drop it. Everything after that should be what you did with what you were handed.

Shift supervisor, warehouse and fulfilment site

I took over a shift where the handover notes had stopped being filled in and stock discrepancies were running at 15–20 items a week. I did not go back over who had let it slide. I spent my first two weeks on shift with the pickers, and found two real causes: a bay layout where two similar SKUs sat next to each other, and a scanner that failed silently when its battery dropped low. I moved the SKUs apart, got the three worst scanners swapped, and rebuilt the handover as a five-line form that took under a minute. Discrepancies dropped to two or three a week within a month. I shared the form with the other two shift supervisors rather than keeping it to my team.

Mistake to avoid: spending a third of the answer establishing that it was not your fault. Fix: give the history one sentence, then move to your first action.

CareerOneStop advises preparing questions that show real interest in the job and the organisation, and specifically suggests asking about day-to-day responsibilities and how performance will be measured (CareerOneStop, undated). These five do that without sounding rehearsed.

• What does a normal week in this role actually look like? Tells you whether the job description matches the work, and gives you concrete detail for any later round.
• How will you know in six months that this hire went well? Surfaces the real success criteria, which are often narrower than the advert suggests.
• Which competencies were you assessing in this conversation? Shows you understand how structured interviewing works and often gets you a straight answer about gaps.
• What happened to the last person in this role? Distinguishes a growth hire from a backfill, and sometimes reveals a problem you would be inheriting.
• What are the next stages, and who will I meet? Lets you prepare the right examples for the right interviewer, and gives you a timeline to follow up against.

• Build six to eight stories, not 25 answers. Cover: a deadline, a failure, a conflict, a decision under ambiguity, an improvement, and a piece of influence. Most of the 25 questions above are these six stories asked from a different angle.
• Write each one in STAR shape. DDI says it introduced the STAR Method in 1974 as part of its Targeted Selection programme and has shaped behavioural interviewing for over 50 years (DDI, undated); the four components are Situation, Task, Action and Result (Big Interview, undated). One line each for Situation and Task, three or four for Action, one for Result.
• Attach a number to every story. A count, a timeframe, a volume, a before-and-after. Check it is defensible before you use it.
• Read the job description and mark the competencies. CareerOneStop recommends gathering information about the position, organisation and industry to anticipate which behavioural questions are likely (CareerOneStop, 2023). Map each of your stories to at least one line in the advert.
• Prepare early-career examples if you need them. Classes, class projects and volunteer work are legitimate sources where work history is short (CareerOneStop, 2023) — just give them the same structure and result.
• Say two answers out loud, timed. Aim for 90 seconds to two minutes. Anything over three minutes is losing the interviewer.
• Write down your five questions and the recruiter's name. Take them in on paper; nobody minds notes.