40 Behavioral Interview Questions and How to Answer Them

Behavioural interview questions — usually opening with "Tell me about a time..." — dominate hiring loops because past behaviour is the best evidence interviewers have for future performance. Forty prompts cover most competency frameworks employers use, even when wording shifts. This guide groups them by theme, explains what each question is designed to surface, and gives concise STAR-oriented guidance for answering. Sixteen questions get full question cards with hidden intent and answer structure; the remaining twenty-four are listed by theme so you can map them to your story bank without reading forty separate scripts.

How behavioural interviews work

Structured behavioural interviewing uses predefined questions tied to competencies — leadership, collaboration, problem solving, integrity. Interviewers take notes against rubrics and compare candidates on evidence, not gut feel alone. That is why vague answers hurt: assessors cannot tick indicators if you never describe what you did. Follow-up probes — "What was your role specifically?" "What would you do differently?" — test whether the story is yours and whether you reflect.

Leadership and influence (questions 1–8)

Leadership questions do not require a manager title. Interviewers want proof you mobilise others, develop people, and make decisions under uncertainty. Weak answers describe personality ("I am a natural leader"); strong answers describe a moment with stakes.

• 4. Tell me about a time you motivated a disengaged team member.
• 5. Describe a situation where you had to influence stakeholders without direct authority.
• 6. Give an example of when you took initiative without being asked.
• 7. Tell me about a time you had to make an unpopular decision.
• 8. Describe how you have handled underperformance on your team.

For influence without authority, document how you built credibility — data, pilots, written agreements — before asking others to change. For underperformance, show fair process: clear expectations, documented feedback, support offered, and outcome whether improvement or exit.

Weak vs strong: leadership example

Weak: "I led a project and everyone looked to me for direction. I kept the team motivated and we succeeded."

Strong: "When our lead quit mid-sprint, I volunteered to run stand-ups, split stories by skill, paired junior devs with seniors, and escalated a scope cut to the PM on day three. We shipped the release with one non-critical item deferred; velocity recovered next sprint."

Conflict and communication (questions 9–14)

These questions test whether you can disagree without damaging relationships and communicate bad news clearly. Interviewers fear candidates who avoid conflict until it explodes, or who burn bridges when challenged.

• 12. Tell me about a time miscommunication caused a problem — how did you fix it?
• 13. Describe a time you had to persuade someone to see your point of view.
• 14. Give an example of receiving constructive criticism you disagreed with at first.

Failure, pressure, and resilience (questions 15–22)

Failure questions filter for accountability and learning. Pressure questions filter for judgment when time and resources are constrained. Candidates who blame others or claim they never fail fail these prompts.

• 19. Tell me about a time you missed a deadline — what happened?
• 20. Describe the most stressful work situation you have faced.
• 21. Give an example of staying calm when others panicked.
• 22. Tell me about a time you had to restart or pivot a project.

Customer focus and teamwork (questions 23–30)

Customer questions apply beyond support roles — any role with internal or external clients. Teamwork questions probe whether you share credit, cover gaps, and resolve friction without escalation.

• 25. Tell me about a time you worked on a cross-functional team.
• 26. Describe a situation where you helped a colleague who was struggling.
• 27. Give an example of receiving help from a teammate — how did you respond?
• 28. Tell me about a time you had to collaborate with someone difficult.
• 29. Describe a team project that did not go as planned.
• 30. Tell me about a time you shared credit or advocated for a colleague's contribution.

Cross-functional stories should name roles — product, legal, sales — and show how you aligned incentives. "Difficult colleague" answers must stay professional: focus on work behaviours, not personal attacks.

Adaptability and problem solving (questions 31–36)

Employers hire for change velocity — new tools, reorgs, market shifts. These questions test whether you learn fast and decide with incomplete data.

• 34. Tell me about a time you solved a problem in a creative or unconventional way.
• 35. Describe a time you identified a problem before others noticed it.
• 36. Give an example of using data to drive a decision.

Problem-solving structure

1. 1State the problem in one sentence with stakes.
2. 2Explain options you considered — even briefly.
3. 3Describe the action you chose and why.
4. 4Close with measurable or observable result.

Integrity, judgment, and inclusion (questions 37–40)

Closing themes cover ethics, transparency, and how you behave when no one is watching. Regulated industries weight these heavily; startups increasingly ask them too as scale brings compliance and culture risk.

• 37. Tell me about a time you saw someone else behave unethically — what did you do?
• 38. Describe a time you had to balance competing priorities fairly.
• 39. Give an example of making a workplace more inclusive or welcoming.
• 40. Tell me about a time you stood up for someone or an idea that was overlooked.

For ethics involving others, show proportionate response — verify facts, address directly, escalate when needed. For inclusion, concrete actions beat virtue statements: changing interview rubrics, amplifying quiet voices in meetings, fixing biassed language in docs.

Mapping forty questions to eight stories

You do not need forty unique stories. Build eight core narratives and tag them by competency. Example: a vendor delay story can answer tight deadline, escalating, influence without authority, and handling stress depending on which Action you emphasise.

Follow-up probes to prepare for

• "What was your specific role versus the team's?" — Use first person for your actions.
• "What would you do differently?" — Honest improvement, not fake regret.
• "What happened six months later?" — Long-term impact or sustained change.
• "How did others react?" — Social awareness without gossip.
• "Why that example?" — Connect back to the role you are interviewing for.

Preparation workflow

1. 1Highlight competencies in the job description.
2. 2Match each competency to one story from the last three years.
3. 3Write STAR bullets for each story — not full scripts.
4. 4Crosswalk this list of forty questions; note which story answers which prompts.
5. 5Run two timed mocks with follow-ups — alone or with Assisted Voice or a peer.
6. 6After each real interview, update stories with new metrics or sharper Results.

Behavioural prep rewards repetition across days, not cramming. Sleep helps you retrieve stories under pressure; a rested candidate adapts when interviewers rephrase question 7 as "Describe a setback you owned." For deeper STAR examples across twenty competencies, see our STAR method guide; for overlap with classic fit questions, see common interview questions.