I wasn't expecting the behavioral round at Stripe to be the one I thought about most afterward, but here we are.
Stripe calls it a "values interview" and it's a dedicated 45-minute round with one interviewer. Not tacked onto the end of a coding session. Its own thing. That tells you they're serious about it.
The questions I got (paraphrased): Tell me about a time you disagreed with a technical direction your team was taking. What did you do, and what happened? Describe a situation where you had to make a decision without all the information you wanted. How did you decide? Tell me about a time you failed. Not a "failure that turned out great" story. A real one. When have you had to push back on a stakeholder's request? How did you handle it?
The last one threw me. They're probing for honesty and self-awareness, not polish. I started to give a "failure that was really a learning opportunity" answer and the interviewer literally asked: "Was it actually a mistake? What did you lose?" Not in a mean way, genuinely curious. But that was a signal that they're trained to catch vague-polished answers.
Stripe's operating principles are public and it's worth reading them before the loop. Things like "users first," "move with urgency and focus," "think rigorously" come up in interview rubrics. But they're testing whether you actually live these, not whether you can recite them.
My prep: I wrote out 8-10 specific stories from the past 3 years with real context, real mistakes, real numbers where possible. Each story mapped to 2-3 different question types. Don't prep 20 shallow stories. Prep fewer deeper ones.
One thing I noticed about the interviewer's style: she kept asking "and then what?" after every answer. They want to hear how things resolved and what you learned, but they're specifically interested in the messy middle, not just the tidy conclusion.
I got an offer. Pending comp negotiation. Happy to answer specific questions.