Search for the Stripe loop and you'll find plenty: how many rounds, what happens in each one, what the take-home looks like. All of it changes constantly, and the people who can tell you are candidates who interviewed there last month. This playbook does something different, and honestly more useful over a two-week prep window: it tells you what Stripe's own leaders have said, on the record and on camera, about the bar they hire and operate against.
This article starts with what we can't tell you and where to go for it, then covers what Stripe's executives say they value, how those values show up in the questions they ask, the stories to build before you interview, a prep exercise taken from the CTO's own monthly routine, and questions to ask them back. Read the values section first, then spend your prep time building three stories, because that's where most candidates are thinner than they realize.
The sources are David Singleton, Stripe's CTO when he described their hiring process in May 2023; Claire Hughes Johnson, who was Stripe's COO from about 160 employees to over 7,000 and wrote Scaling People; Katie Dill, Stripe's head of design, previously at Airbnb and Lyft; and Will Larson, CTO at Carta and formerly an engineering leader at Stripe, Uber, and Digg. Every quote below plays the exact moment it was said.
What this playbook will not tell you
We don't have reliable information about Stripe's current interview loop. How many rounds you'll get, which order they come in, whether there's a take-home, how long the onsite runs, and what the current rubric names are all things that change from year to year, team to team, and level to level. Anyone writing a confident "the Stripe loop in 2026" post without recent first-hand data is guessing, and a wrong guess will waste your prep.
So go get the schedule from people who have it:
Where to get current loop specifics
- Your recruiter. Ask directly: how many rounds, what each one covers, who's on the panel, and whether anything is take-home. Recruiters answer this happily and it costs you nothing.
- Blind, Levels.fyi, and Glassdoor. Filter to posts from the last few months and to your role and level. Older posts describe a process that has probably moved.
- People who work there now. A referral or a warm intro gets you a much better description than any article. The referral playbook covers how to ask.
The rest of this article covers the part that doesn't change much. The values Stripe hires against have been stated publicly by three different executives across three years, and they line up.
What Stripe's leaders say they value
Stripe runs on what it calls operating principles rather than values. David Singleton, then CTO, described them as behaviors distilled from the most effective people at the company (23:04 in his episode), and said they get used constantly: people cite them when celebrating each other's work, and feedback processes are framed around them. Two come up over and over from different leaders.
Users first. Singleton names it as the very first operating principle at 23:26. In practice it works as the tiebreaker for where effort goes.
Be meticulous in your craft. Katie Dill, Stripe's head of design, says this one is expected of everybody, not just designers.
Meticulous craft applies to every job. The player below is queued to 52:33, the exact moment Katie Dill explains how the principle shows up in roles that have nothing to do with design. Watch on YouTube.
"Our operating principles include meticulous craft. And it is one of the things that is really important to us as an organization, is just like having that meticulous care for all that you do, like whether it's you're designing the space that we work within, or that you're creating the API, or that you're building the interface, or that you're talking to people on support calls. The meticulous craft is something that is actually expected of everybody."
Dill also gives you the vocabulary to talk about quality precisely, which matters because "I care about quality" on its own tells an interviewer nothing. She describes levels: does the thing work at all, does it work well and error-free, and does it exceed what the user was even looking for. If you can place your own past work on that scale and explain why you stopped where you stopped, you're already talking the way her team talks.
The levels of quality. The player below is queued to 11:52, the exact moment Katie Dill lays out the scale from baseline to exceeding expectations. Watch on YouTube.
"There are levels of quality. There is the, does the thing work, does it provide some sort of value proposition, does it execute on its job? That's baseline quality. Next is, does it do it exceedingly well, is it error free? And then beyond that, like level three, level four, level five, does it exceed expectations and do something that you weren't even seeking for as a user?"
If you are interviewing for a design role specifically, our design interview playbook covers how Dill and other design leaders disagree about whether your portfolio case needs to point at a metric.
Singleton's favorite example of the craft principle is small and specific, which tells you something about what "meticulous" means there. At 25:04 he describes joining Stripe and hitting an error from their API, then finding that the error message linked straight to the docs page explaining the fix. His comment: "Like the error messages on your API, who's ever going to look at them? Well, turns out developers, while they're building and if they're running into problems, they will look at them. It's actually a really high-stakes moment."
Will Larson, who was an engineering leader at Stripe before becoming CTO at Calm and then Carta, adds one more that's worth knowing about. He mentions "optimize globally" as a Stripe value, though he notes he believes it's no longer one, and explains it as choosing what's better for the whole organization even when something else would be better for your own team. If you have a story where you gave up a local win for a company-level one, that's the shape of story that lands at a company with this instinct.
What the CTO said about how Stripe interviews
In May 2023, Singleton described the design philosophy behind their loops. Formats will have moved since, but the philosophy is the kind of thing that persists, and it changes how you should prepare.
He said Stripe uses structured loops so every candidate for a role goes through a consistent process, which lets interviewers calibrate what a strong answer even looks like. Then he said the thing that should change your prep:
Nothing is a trick question. The player below is queued to 15:08, the exact moment David Singleton describes what Stripe's interview exercises are designed to be. Watch on YouTube.
"The other thing that these loops have in common is nothing is a trick question. Like we try to put people into an environment which is as close to doing the actual work together as you possibly can. So for engineers for instance, we've got several different coding exercises that they do. They share their screen with the interviewer. It's actually kind of pair programming. You're welcome to use Google, to search Stack Overflow."
He goes on at 15:48 to say the PM side had a written exercise drawn from real problems, done in your own time with a suggested time limit, and that what they were watching for was whether you attack the problem in a way that's curious, digs into the details, and stays collaborative with your interviewer.
Two practical things follow from that, if the philosophy still holds when you interview. First, treat every exercise as collaboration, because he says out loud that asking your interviewer questions is welcome. Second, don't grind trick puzzles. Practice narrating your reasoning while you work, because a screen-shared pairing session scores how you think out loud at least as much as what you produce.
The question three Stripe leaders say they ask
When Lenny's Podcast compiled favorite interview questions from more than 100 guests, Katie Dill, Karri Saarinen of Linear, and Camille Hurst all named the same one: tell me what work you're most proud of. Dill explains what she's listening for, and it's the clearest statement of the Stripe bar you'll find in a single sentence.
Taste and judgment, from one question. The player below is queued to 10:10, the exact moment Katie Dill explains why she asks candidates what work they're most proud of. Watch on YouTube.
"Tell me what work you are most proud of. And the reason I ask that is because it helps me understand their taste and their judgment, what motivates them, what work they view as good and as a good outcome. It also helps me understand a little bit about what they like to do, and where their kind of gravity pulls them."
Read that list again, because it's close to a scoring rubric. She's checking what you consider good, which is a question about your standards, and where your energy naturally goes, which is a question about fit. Whether the project was impressive matters far less. A candidate who answers with the biggest number on their resume tells her almost nothing about either.
Build three stories that show craft and judgment
Most people prepare stories about outcomes. At a company that talks like this, spend your prep on the decisions inside those stories. Pick three pieces of work and rebuild each one around the choices you made rather than the result you got.
Story one: the quality call
- A time you spent more effort on something than anyone asked for, and could explain why that specific detail mattered to a specific user.
- Say where the work landed on Dill's scale, and where you chose to stop. "We got it to error-free and deliberately didn't go past that, because the deadline mattered more to this customer than polish did" is a strong answer.
- Have the counter-story ready too: a time you shipped something rougher on purpose. If every story you tell is about polish, an interviewer starts to wonder whether you can prioritize.
Story two: the details nobody else went into
- Singleton's example of great work is a PM who kept asking whether a painful government process really had to work that way, and eventually got the IRS to change how a number gets issued (13:32). That's the kind of story: curiosity that didn't stop at the first "that's just how it is."
- Find your version. Where did you dig two levels below where your job required, and what did you find?
Story three: the global call over the local one
- A time you chose the option that was worse for your team and better for the company, and can name what it cost you.
- Name who you had to convince and how. This is where interviewers hear whether you can influence without authority.
For all three
- Say what you'd do differently. A story with no revision in it sounds rehearsed.
- Keep the setup under 30 seconds. Interviewers want the decision more than the org chart.
- Name real tradeoffs with real losses. Nobody believes "we got everything we wanted."
The behavioral interview questions playbook covers the general mechanics of structuring these answers, and how to position yourself for a job covers choosing which stories to lead with for a particular role.
How Stripe's former COO reads people
Claire Hughes Johnson ran Stripe's operations from roughly 160 people to over 7,000, and she wrote the book on how she did it. Her first operating principle is about self-awareness, and it's directly relevant to how you'll come across in an interview.
Build self-awareness to build mutual awareness. The player below is queued to 33:20, the exact moment Claire Hughes Johnson names her operating principles and explains the one about strengths. Watch on YouTube.
"My operating principles in the book, one is build self-awareness to build mutual awareness. Another one is say the thing you think you cannot say. I've come to believe that often your biggest strength is also your weakness, but two, it's something that you don't know is a big strength, because it's almost like breathing."
Her method for getting there, described from about 30:34 onward, is to write down your top few values, then the story behind each one, then what she calls your work style tendencies: whether you run introverted or extroverted, and whether you lean task-oriented or people-oriented. Doing that exercise before you interview gives you something most candidates don't have, which is a real answer to "what are you like to work with" that isn't a repackaged strength.
Her second principle is worth practicing out loud, because interviews are full of moments where the honest thing feels risky. At 35:32 she gives two tactics: ask a question instead of making a statement, and own the observation as yours rather than passing judgment. Compare "I wonder if I'm missing something about how these two teams overlap" with "that team was misaligned." Only the first one gets you a conversation. In an interview, that's how you disagree with a premise without sounding difficult.
Say the craft part out loud
Work Coach records you telling a story and marks where you jumped to the result and skipped the decision. It drills the same story with follow-ups until the judgment comes out.
Start Free Trial2-week trial, no credit card needed. Your data is never shared with your employer.
Write a friction log before you interview
This is the most useful Stripe-specific prep you can do, and it comes from the CTO describing his own routine. Stripe uses a practice called friction logging: you pick a specific user, walk their end-to-end path through the product, and take detailed notes on every place it gets hard.
The CTO does this once a month. The player below is queued to 33:20, the exact moment David Singleton describes his own friction log habit. Watch on YouTube.
"For years and years, I have gone through the process of onboarding as a user to Stripe once a month, writing a friction log, and then tagging in the right people across the company that might need to take action on some of the things that we're observing."
He explains the method itself at 25:48. The important part is picking a specific person first. "A developer" is too vague. Pick an engineer at a particular kind of company doing a particular integration. Then you go through it for real, in the dashboard and the docs and the code, writing stream-of-consciousness notes and flagging every point of friction that person would hit.
Your pre-interview friction log
- Pick one user and write them down in a sentence. A solo founder taking their first payment, a developer adding a subscription tier, a finance person reconciling payouts.
- Do the flow yourself. Sign up, read the docs, write the integration if you can. Test mode is free.
- Note friction as you hit it, not afterward. Timestamps, the exact wording that confused you, the moment you had to open a second tab.
- For your top three points of friction, write what you'd change and why that specific user cares.
- Bring two of them into the conversation, and open with something like "I ran a friction log on your onboarding flow and got stuck here."
Do this for whichever surface matches the job. Design candidates should log a visual and flow-level pass, PM candidates should log the end-to-end job, and engineers should actually build the integration.
Why good candidates still get turned down
Will Larson, now CTO at Carta and formerly an engineering leader at Stripe and Uber, models hiring as a pipeline. When he walks through where pipelines break, the most common failure has nothing to do with candidate quality. He's describing hiring pipelines generally rather than Stripe's specifically, but it's a useful reframe for anyone interviewing at a high-bar company.
The bottleneck is usually conviction. The player below is queued to 14:32, the exact moment Will Larson describes the most common place hiring pipelines stall. Watch on YouTube.
"For a lot of pipelines, the biggest issue is hiring managers don't want to extend any offers because the hiring managers can't get to confidence on any candidate. And you'll see a ton of candidates getting to offer stage but almost none of them converting."
Your job in the loop is to make conviction easy to reach. That means being specific enough that an interviewer can repeat your story accurately to someone who wasn't there, and consistent enough across rounds that four people come away with the same picture of you. Answers that sound strong but stay vague are the ones that fall apart in the debrief.
The other half of conviction happens after your last round. At 1:10:55, Singleton says Stripe pays a lot of attention to references, and gives the reason: an interview loop gets you maybe eight hours with someone, while people who've worked with them are drawing on thousands of hours. So line your references up early. Tell them which role it is, which stories you told, and what you'd like them to be able to speak to. That isn't coaching them to lie. It just means the person who saw your best work is the one who picks up the phone.
If you're heading into a full onsite, the final-round playbook covers how to prepare for a whole panel in sequence, and preparing in 24 hours covers what to cut if the loop is tomorrow.
Questions to ask them back
Every question below comes out of something a Stripe leader has said publicly, which means you're asking about things the company actually talks about internally rather than fishing for a compliment.
About craft and quality
- "Where does this team choose to be meticulous, and where do you deliberately accept rough edges?"
- "What's a recent example of quality work on this team that wouldn't show up in any metric?"
- "Who does the friction logging here, and what happens to what they find?"
About the work itself
- "What's the hardest decision this team made in the last six months?"
- "Which users do you have the clearest picture of, and which ones do you wish you understood better?"
- "What would I be expected to have shipped or figured out by month three?"
About how you'd work together
- "How do you like to give feedback, and how quickly?"
- "What's something people find hard about working with you?" Claire Hughes Johnson's whole self-awareness argument says a good manager has an answer ready.
- "What made the last person in this role successful, or not?"
Ask two or three, not the whole list. And write down what they say, because the answers are your best material for the follow-up email and for deciding whether you want the job.
Frequently asked questions
How hard is it to get hired at Stripe?
It's hard, and it's slow on purpose. Singleton described being patient on hiring, especially for leadership roles, and said they're happy to meet tens or hundreds of people for a role and to keep building a relationship with someone who isn't ready to move yet (10:05). Plan for a longer process than you'd expect, and don't read silence as rejection.
What is Stripe's culture actually like?
The consistent picture from three executives: mission-driven and unusually explicit about it, heavy on writing, high on autonomy, and detail-obsessed in a way that shows up in small things like API error messages. Singleton says they don't hide any of that during hiring (9:46), because caring about the mission is close to a requirement. He also describes an environment where lots of people end up doing a different job than the one they were hired for, which is a real perk and also a warning if you want a narrow, stable role.
Should I mention that I used the product?
Only with specifics. Saying you love Stripe's docs gets you nothing. Saying you built a test integration for subscriptions, got stuck at a particular step, and here's what you'd change gets you a real conversation. That's the whole point of the friction log above.
Is Stripe's interview process the same for engineers, PMs, and designers?
Singleton said in 2023 that the structure was consistent across roles, with exercises tailored to each: pair-programming-style coding for engineers, a written exercise for PMs. What each of those looks like now, and what design gets, is exactly the kind of specific your recruiter should confirm.
What if I'm not a payments person?
Singleton says the space rewards people who want to learn a lot of detail about systems that aren't well understood outside the industry (11:58). Nobody expects you to arrive fluent in interchange fees. They do want evidence that you go deep on unglamorous things, so lead with a story where you learned a boring domain thoroughly because the work required it.
Your Stripe prep on one page
First, get the facts we can't give you
- Ask your recruiter for the exact loop: rounds, formats, panel, take-home.
- Read recent first-hand accounts filtered to your role and the last few months.
- Find someone who works there now and ask what the team is actually working on.
Then build the material
- Three stories: a quality call, a time you dug two levels deeper than required, and a choice that was better for the company than for your team.
- One counter-story where you shipped something rough on purpose.
- Your answer to "what work are you most proud of," rebuilt around what you consider good rather than what looked biggest.
- Your values and work style tendencies written down, so "what are you like to work with" has a real answer.
Then do the work they do
- Run a friction log on the surface closest to the job. Pick one specific user first.
- Write down your top three friction points and what you'd change.
- Practice narrating your reasoning while you work, since exercises may be collaborative and screen-shared.
Before and after the loop
- Line up references early and tell them which stories you told.
- Pick two or three questions to ask back, and write down the answers.
- Keep your story consistent across every interviewer, because the debrief is where conviction gets built.
Sources
- Lenny's Podcast: Building a culture of excellence, with David Singleton, CTO of Stripe (May 2023)
- Lenny's Podcast: Lessons from scaling Stripe, with Claire Hughes Johnson, former COO of Stripe (Mar 2023)
- Lenny's Podcast: Building beautiful products with Stripe's head of design, Katie Dill (Oct 2023)
- Lenny's Podcast: My favorite interview questions from 100+ guests (Nov 2023)
- Lenny's Podcast: The engineering mindset, with Will Larson, CTO of Carta (Jan 2024)