Courses › Behavioral Interviews › Question Themes

40 Common Questions

The questions that come up most, grouped by competency, with what each one probes.

These are the questions that come up most often in software engineering behavioral interviews, grouped by the competency they probe. For each group, make sure your story bank has at least two stories that fit.

Introduction and motivation

• Tell me about yourself.
• Why do you want to work here?
• Why are you leaving your current role?
• What are you looking for in your next team?
• Where do you see yourself in a few years?

[!TIP] "Tell me about yourself" 90 seconds: your current role and scope → one or two highlights with impact → why this role. Not your life story, and not a list of technologies.

Ownership and initiative

• Tell me about a time you took ownership of something outside your responsibilities.
• Describe a time you noticed a problem nobody else was addressing.
• Tell me about a time you went above and beyond for a customer or user.
• Tell me about a project you drove from idea to launch.

Collaboration and conflict

• Tell me about a disagreement with a teammate.
• Tell me about a time you disagreed with your manager.
• Describe working with a difficult stakeholder.
• Tell me about a time you had to compromise.
• Describe a time you worked across teams to deliver something.

Leadership and influence

• Tell me about a time you led without formal authority.
• Describe a time you convinced others to adopt your idea.
• Tell me about a time you mentored someone.
• Tell me about a time you improved how your team works.

Ambiguity and decision-making

• Tell me about a project with unclear requirements.
• Describe a decision you made with incomplete information.
• Tell me about a difficult technical trade-off.
• Tell me about a time you had to change direction mid-project.

Execution and prioritization

• Tell me about a time you met a tight deadline.
• How do you prioritize competing demands?
• Tell me about a time you had to cut scope.
• Describe a time you delivered a project under significant constraints.

Failure, mistakes and feedback

• Tell me about a time you failed.
• Tell me about a mistake that affected others.
• Tell me about critical feedback you received.
• What's a weakness you're working on?
• Tell me about a production incident you were involved in.

Impact and technical depth

• What's the most impactful project you've worked on?
• Tell me about the most technically challenging problem you've solved.
• Describe a time you improved performance, reliability or cost.
• Tell me about a technical decision you're proud of — and one you regret.

Growth and learning

• Tell me about a time you had to learn something quickly.
• How do you stay current technically?
• Tell me about a time you changed your mind about something important.

Values and judgment

• Tell me about a time you pushed back on something you thought was wrong.
• Describe a time you had to balance speed against quality.

How to practice

• Answer 5–10 of these out loud each day in the week before your interviews.
• Time yourself: 2–3 minutes per answer.
• After each, ask: did I say what I did? Did I give a result? Did I reflect?
• Practice the behavioral questions in the question library with the hints and approaches, then do a mock interview.