40 Behavioral Interview Questions and Answers (With STAR Examples)
The behavioral interview questions employers ask most, grouped by competency, with STAR sample answers, timing guidance and a story bank you can reuse.
Key takeaways
- Behavioral questions ask about what you actually did in the past, because past behavior is treated as the best predictor of future behavior.
- Almost every question maps to one of seven competencies: teamwork, conflict, leadership, failure, problem solving, pressure and ownership.
- Answer with STAR and spend most of the time on the Action: roughly 10% Situation, 10% Task, 60% Action, 20% Result.
- Prepare 8 stories, not 40 answers. A strong story can cover four or five different questions.
- Aim for 90 seconds to 2 minutes per answer, then stop and let the interviewer ask follow-ups.
Contents
Behavioral interview questions ask you to describe how you handled real situations in the past: a conflict, a failure, a tight deadline, a decision you had to make. The best way to answer them is the STAR method: briefly set the Situation and your Task, spend most of the answer on the Actions you personally took, and finish with a concrete Result.
Below are 40 of the most common behavioral questions, grouped by the competency they test, with sample answers, timing guidance and a simple system for preparing once and reusing your stories across interviews.
Why interviewers ask behavioral questions
Interviewers have a simple problem: everyone says they are a team player who works well under pressure. Behavioral questions replace claims with evidence. Instead of “Are you good with conflict?”, they ask “Tell me about a disagreement with a colleague”, and listen for what you actually did.
The questions are rarely random. Most companies use a list of competencies for the role and ask one or two questions for each. If you know the competencies, you can predict most of the questions.
How the 40 questions in this guide are distributed. Your interview will weight them by role.
- Teamwork and collaboration7
- Conflict and difficult people6
- Leadership and influence6
- Failure and learning5
- Problem solving and decisions6
- Pressure and time management5
- Ownership and initiative5
How to answer: the STAR method in one minute
STAR stands for Situation, Task, Action, Result. It is popular because it forces a short setup and a clear ending, and it makes your own contribution visible.
Recommended share of your speaking time. Most weak answers spend too long on the Situation.
A few rules make STAR answers noticeably stronger:
- Say “I”, not “we”. Interviewers are hiring you, not your team. Describe the team’s work briefly, then your part in detail.
- Make the result concrete. Numbers are best (time saved, revenue, error rate, customers). If you have none, describe what changed and how you know.
- Add one sentence of reflection for failure and conflict stories: what you would do differently.
- Stop after the result. A good answer invites follow-ups; it does not try to pre-empt them.
For a deeper walkthrough with more examples, read our full STAR method guide.
Build a story bank instead of memorizing 40 answers
You cannot memorize answers to every possible question, and you should not try: memorized answers sound memorized. Instead, prepare a small set of flexible stories.
- List 10 moments from the last 3–5 yearsProjects you are proud of, mistakes, disagreements, launches, crises, times you taught or led someone.
- Keep the best 8Prefer recent, specific stories where your own actions changed the outcome.
- Write each as 4 bullet pointsOne line each for S, T, A and R. Bullets, not paragraphs, so you do not memorize sentences.
- Tag each story with competenciesMost stories cover 3–5 competencies. A launch story can show pressure, ownership and teamwork.
- Add a number to every ResultPercentages, time, money, users, defects. Estimate honestly if exact data is unavailable.
- Say each story out loud twiceTime it. Cut until it fits in about 2 minutes.
| Story | Teamwork | Conflict | Leadership | Failure | Problem solving | Pressure | Ownership |
|---|---|---|---|---|---|---|---|
| Rescued a delayed product launch | ✓ | ✓ | ✓ | ✓ | |||
| Disagreed with my manager on priorities | ✓ | ✓ | |||||
| Shipped a bug that reached customers | ✓ | ✓ | ✓ | ||||
| Onboarded and mentored a new hire | ✓ | ✓ | |||||
| Automated a manual reporting process | ✓ | ✓ | |||||
| Took over a project from a leaving colleague | ✓ | ✓ | ✓ |
Teamwork and collaboration questions
- Tell me about a time you worked on a team to achieve a difficult goal.
- Describe a situation where you had to work with someone whose style was very different from yours.
- Give an example of how you helped a teammate who was struggling.
- Tell me about a time you had to rely on others to finish your work.
- Describe a project where you collaborated with another department.
- Tell me about a time you received feedback from a peer. What did you do with it?
- How have you contributed to a team you were not leading?
What interviewers listen for: you share credit, communicate proactively and adapt to others without giving up on the goal.
S On a checkout redesign I was paired with a designer who liked to explore many options before committing, while I prefer to decide early and iterate in code.
T We had six weeks and needed a tested design and a working prototype by week four.
A In our first meeting I asked how she liked to work and explained my own habits. We agreed on two-day “explore” windows where I did not push for decisions, followed by a short review where we picked one direction. I built quick throwaway prototypes of her top two ideas so we could test them with five users instead of debating. I also shared my technical constraints early, so she did not spend time on options we could not build.
R We delivered the prototype a few days early, and the new checkout increased completed payments by 6% in the A/B test. We kept the explore-then-decide rhythm for the next two projects.
Conflict and difficult people questions
- Tell me about a time you disagreed with your manager.
- Describe a conflict with a coworker and how you resolved it.
- Give an example of dealing with a difficult customer or stakeholder.
- Tell me about a time you had to deliver bad news.
- Describe a time someone did not do their share of the work.
- Tell me about a time you had to say no to a request.
What interviewers listen for: you stay calm, focus on the problem rather than the person, use data and reach a resolution that works for the business.
S My manager wanted to add a new reporting feature to our next release, two weeks before the deadline.
T I owned the release plan, and I believed adding the feature would put the date and the quality of the main feature at risk.
A I asked for 20 minutes to discuss it and prepared a short comparison: the remaining work, our current bug count and an estimate of the reporting feature. I started by asking what the request was meant to achieve. It turned out a key customer needed one specific export, not the whole feature. I proposed shipping the release as planned plus that single export as a CSV, and building the full reporting feature in the following sprint.
R My manager agreed, the customer got the export on time and the release went out with no critical bugs. Since then I start disagreements by asking about the goal behind the request, which usually reveals a smaller solution.
The safest structure for conflict stories
Show that you understood the other side before pushing your view, that you used facts rather than opinions, and that the relationship was fine afterwards. Never make the other person the villain of the story.
Leadership and influence questions
- Tell me about a time you led a project or team.
- Describe a time you persuaded others to adopt your idea.
- Give an example of how you motivated a team during a hard period.
- Tell me about a time you had to lead without formal authority.
- Describe a time you had to make an unpopular decision.
- Tell me about someone you mentored. What was the outcome?
What interviewers listen for: you set direction, bring people along with reasons rather than rank, and take responsibility for the outcome. Leadership questions are asked of individual contributors too, so prepare at least one story even if you have never managed anyone.
Failure and learning questions
- Tell me about a time you failed.
- Describe a mistake you made at work and how you handled it.
- Tell me about a time you missed a deadline.
- Give an example of feedback that was hard to hear.
- Describe a time a project did not go as planned.
What interviewers listen for: honesty, ownership without excuses, and a concrete change in your behavior afterwards. The reflection matters more than the mistake.
S In my first year as an analyst I built a weekly revenue dashboard that the sales team started using to set targets.
T I was responsible for the data pipeline behind it.
A I tested the dashboard against last month’s numbers, but not against refunds, which were processed in a separate system. Three weeks later a sales lead noticed that one region looked 8% better than finance’s report. I told my manager the same day, traced the issue to the missing refunds, fixed the query and sent a short note to everyone using the dashboard explaining what had been wrong and which numbers to correct.
R The fix was live within two days and no targets had been finalized yet. Since then I write a reconciliation check against finance data for every new metric, and I added that step to our team’s dashboard checklist.
Problem-solving and decision questions
- Tell me about the most difficult problem you solved at work.
- Describe a time you had to make a decision without all the information.
- Give an example of a process you improved.
- Tell me about a time you used data to make a decision.
- Describe a creative solution you came up with.
- Tell me about a time you had to choose between two good options.
What interviewers listen for: how you break a problem down, which options you considered, how you decided and how you checked the result.
Pressure and time management questions
- Tell me about a time you worked under a tight deadline.
- Describe how you handled several competing priorities.
- Give an example of staying calm in a stressful situation.
- Tell me about a time you had too much work. What did you do?
- Describe a time you had to adapt quickly to a change.
What interviewers listen for: prioritization with clear criteria, communication about trade-offs, and protecting quality where it matters.
Ownership and initiative questions
- Tell me about a time you went beyond your job description.
- Describe a problem you noticed and fixed without being asked.
- Give an example of a goal you set for yourself and how you reached it.
- Tell me about a time you took responsibility for something outside your role.
- Describe the accomplishment you are most proud of.
What interviewers listen for: you notice problems, act without waiting for permission where appropriate, and follow through to a result.
Common mistakes in behavioral interviews
Strong
- A specific moment: “In March, during the migration…”
- Your own actions, in order, with reasons
- A result with a number or a visible change
- A short reflection for failures and conflicts
- About 2 minutes, then stop
Weak
- A general habit: “I usually try to…”
- “We did…” for the whole answer
- No ending, or “and it went well”
- Blaming a colleague, manager or client
- Five minutes of context before the action
Two more traps worth naming:
- The fake weakness. “I work too hard” or “I’m a perfectionist” in a failure question signals that you are avoiding the question. Read our guide to answering “What is your greatest weakness?” for honest alternatives.
- The hypothetical answer. If asked “Tell me about a time…”, do not answer “I would…”. If you truly have no example, say so briefly, then describe the closest real situation.
How to handle follow-up questions
Good interviewers dig into one story with follow-ups: Why did you choose that approach? What would you do differently? What did your manager think? This is where prepared but not memorized stories pay off.
- Pause before answering. Two seconds of thinking looks confident, not slow.
- Go one level deeper, not wider: details of the same situation, not a new story.
- It is fine to say what you do not know (“I didn’t see the final numbers, but the team lead told me…”).
Behavioral questions by role
The competencies are the same everywhere, but the examples interviewers expect differ by role:
| Role | Most-weighted competencies | Example question |
|---|---|---|
| Software engineer | Ownership, problem solving, collaboration | Tell me about a production incident you handled |
| Product manager | Influence, decisions with incomplete data, conflict | Tell me about a time you said no to a stakeholder |
| Data analyst / scientist | Problem solving, communicating findings | Describe a time your analysis changed a decision |
| Sales / customer success | Pressure, difficult customers, initiative | Tell me about a deal you lost and what you learned |
| Manager | Leadership, difficult conversations, hiring | Tell me about a time you managed underperformance |
More role-specific questions are in our behavioral interview questions list and the questions by role section.
During the interview: keeping your structure
Even with good preparation, it is easy to lose structure when a question arrives that you did not expect. A real-time interview copilot like Sottena can help here: it detects the behavioral question as it is asked and shows a short STAR outline built from the stories in your interview context, so you can pick the right story and keep the answer on track. Use it in line with the rules of each interview.
Frequently asked questions
What is a behavioral interview question? +
How long should a behavioral interview answer be? +
What if I don't have work experience for a behavioral question? +
Can I use the same story for several questions? +
Is it okay to talk about a failure? +
What is the difference between behavioral and situational questions? +
Get a STAR outline the moment a behavioral question is asked
Sottena listens to the interviewer, detects each question and shows short answer points in about a second. 150 free credits, no card required.