Behavioral interview questions, grouped by what they test
Most behavioral rounds come back to the same few themes. The wording changes from company to company (Amazon, for example, ties its questions to its Leadership Principles), but if you have an example ready for each group below, you can adapt it to the question you actually hear. Each group starts with what the interviewer is trying to learn. Not interviewing for an engineering role? Our behavioral interview questions and answers cover every role, with example answers.
Disagreement and conflict
Whether you understood the other point of view, and how a decision actually got made.
- Tell me about a time you disagreed with another engineer on a technical decision. How did you resolve it?
- Describe a time you pushed back on a product requirement. What happened?
- Tell me about a time you disagreed with your manager.
- Describe a conflict on your team. What was your part in resolving it?
- Tell me about a code review where you and the author didn’t agree.
Ownership and impact
What you personally decided and did, and how you know it made a difference.
- Tell me about a project you’re proud of. What was your part?
- Describe an improvement you took responsibility for without being asked.
- Tell me about a time you went beyond your assigned work to fix a problem.
- What’s the most useful thing you’ve shipped? How do you know it helped?
- Tell me about something you owned from the first design to launch.
Ambiguity and problem solving
How you decide what to look at first when the answer isn’t obvious.
- Tell me about a problem where the next step wasn’t clear. How did you decide what to investigate?
- Describe a time you had to decide without all the information you wanted.
- Tell me about the hardest bug you’ve tracked down.
- Describe a time the requirements changed partway through a project.
Mistakes and setbacks
Whether you can talk about something that went wrong without hiding your part in it.
- Describe a release that didn’t go as planned. What did you do once you understood the problem?
- Tell me about a mistake you made. What did you change afterward?
- Tell me about a deadline you missed. When did you tell the people affected?
- Describe a project that failed. What would you do differently?
- Tell me about a time you received critical feedback. What did you do with it?
Working with others
How you get things done with people who see the work differently.
- Describe a time you helped another engineer or team get unstuck.
- Tell me about working with a difficult teammate or stakeholder.
- Describe a time you explained a technical tradeoff to someone without an engineering background.
- Tell me about a time you mentored someone. What changed for them?
- Describe a project that depended on another team. How did you keep it moving?
Priorities and pressure
What you chose not to do, and why.
- Tell me about a time you had too much to do. How did you decide what to drop?
- Describe a time you had to choose between shipping quickly and doing it more thoroughly.
- Tell me about a time you worked to a tight deadline.
- Describe a time you said no to a request.
Influence, more often asked for senior roles
How far your decisions reached beyond your own work.
- Tell me about a time you got a team to adopt your approach without authority over them.
- Describe a technical decision you made that affected other teams.
- Tell me about a time you improved code quality, testing, or reliability across a team.
- Describe a time you changed your mind after hearing someone else’s argument.
Motivation and growth
Whether this role makes sense for you, in your own words.
- Why do you want to work here, and why this role?
- Tell me about something you taught yourself recently.
- What kind of work gives you energy, and what drains it?
- Where do you want to grow over the next couple of years?
You don’t need a separate story for every question. Start with a few experiences, check which questions they actually answer, and add others where you find a gap. The next sections show how to choose them and explain an engineering decision.
Start with one example from your own work.
Open the job description, pick a responsibility, and choose an experience that shows how you’ve handled it. Give someone a short answer: what was happening, what decision did you make, and what happened afterward? Then ask them to choose a follow-up you haven’t prepared.
Pick three responsibilities from the job description and write down one experience for each. You only need a few notes at this point. If you can’t explain what your part was, mark that example and come back to it.
Start with the responsibilities you’ll actually take on. A project can be impressive and still tell the interviewer very little about how you’d approach this role. Choose examples where you can explain the decisions and your contribution in enough detail to answer questions.
The worked answer shows what this looks like with an Android rollout disagreement. Let’s first build a small set of examples you can use.
Choose a few stories you know well.
Begin with about five experiences. There’s nothing special about that number; it’s just a manageable place to start. You can add more when you find a question or responsibility your examples don’t cover.
Look for situations where you had to make a decision, work through uncertainty, or change your approach. To make this concrete, think about mobile products for food delivery, messaging, or property listings. These fictional situations are prompts to help you recall your own work, not experiences to claim as your own:
- A disagreement
- a food-delivery app is moving its order-tracking screen from polling to live updates. One engineer wants a single cutover; another wants to start with staff orders. What makes each approach reasonable?
- An ambiguous problem
- an exercise app using on-device pose estimation misses repetitions when the phone is placed at an angle. Is the next step a model change, a camera-position guide, or a better way to flag an unreliable reading?
- A setback
- a messaging screen loads quickly with short conversations but freezes while opening a long history with photos. How did you find the case your performance checks missed, and what did you tell the team about the release?
- Taking ownership
- a property-listing draft loses its photos when an upload fails. How would you work through saving the draft, retrying the upload, and making sure the same photo isn’t attached twice?
- Helping someone else
- several Android squads share a module that makes small edits trigger long rebuilds. How did you identify the dependency, agree on a smaller boundary, and help another squad move without blocking its release?
These will overlap, which is fine. An incident might give you something to say about judgment, communication, and learning. You can focus on the part relevant to the question while keeping the facts the same.
Write notes you can work from.
For each example, note the situation, your responsibility, the options you considered, what you did, and what happened afterward. Add what you learned, if it changed how you work. Also note anything you don’t remember clearly. It’s better to notice that now than fill in a convincing detail while you’re talking.
Name the system and the user action. “The Android order-tracking screen showed an old delivery status after reconnecting” gives someone far more to work with than “I improved a service.” You can explain that without sharing internal project names or customer data.
If you haven’t managed people, that’s fine too. Think about the influence you’ve had through your actual work: getting a design adopted, resolving a dependency, or helping someone understand a tradeoff. Explain the scope you had rather than trying to make the story sound like a management example.
Explain the engineering decision.
Use STAR for the overall structure. In an engineering answer, make the technical choice understandable: what behavior was wrong, which options you considered, what you owned, and how you checked the change.
In the fictional order-tracking example, “we improved reliability” hides the decision. A clearer account says: “I owned the Android rollout and reconnect checks. We kept each order on one update path and started with staff orders; another engineer fixed the version check that rejected older status events.” That distinguishes your work from the team’s and gives the interviewer a decision to examine.
Describe a result someone could check. For that rollout, an older event stopped moving the screen from “Picked up” back to “Preparing.” For a build-time story, compare the same edit and build before and after, including whether the cache was warm. Use a measurement only if you can explain it. The worked rollout answer shows the full revision and follow-ups.
The follow-up questions are worth practicing separately.
Pick a question from the list above and answer it with one of your stories. Then ask someone to choose a follow-up from below. If you’re preparing for a senior role, choose an example where you can explain the scope of your decision and its effect on other people’s work.
Once you can tell the story, try asking something that makes you look at it from a different angle. This is where you may find that you remember the outcome better than the reasoning that led to it.
- What was reasonable about the other approach?
- Did anything change your mind?
- What would you have done if the team chose the other option?
- What did you know at the time, and what became clear later?
- When did you tell the people affected?
- What did you change afterward? Have you used that change since?
- Which part depended on something you personally did?
- How do you know the result was an improvement?
- What did you leave unfinished, and why?
These are practice questions, so don’t treat them as a list to predict your interview from. Change their order, or ask a partner to choose one. You want to get used to thinking about the question you’ve just heard.
And sometimes the honest answer is “I don’t remember the exact number” or “That wasn’t my decision.” You can explain what you do know and where your responsibility ended. Practicing that is useful too.
Practice for your target company
Paste the job link and practice the behavioral and technical rounds that company runs, with real follow-up questions. Your first round is free.
For engineering interview loops by employer, see our guides for Anthropic, Bloomberg, Databricks, and Stripe.
If you have a week, here’s how to use it.
Adjust this around the time you actually have. Each session should leave you with something useful for the next one, rather than another pile of notes to read.
Choose the examples
Go through the role and pick your initial stories. Write short notes and check whether you can explain your contribution. Identify anything you need to remember or verify.
Give it a first try
Answer two questions aloud. Record yourself if you’re comfortable with that, or ask a practice partner where they lost the thread. Try to finish even if you stumble. Restarting every time can leave you very well practiced at the first sentence.
Work on one thing
Pick a problem from that attempt. If your contribution wasn’t clear, work through what you personally decided and did. If the decision seemed arbitrary, explain the alternative and why you chose against it.
Try the follow-ups
Use the questions above on the same stories. Pay attention to where you need time to think, where you’re missing a fact, and where the question assumes something that didn’t happen.
Have a longer conversation
Try a behavioral round with a partner or an AI interviewer. Our comparison of AI practice, partners, and coaches can help you choose. Mix the questions so you have to choose your example in the moment. If you want to use RoundHound, here’s how behavioral practice works.
Revisit what was difficult
Keep something that worked well and choose one thing to improve. After a short exercise on that part, try a different question that needs the same skill. Can you explain your contribution clearly in another story too?
Give yourself some room
Review your notes and the interview instructions. Check that you know which examples relate to the role, then leave them alone for a bit. Don’t spend the last evening rewriting every answer. You’ll need room to listen and think in the actual conversation.
How do you know whether it’s helping?
After an answer, ask whether the listener could explain what you were responsible for, why you made the decision, and what happened afterward. Check that you answered the question you were asked. A well-told story can still go in the wrong direction.
Look for feedback you can act on. “Be more confident” doesn’t give you much to try. “Explain the decision before going through the alternatives” gives you a change you can make in your next answer.
If you’re using AI feedback, read it critically. It may misunderstand your explanation or suggest something that doesn’t fit the experience. Go back to what you said and decide whether there’s a useful point in it.
Then try another round. If you can explain the difficult part more clearly without relying on a script, you’ve made progress. There’s still no way to rehearse every question, but you’ll have a better grasp of your own examples and more practice thinking them through when someone asks a follow-up.
If you’d like to see the exercise worked through, start with the example answer. If you already have a story in mind, give behavioral practice a try.
