If you've interviewed at a big company, you've probably hit a round that felt different from the rest. The interviewer wasn't on the team you'd join. They asked more about how you work than what you've built. That's usually a bar raiser.
The name comes from Amazon, but plenty of companies run some version of it now. The format varies. The intent doesn't. Someone outside the hiring team is there to keep the bar high, to make sure the team isn't grading on a curve because they're desperate to fill a seat.
Here's what that round is really testing, and how to be ready for it.
They're testing your judgment, not your resume
The hiring manager already likes your background. That's why you're this far. The bar raiser isn't re-checking whether you can code. They're checking whether you make good calls when things are messy.
So the questions skew toward decisions. Why did you pick that approach? What did you give up? What did you do when you found out you were wrong?
The strong answers all share one trait: a clear reason behind the choice. Not "we used Postgres because that's what we knew," but "we used Postgres because we needed transactions and the data was relational, and the team could operate it." Same decision, completely different signal.
They're testing whether your stories hold up under follow-ups
This is the big one. A bar raiser will pick one story and stay on it. First question is broad. Then they dig.
"You said you led that migration. What did the other engineers actually do?" "You said it improved performance. By how much, and how did you measure it?" "What would you do differently?"
People who exaggerate fall apart here. Not because lying is hard, but because real stories have texture. You remember the annoying edge case, the meeting where you got pushback, the thing that broke in production at 11pm. Made-up stories are smooth and empty.
So bring stories you actually lived. Pick three or four projects you can talk about for ten minutes each without running dry. Know the numbers, know the tradeoffs, know what went wrong. If you only owned part of it, say so. "I owned the API layer; a teammate handled the data pipeline" is a stronger answer than vaguely claiming the whole thing.
They're testing ownership
Most bar raiser rubrics have some version of "does this person take responsibility." It shows up in small ways.
Watch your pronouns. If every success is "we" and every failure is "they," that gets noticed. The opposite is just as bad - claiming sole credit for team wins reads as someone who'll be hard to work with.
The cleanest pattern: "we" for outcomes, "I" for your specific contribution, and honest ownership of mistakes. "We missed the deadline, and part of that was on me - I underestimated the testing work" lands well. It signals you can be trusted with hard problems because you won't hide from them.
They're testing how you handle being wrong
Almost every bar raiser asks some flavor of "tell me about a time you failed" or "a time you disagreed with someone." They're not collecting horror stories. They want to see what you learned and whether you can disagree without being a jerk.
For failure stories, skip the fake ones ("I work too hard"). Pick a real miss, explain what happened, and spend most of your time on what you changed afterward. The recovery is the point.
For conflict stories, show that you can hold a position and also update when you're wrong. "I pushed for the rewrite, the team pushed back, we talked it through, and I came around once I understood the migration cost" is a great answer. It shows spine and flexibility at once.
How to prep for it
You can't game this round, but you can be ready.
- Write out four or five real stories. For each one, jot the situation, your specific role, the decision and why, the outcome with a number if you have it, and what you'd change.
- Practice out loud. The follow-ups are where people stumble, so have someone push on your stories until you hit the edges of what you remember. A mock interview is good for exactly this.
- Be honest about scope. Inflated stories are the fastest way to fail a bar raiser, because the whole round is built to find the seams.
The bar raiser isn't trying to trip you up. They're trying to figure out if you'd raise the level of the team or lower it. The best way through is the simple one: bring real work you understand deeply, own your part of it honestly, and show that you get sharper when things go sideways.