Behavioral Interview Questions
For both sides of the table: interviewers choosing 'tell me about a time' questions and candidates preparing to answer them. The list is grouped by what each question tests: teamwork and communication, conflict, failure and feedback, leadership, pressure and priorities, and initiative and problem solving. Every note says what the interviewer is listening for and what a strong answer includes, and the guide explains the STAR method (situation, task, action, result) with a worked example, how a rehearsed answer gets probed and which questions suit managers, nurses and teachers.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Teamwork and communication
Tell me about a time you worked as part of a team to reach a goal. What was your role?
Why ask it
The usual teamwork opener. An interviewer is trying to pick one person out of the group: which part was yours, who was waiting on it and what the team got done. Say 'I' for what you did and 'we' for the result, and choose a goal that could have been missed.
Tell me about a time someone on your team was not doing their share.
Why ask it
Nearly everyone has this story, so what gets scored is the order of events. Speaking to the person first, with one specific example and a question about what was in their way, is the start an interviewer hopes for. Going straight to the manager, or carrying the extra work in silence and resenting it, both go down worse.
Describe a time you had to work closely with someone whose personality was very different from yours.
Why ask it
Interviewers ask this to hear what you changed about your own approach. Name the difference in neutral terms, such as one of you planning in detail and the other deciding as they went, then say what you agreed between you. If the story ends with the other person coming around to your way, expect to be asked what you adjusted.
Tell me about a time you helped a teammate who was struggling.
Why ask it
What is being tested is whether you noticed, and how you offered. Say what tipped you off, what you did that left the person more able next time, and what it cost your own work. Quietly redoing their work for them scores less than it sounds.
Tell me about a team project that did not go well. What was your share of the reason?
Why ask it
The second sentence is the point, and it is there because most people describe a bad project as something that happened to them. Name one thing you could have done earlier or differently, and what you do now. A candidate who finds no share at all has answered a different question.
Describe a time your own work depended on someone else finishing theirs first.
Why ask it
Listen for what the candidate did before the date was at risk: agreeing what they needed and by when, checking in early, having a fallback. Waiting and then reporting that the other person was late is the weak answer. A good follow-up is 'when did you first know it might slip?'
Tell me about a time you worked with people from other departments or specialties.
Why ask it
Each group has its own priorities and vocabulary, and the answer shows whether you learned theirs. A nurse might describe working with pharmacy or therapy staff, a teacher with support staff, an engineer with sales. Say what the other side needed from you, not only what you needed from them.
Give me an example of a time you joined a team partway through a project.
Why ask it
Tests how fast someone gets useful without stepping on what is already there. Good stories include reading what existed, asking why things were set up as they were and taking one job off somebody's plate in the first week. It suits a candidate who would be joining an established team, which is most of them.
Describe a time a group you were in could not agree. What did you do to move it forward?
Why ask it
The skill is getting to a decision people will act on, and the answer shows which tools a person reaches for: restating each side, finding what both wanted, proposing a trial, asking whoever owned the call to make it. 'We voted' is fine if you can say what happened to the people who lost.
Tell me about a time you took on a task outside your role so the team could finish.
Why ask it
Shows whether someone puts the group's result above their own job description. The detail to include is whose task it had been and how you squared it with your own work. Interviewers may ask how often this happens, because a person who always fills the gap can be covering for a problem nobody has fixed.
Tell me about a time you worked with teammates you rarely or never saw in person.
Why ask it
Remote and split-shift teams lose the small corrections that happen in a shared room. The answer should say what replaced them: decisions written down, a regular call, an agreement about how fast to reply. Anyone applying for a hybrid or multi-site job should have this story ready.
Tell me about a time you made sure a colleague got credit for their work.
Why ask it
A short question that shows how someone talks about other people. The answer should name the colleague's contribution precisely and say where the credit was given: in the meeting, in the email, to the manager. Asked right after a story heavy with 'I', it also checks whether the candidate noticed anyone else.
Tell me about a time a misunderstanding on your team caused a problem. How did it get cleared up?
Why ask it
The useful part is where the misunderstanding started: an instruction given only out loud, a word two people used differently, a date nobody wrote down. End with the habit you took from it, such as confirming in writing or repeating a request back. Telling it without blaming anyone is a good sign in itself.
Describe a time you had to explain something technical to someone with no background in it.
Why ask it
Nurses do this with families, teachers with parents, engineers with customers. Tell it with the actual comparison or picture you used, the jargon you dropped and the question you asked at the end to find out whether the person could now act on it. 'I kept it simple' tells an interviewer nothing; the comparison itself does.
Tell me about a presentation or a pitch that mattered. How did you prepare?
Why ask it
Aimed at the preparation more than the performance. Start from the audience: what they already knew, what they had to decide and what they were likely to object to. An interviewer can ask which question from the floor was hardest and how it was handled.
Conflict
Tell me about a time you had a conflict with a coworker. How did you resolve it?
Why ask it
Expect some version of this in most interviews, and prepare it first. The interviewer is listening for a disagreement about the work, a direct conversation with the person and an ending both could live with. A story where you were simply right and the other person was difficult will be probed until it falls apart, so choose a real conflict with something at stake.
Tell me about a time you disagreed with a decision your manager made. What did you do?
Why ask it
The person asking is usually a manager, and is picturing being on the other end of it. Say what you objected to and why, where you raised it (one to one beats in front of the team) and what you did once the decision stood. Be ready for 'and who turned out to be right?', and pick a story you can answer that about honestly.
Describe a time you had to calm down an angry customer, patient or parent.
Why ask it
Close to certain for any job that faces the public. Give the person's complaint in their terms first, then what you said in the first minute, what you could put right yourself and what you had to tell them was out of your hands. Take out anything that would identify them, and if they had a point, say so.
Tell me about a time you had to give someone bad news.
Why ask it
The test is whether you delivered it early, directly and yourself. A good answer covers how you prepared, the words you opened with and what you offered next: an option, a new date, a next step. Softening the news until the person did not realize it was bad is a common weak version.
Tell me about a disagreement at work where you turned out to be wrong.
Why ask it
Asked because most conflict stories star the teller as the reasonable one. The interviewer wants the moment you realized, what you said to the other person and whether you argue any differently since. A candidate who cannot think of a single occasion has told the interviewer something as well.
Describe a time two people you answered to wanted different things from you.
Why ask it
Common wherever someone has two bosses: an assistant shared by two managers, a teacher between a department head and a principal, an analyst on two projects. Quietly choosing one and hoping is the weak move. An interviewer wants to hear that you put the clash in front of both, with what each option would cost, and let them settle the order.
Tell me about a time you worked for a manager whose style did not suit you.
Why ask it
A candidate who can describe the mismatch without running the manager down is showing the skill being tested. Useful answers name the difference, such as wanting more detail or less checking, and what the candidate asked for or adapted to. Interviewers should compare the answer with how the real manager works.
Tell me about a time you stepped in between two colleagues who were not getting along.
Why ask it
Mostly asked of managers and team leads, though anyone can be caught in the middle. Look for hearing each person separately, sticking to what the work needed and not ruling on who was the better person. It is also fair to answer that you chose not to step in, if you can say why that was the right call.
Tell me about a time you changed someone's mind at work.
Why ask it
The persuasion question. Tell it from the other person's side: what they believed at the start, what they stood to lose by agreeing and the one fact, example or trial that moved them. Wearing someone down over a month is persistence, and an interviewer can tell it from persuading.
Describe a time you had to enforce a rule that the other person thought was unfair.
Why ask it
Teachers, nurses, supervisors and anyone at a front desk will recognize this one. The balance to show is holding the line while treating the person decently: explaining the reason, offering what you could and not making it personal. A good follow-up is whether the candidate agreed with the rule themselves.
Tell me about a time you had to compromise to keep a piece of work moving.
Why ask it
What you gave up, what you kept and why that was the right trade is the whole answer. Interviewers are checking that a candidate can tell a preference from a principle. If nothing of value was given up, it was not a compromise, so choose a story where it stung a little.
Tell me about a time a colleague was rude or dismissive toward you. How did you respond?
Why ask it
Interviewers are looking for restraint first and a direct word second. A good answer describes what was said, what you did in the moment and whether you raised it afterward in private. Retaliation, a long silence or a story that is still angry in the telling all count against the candidate.
Tell me about a time you spoke up when everyone else in the room seemed to agree.
Why ask it
The answer shows whether a concern gets voiced or swallowed. Strong versions put the concern as a question or a risk, with a reason, and accept the group's decision afterward. Worth asking for roles in safety, finance, quality or patient care, where one unspoken doubt can be expensive.
Tell me about a time you saw a colleague do something unsafe or against the rules. What did you do?
Why ask it
Asked in nursing, childcare, construction, finance and anywhere a shortcut can hurt someone. What counts is that you acted, and in what order: dealing with the immediate risk, speaking to the person, reporting it through the route your workplace sets. Keep the colleague unidentifiable, and do not present 'I stayed out of it' as discretion.
Tell me about a time being honest cost you something.
Why ask it
An integrity question that cannot be answered with a slogan. A real example has a price: a sale lost, an awkward week, a manager annoyed. Interviewers should prefer a small story told plainly to a dramatic one, and should not expect every candidate to have one.
Failure and feedback
Tell me about a time you failed.
Why ask it
Short on purpose: what you choose to call a failure is part of the answer. Pick something that really went wrong and was at least partly yours, spend one sentence on the circumstances and the rest on what you did about it and what you do differently now. A success in disguise, such as working too hard, is an answer interviewers recognize at once.
Describe a mistake you made at work. How did you handle it?
Why ask it
Smaller than a failure and often more telling, because the question is about the first hour afterward. The strong order is: noticed, told the person affected, fixed it, changed something so it would not happen again. Interviewers should be wary of a mistake so small it cost nothing.
Tell me about a time you received feedback that was hard to hear.
Why ask it
The interviewer is working out what it will be like to manage you. Say what the feedback was in the giver's words, how you reacted at first and what you changed, with a later example that shows the change held. Admitting the first reaction was defensive makes the rest more believable.
Tell me about a time you missed a deadline.
Why ask it
What matters is when the other person found out. Give the day you first doubted the date, what you said or sent, the new date you offered and whether you hit that one. 'I have never missed one' usually prompts the interviewer to ask about a near miss.
Give me an example of a goal you set and did not reach.
Why ask it
Differs from the failure question in that the target was your own. Was the goal specific in the first place, how far short did it fall, and did the candidate then adjust the goal, the method or the effort? Sales, fundraising and teaching candidates should expect this in terms of their own numbers.
Tell me about a time you gave a colleague feedback they did not want to hear.
Why ask it
The interviewer is after the wording, so quote yourself: the sentence you opened with, the example you gave and where the two of you were at the time. Then say what the colleague did the following week. If they took it badly, admit it and say what you would phrase differently; that is easier to believe than instant thanks.
Tell me about a time you asked for feedback instead of waiting for it.
Why ask it
Separates people who treat feedback as an event from people who go and get it. The useful details are who was asked, what exactly was asked and what was done with the answer. 'I'm always open to feedback' describes a door left open, which is not the same as going to ask.
Tell me about a time you caught your own error before anyone else noticed. What did you do next?
Why ask it
It sounds like a question about accuracy and is really about what you do when nobody would ever know. The answer being hoped for is that you fixed it and still told whoever needed to know. Interviewers for clinical, financial and safety jobs tend to give it extra weight.
Tell me about a decision you made that turned out to be the wrong one.
Why ask it
Good answers separate a bad decision from a bad outcome: what did you know at the time, what did you miss and could you have known it? The interviewer is also listening for how quickly the decision was reversed once the evidence came in. Defending the decision for most of the answer is the weak version.
Describe a time someone complained about you or your work.
Why ask it
Can the candidate treat a complaint as information? Even where it was partly unfair, the answer should say what was true in it and what was done about that part. Nurses, teachers and anyone in customer service should have one ready, with no names in it.
Tell me about a time you took a risk at work and it did not pay off.
Why ask it
A workplace that wants initiative has to hear about the attempts that missed. Interviewers listen for a risk that was thought through, with a limit on the downside and someone informed beforehand. Candidates can end with what they would still do the same, which often says more than the lesson.
Tell me about a time you made the same mistake twice.
Why ask it
Few candidates prepare for this, so it tends to get an unrehearsed answer. Repeats usually have a cause the first fix did not reach, such as rushing, not writing things down or not asking, and a strong answer names it. Give the candidate time to think; a long pause here is normal.
Tell me about a time you were passed over for something you wanted, such as a promotion or a place on a project.
Why ask it
Disappointment is the subject, and what you did the following week is the answer: whether you asked why, what you took from the reply and how you worked with whoever got it instead. If the story is still told with a grievance, the interviewer will notice before the candidate does.
Tell me about a time you had to admit you did not know something.
Why ask it
Asked a lot in clinical, technical and teaching interviews, where bluffing does harm. The answer should show you said so plainly, found out from a reliable source and came back with the answer. An interviewer can follow up by asking how the other person reacted.
Tell me about a performance review that surprised you.
Why ask it
A surprise in a review means a gap between how you saw your work and how someone else did. The interviewer wants to hear what the gap was, whether you asked for examples and what you did so that the next review held no surprises. A pleasant surprise counts too, if you can say why you had underrated yourself.
Leadership
Tell me about a time you led a team through a difficult project.
Why ask it
The core leadership question, for managers and for anyone who has run a project. Interviewers listen for how the work was divided, how the leader found out it was going off course and what they did then. Spend less time on how hard the project was and more on two or three decisions you made as the person in charge.
Describe a time you had to motivate someone who had lost interest in their work.
Why ask it
Start with how you found out why, since the fix for boredom is different from the fix for feeling overlooked or being worn out. Then give the conversation, the specific change and what you later saw in the person's work. Pep talks and pressure are the weak answers.
Tell me about a time morale on your team was low. What did you do about it?
Why ask it
The group version of the motivation question, and harder, because a team's mood usually has a cause outside any one person: a lost contract, a run of overtime, a decision nobody explained. An interviewer wants the cause named, one thing the candidate changed that was within their power and an honest account of what they could not fix. A team lunch on its own is not an answer.
Tell me about a time you delegated something important. How did you choose the person, and how did you follow up?
Why ask it
Three things are scored: the match between task and person, how clearly the result was described, and the checking afterward. Handing it over and disappearing is one failure; hovering is the other. New managers who still do everything themselves tend to struggle to find an example, which is useful to know.
Tell me about a time you managed someone whose work was not good enough.
Why ask it
A standard for management jobs, and a hard one to bluff. The interviewer wants to hear that the person was told clearly and early, with examples, given support and a fair chance to improve, and that the candidate saw it through wherever it ended. Keep the person unidentifiable and the tone respectful.
Tell me about someone you helped get better at their job.
Why ask it
Good managers and senior colleagues have a name in mind immediately. The answer should say what the person could not do before, what the candidate did, such as coaching, a harder assignment or regular review, and where that person is now. If the candidate takes all the credit for the improvement, ask what the person did themselves.
Describe a time you had to make an important call quickly, with nobody available to ask.
Why ask it
Common in nursing, operations and shift work, where the senior person is not always in reach. Look for what the candidate weighed, what they did to limit the damage if they were wrong and who they told afterward. Candidates should say how they knew the decision was theirs to make.
Tell me about a time you led a change that people resisted.
Why ask it
Resistance usually has a reason, and the answer shows whether the leader went looking for it. Strong stories include explaining why the change was needed, altering the plan where an objection was sound and holding firm where it was not. Ask how many people were still working the new way six months on.
Tell me about a team you took over from someone else. What did you do in the first month?
Why ask it
A fair question for anyone hired to manage from outside, because the first month of the job will be exactly this. An interviewer hopes for time spent with each person, a look at how the work really flowed and one or two early decisions, with the bigger changes held back until the picture was clear. Ask what the candidate kept from the previous manager.
Describe a time you had to choose between what your team wanted and what the organization needed.
Why ask it
A question for managers and leadership roles about where loyalty sits when it is pulled two ways. The interviewer hopes to hear the trade-off explained honestly to the team, without hiding behind 'they made me do it'. The follow-up is how the team took it and what the candidate did to repair things.
Tell me about a time you set a goal for a group. How did you keep people on track?
Why ask it
The answer needs a goal people could measure themselves against and a routine for checking progress that did not depend on the leader chasing everyone. Ask what happened when the group fell behind. Teachers can answer with a class, coaches with a team, managers with a quarter.
Tell me about a time you led people who had more experience than you.
Why ask it
Authority by title does not work here, so the answer shows what the candidate used in its place. Asking the experienced people what they knew, being clear about which decisions were the leader's and giving credit openly are the good signs. A natural question for a first-time manager or an internal promotion.
Tell me about a time a group had no clear leader. What did you do?
Why ask it
Open enough that 'I took the lead' and 'I backed the person who did' can both be strong answers. What the interviewer is checking is whether the candidate read what the group needed. Candidates without management experience can use a school project, a volunteer group or a shift with the supervisor away.
Tell me about a time you had to pass on a decision from above that you did not agree with.
Why ask it
Tests whether a manager can own a message without lying about it. The strong version argued upward first, then explained the decision to the team in their own words and helped make it work. Telling the team 'I don't like it either' buys a moment of popularity and is the answer to watch for.
Tell me about the hardest conversation you have had with someone who reported to you.
Why ask it
What the candidate counts as hardest tells you their range: a warning, a layoff, a refusal of a raise, a personal difficulty affecting work. The marks are for preparation, plain words and respect for the person. Interviewers should not press for private details about the employee.
Tell me about a time you defended your team, or one person on it, to someone more senior.
Why ask it
Most managers say they back their team, and this asks for the occasion. A good answer has the facts gathered first and the case made calmly to the right person. It is stronger still if the candidate also dealt with whatever the team had in fact got wrong.
Tell me about a time you let someone do a task their own way when you would have done it differently.
Why ask it
A test for the manager who cannot let go. The interviewer wants to know how the candidate decided the difference did not matter, and what happened. An honest 'their way turned out better' is one of the best answers available.
Pressure and priorities
Tell me about a time you worked under a tight deadline.
Why ask it
The interviewer wants the method under the rush: what was cut, what was protected and who was kept informed. Say how the deadline came about, since a crisis you inherited reads differently from one you brought on yourself by starting late. Finishing on time by working all night is a result, but the planning is what gets scored.
Describe a time you had several things due at once. How did you decide the order?
Why ask it
A prioritizing question, and the answer should contain a rule: what was due first, what others were waiting on, what would do most harm if late. The telling detail is somebody being told that their item would come second. A candidate who simply did everything has not shown a decision.
Tell me about a time you stayed calm when the people around you did not.
Why ask it
Often asked of nurses, teachers, dispatchers and anyone in front of the public. Describe what was happening, what you did with your voice, your pace and your attention, and what you dealt with first. The claim 'I am good under pressure' needs this story behind it.
Tell me about a time your priorities were changed for you in the middle of a week.
Why ask it
Checks flexibility without using the word. Useful details: who changed the priority and how you heard, what you asked before agreeing, and the message you sent to the person whose work had just moved down the list. A little grumbling in the story is fine if the re-planning is there too.
Give me an example of a big change at work you had to adapt to, such as a new system, a new manager or a restructure.
Why ask it
The adaptability question in its most common form. Two things get noticed: how long the complaining phase lasted, and what the candidate did to get competent in the new arrangement. Helping colleagues through it is a bonus worth mentioning.
Tell me about a time you had to handle an emergency at work.
Why ask it
Emergencies show training and temperament together. A strong answer follows the order of what was done, including the moment help was called, and stays factual. If the role has real emergencies, as a ward, a classroom or a plant does, ask every candidate and compare the answers against your own procedure.
Describe a time you had to get focused work done while being interrupted constantly.
Why ask it
Reception, nursing, teaching and support roles are like this all day, so the question is practical. Good answers have a tactic: batching the interruptions, a signal for 'not now', a note of where they stopped. A candidate who needs long quiet stretches is better off finding that out here.
Tell me about a time you were under heavy pressure at work for weeks, not days. What kept your work steady?
Why ask it
A deadline is a sprint; this asks about the long stretch, such as a busy season, a short-staffed ward or the run-up to exams. Good answers are about arrangements: what was dropped, what was shared out, how the candidate kept mistakes from creeping in. Getting through it on little sleep is not the answer being looked for.
Tell me about a time you had to deliver with fewer people, less money or less time than the job needed.
Why ask it
Scarcity forces choices, and the answer shows whether the candidate made them or let them happen. Listen for what was dropped, what was simplified and what was said to the people expecting the full version. A story where everything was delivered anyway deserves a question about what it cost.
Tell me about a time a small detail mattered a great deal. How did you make sure you got it right?
Why ask it
The attention to detail question, asked as an event. The strong answer includes a checking habit that exists whether or not anyone is watching: a second read, a checklist, a colleague's eyes. In roles with doses, figures, contracts or code, ask about the time the check caught something.
Tell me about a time you realized you had taken on too much. Who did you tell, and when?
Why ask it
Asked because overload that stays hidden becomes missed work. The interviewer hopes to hear that the candidate spoke up while there was still time to move things, and came with a proposal. Candidates sometimes fear this question makes them look weak; naming a limit early is the strong answer.
Tell me about a time something outside your control went wrong. What did you do?
Why ask it
A supplier fails, a system goes down, a colleague is out sick. The answer shows where the candidate's attention goes: to the part still within reach, or to the unfairness. Look for a quick account of the cause and a long account of the response.
Tell me about a time you had to keep doing good work during a difficult period for the team or the organization.
Why ask it
Uncertainty tests steadiness in a way a deadline does not. A good answer says what the candidate chose to concentrate on, what they did about rumor and whether they helped anyone else keep going. Interviewers should stick to the work and not ask about the candidate's personal circumstances at the time.
Initiative and problem solving
Tell me about a time you noticed a problem before anyone else and acted on it.
Why ask it
The standard initiative question. Explain how you spotted the problem, why it was worth acting on and who you told, since fixing things unannounced can cause trouble of its own. Interviewers should ask what would have happened if the candidate had left it alone.
Give me an example of a time you did more than the job asked of you.
Why ask it
Candidates like this question and interviewers have heard every version, so choose an example where the extra step was your own idea and somebody benefited. Say why you judged it worth doing. An interviewer may ask whether it stayed a one-off or turned into something the team kept.
Tell me about the achievement you are proudest of. What did it take?
Why ask it
A friendly question with a serious purpose: your choice shows how big a thing you have carried and what you count as a win. Include the obstacle, your own actions and a result someone else would recognize. Candidates who pick something recent and close to the job make the interviewer's work easy.
Tell me about a goal you set for yourself and how you reached it.
Why ask it
The plan matters more than the prize: the steps, and what happened when progress stalled. A goal with a date and a measure is easier to tell than 'getting better at' something. For an early-career candidate it need not be a work goal: a qualification, a savings target or a race all show the same habits.
Describe a time you found a quicker, cheaper or safer way to do a routine task.
Why ask it
Improvement stories need a before and an after. Say how the task was done, what you changed, how you tested it and whether other people took it up. If you can state the saving honestly, in minutes or errors or money, do; if you cannot, say how you knew it was better.
Tell me about a problem you solved that had other people stuck.
Why ask it
The problem-solving question. The interviewer follows the reasoning: how you defined the problem, what you ruled out and why the answer was not obvious. Give credit to whatever the others had already tried, since it usually narrowed the search.
Tell me about a time you had to pick up a new skill or system with little training.
Why ask it
Every new hire has to do this in the first month, which is why the question comes up. Describe the first day: what you opened, read or watched, the person you sat beside and the first real task you tried on your own. Mention how long it took, because the interviewer is estimating how soon you would be up to speed.
Describe a time you were handed a task and the instructions were unclear. What did you do first?
Why ask it
'What did you do first?' is the half to answer. The convincing first moves are small: one question to the person who set the task, a look at how it was done last time, a rough version shown early to check it was what they meant. Managers who know their briefs are loose should put this to every candidate.
Tell me about a decision you had to make without all the information you wanted.
Why ask it
Say what you knew, what you could not find out in the time and what you did to make the decision easy to undo if it proved wrong. Interviewers ask this of anyone who will have to act before the picture is complete, which covers most jobs with a customer or a deadline in them. 'I waited until I had more data' sidesteps the question.
Give me an example of a time you used numbers or evidence to make your case.
Why ask it
Cover where the evidence came from, how you presented it and whether it changed the outcome. Explain the figures simply, as you did for the original audience. Be ready for 'what would have changed your mind?', which checks that the evidence led to the conclusion and not the other way around.
Tell me about an idea of yours that was put into practice.
Why ask it
Having ideas is common; getting one adopted takes persuasion and follow-through, and that is what is being scored. Describe who had to agree, what objections came up and what the idea did once it was running. Small counts: a new form, a changed schedule, a reworded email.
Tell me about an idea you put forward that was turned down.
Why ask it
Shows how a candidate takes a no. The good versions found out the reason, then either improved the idea and brought it back or dropped it with good grace, and did not go around the person who decided. Sulking and secretly doing it anyway are the two versions to listen for.
Describe a project you carried from start to finish largely on your own.
Why ask it
Shows whether someone can plan, pace and finish without being chased. Ask how they set their own checkpoints and when they chose to get a second opinion. It matters most for remote roles and for any job where the manager is rarely in the room.
Tell me about a time you asked for more responsibility.
Why ask it
Ambition is easy to state in an interview, and this asks when it last showed. The answer should include what you asked for, how you made the case and how you handled the extra load once you had it. If the request was refused, what you did next is just as good an answer.
Tell me about something that took far longer than you expected to get right.
Why ask it
Persistence is what is being tested, along with the judgment to know when to change approach. A good answer shows what kept you going and what you changed between attempts. Interviewers should ask at what point the candidate considered stopping, and why they did not.
Tell me about something you did for a customer, patient or student that nobody would have noticed if you had skipped it.
Why ask it
Gets at standards held when nobody is checking. The best answers are small and specific: a follow-up call, a note left for the next shift, a lesson reworked for one child. Useful for service, care and teaching roles, where most of the good work goes unseen.
Answering and asking behavioral questions: STAR, probing and choosing
Practical guidance for the conversation itself
The STAR method in plain words
What a behavioral question is
A behavioral question asks for something you did, not something you would do: 'tell me about a time', 'describe a time', 'give me an example'. The reasoning is simple. How a person handled a real deadline or a real disagreement is better evidence than their opinion of how they would. So the answer has to be one occasion, with a beginning and an end.
Situation, task, action, result
STAR is an order for telling that occasion. Situation: where you were and what was going on, in a sentence or two. Task: what you in particular were responsible for. Action: what you did, step by step. Result: how it ended and what changed because of it. It is a way of not leaving anything out, and nobody will mark you on naming the letters.
A worked example
Here is the shape, with a made-up answer to 'Tell me about a time you missed a deadline.' Situation: 'I put together the monthly report for our regional manager, due on a Friday.' Task: 'Collecting and checking the figures from two branches was my part.' Action: 'On Wednesday one branch's numbers did not add up. I called the manager that afternoon, told her the full report would reach her on Monday and why, and sent the sections I had already checked so she had most of it on time. Then I went through that branch's entries with their bookkeeper and found a week that had been entered twice.' Result: 'She had the corrected report on Monday morning. I now ask for branch figures two days earlier, and I have not been late with it since.' Spoken, that is about a minute, and more than half of it is action. A real answer has room for a little more detail in the same proportions.
Spend most of the time on the action
A long situation and a rushed ending is the usual way these answers go wrong. As a rough guide, give the situation and task about a quarter of the answer, the action about half and the result the rest. Stopping at around two minutes leaves room for the follow-up questions, which is where the interviewer learns the most.
Say 'I' for what you did
Teams do things together, and it is right to say so, but the interviewer is hiring one person. Use 'we' for the goal and the result and 'I' for your own decisions and actions. If you catch yourself three sentences into 'we decided, we built, we launched', stop and say which part was yours.
End on a result, then on what you learned
State what happened: the order shipped, the patient's family was satisfied, the error rate fell, the colleague stayed. Use a number only if it is true and you could explain where it comes from. For failure questions the result is bad by definition, so the ending is what you changed afterward and a later occasion when the change showed.
Prepare stories, not answers
You cannot predict the questions, but six to eight stories will cover most of them: a team success, a conflict, a failure, a time you led, a time under pressure, something you started yourself, and one or two from the kind of work this job involves. Write each as four short lines under the STAR headings. One story can serve several questions if you change which part you dwell on.
If you have little work history
School projects, part-time jobs, volunteering, sport and caring for family all contain deadlines, disagreements and mistakes. Choose the example where your own actions are clearest, and say where it comes from without apologizing. If you have no example at all, say so and describe what you would do; an invented story tends to come apart at the second follow-up.
How an interviewer probes a rehearsed answer
Why probing is needed
Candidates prepare for these questions, and they should. The cost is that a polished answer can be a story about a team's success with the candidate's own part left vague. Follow-up questions are how an interviewer gets from the prepared version to what happened. They are fair as long as every candidate gets them.
Bring it down to one occasion
If the answer begins 'I usually' or 'I always try to', it is a description of a habit. Say: 'think of one time that happened; when was it?' You have reached a real event when the story has a month in it, a particular person on the other side and a point where it could have gone differently.
Ask for the words and the order
'What did you say to her?' 'What did you do first?' 'What happened the next morning?' Someone who was there can answer these without effort. Someone describing what a good employee would have done slows down, turns general or changes the subject.
Find the candidate inside the 'we'
'Which part of that was yours?' and 'What would not have happened if you had been away that month?' separate the person from the team. Ask them in a neutral voice. Plenty of modest candidates say 'we' out of habit and have a strong answer once asked.
Ask about the part that went badly
Rehearsed stories are smooth. 'What was the hardest moment?', 'what would you do differently?' and 'who disagreed with you?' bring back the rough edges, and a candidate who can supply them is more believable for it. A story with no difficulty in it at all was probably chosen for its ending.
Ask for a second example
One good story can be luck or long preparation. 'Tell me about another time' is the simplest probe there is, and the second example is usually less polished and more typical. Keep it for the two or three qualities the job depends on most.
For candidates: what probing means
Follow-up questions are a sign the interviewer is interested, not a sign the answer failed. Answer them plainly and briefly, and say 'I don't remember exactly' when that is true. The preparation that survives probing is knowing your own stories in detail, not memorizing a script.
Choosing questions for the role
Start from the situations in the job
Before choosing, write the job as a short list of situations: an upset parent at the door, three orders due the same afternoon, a new system every year. Then pick the questions that ask for those situations, a couple for each. With follow-ups, six to eight questions is usually all one interview has room for, and putting the same ones to every candidate is what lets you compare the answers.
For managers and leadership roles
Lean on the Leadership group, and add the Conflict questions about stepping between two colleagues and disagreeing with a manager's decision. Ask for examples about people as well as projects: a poor performer, someone developed, low morale, an unwelcome decision explained. For someone coming in from outside, ask about a team they took over. For a first-time manager, the questions about a group with no clear leader and about leading more experienced people fit best.
For nurses and other clinical roles
Interviewers tend to choose questions about pressure, working with other specialties, upset patients or relatives, explaining something technical in plain words, a colleague's unsafe shortcut and owning an error. Candidates should prepare examples from practice or placements and remove anything that could identify a patient. The interviewer is listening for safe habits as much as for a good outcome.
For teachers
Expect the angry parent, the goal a class did not reach, the disagreement with a colleague over approach, the rule that had to be enforced and the constant interruptions. Answers that work stay specific about what was done and what changed for the student, and keep children and families anonymous.
For entry-level candidates
Choose questions anyone with a school or part-time history can answer: teamwork, a mistake, a deadline, learning something fast, a goal reached. Say at the start that examples from study, volunteering or sport are welcome. Leave the questions about managing people for roles that involve it.
Score the content, not the storytelling
Behavioral answers are stories, and some people simply tell stories well. Before the first interview, turn the note under each question you picked into two or three things you expect to hear, in your own workplace's terms: 'told the customer the same day', 'spoke to the colleague before the manager'. Tick them off straight after the interview. A halting answer that has all three beats a polished one with none.
Common mistakes on both sides
Answering with what you would do
'I would sit down with the person and listen' is an answer to a different question. If no real example comes to mind, ask for a moment to think. A smaller true story is better than a general statement of good intentions.
The failure that is not a failure
'I work too hard' and 'I care too much' are recognized at once. Choose a real failure of moderate size, own your part in a sentence and move on to what you changed. Do not choose one in the central skill of the job you are applying for.
Blaming the other people in the story
Conflict and failure questions invite it. Describe what the other person did in plain terms, without a verdict on their character, and give at least one reason they might have had. Interviewers assume that the way you talk about a past colleague is how you will talk about them.
Leading the candidate
'You would tell your manager straight away, wouldn't you?' gets a yes from everyone. Ask what happened and wait. The same goes for nodding at the answer you hoped for: keep your reactions even until the scoring is done.
Marking honesty down
If an honest account of a mistake scores lower than a smooth non-answer, candidates learn to give non-answers and you learn nothing. Score the handling of the failure: how fast it was owned, what was done and what changed. The size of the mistake matters only if it bears on the job.
Following a story into private territory
Real stories sometimes touch on health, family or other personal matters, especially the ones about pressure. Interviewers should not ask about those, and should bring the conversation back to what happened at work. Candidates never need to share private details to answer well: choose an example that does not depend on them.