"We're a business full of product-minded builders seeking to make it easier for businesses to get started and operate. People come to Stripe because they see a great opportunity to help businesses at scale."
Strong mission attracts builders who care about impact
Patient hiring over speed — willing to meet hundreds of candidates
Build deep personal relationships; wait for the right moment
Learning opportunities matter as much as the role itself
Culture & Hiring
Hiring Philosophy That Built Stripe
Structured, consistent loops: Everyone goes through the same process; no trick questions
Simulate real work: PM exercises, pair programming for engineers, problems close to actual work
Hiring is personal: Managers deeply involved, not delegated to recruiting machines
Patience matters: Critical roles can involve meeting 100+ candidates
Build relationships: If someone isn't available now, stay in touch for the right moment
200
employees before first PM
~5
years of product-minded engineering
The hiring secret
Stripe's early success came from hiring product-minded engineers and building a culture where everyone thinks like a PM — not just those with the title.
Meticulous Craft
Walking the Store & Engineer Occasions
Walking the Store: Leadership regularly joins teams, picks small features to ship end-to-end, experiences the real friction engineers face
Friction Logging: Document all the obstacles encountered — slow builds, unclear docs, approval delays
Clear the calendar: Treat it like vacation to block meetings and get maker time
Share findings: Demonstrate you understand what teams actually experience day-to-day
Do it regularly: New managers should do this in their first 6 months, then annually
The CI/CD impact
Finding places where automation could replace manual processes (e.g., documentation handoffs across time zones) that weren't properly solved yet.
Why it works
You can't guide teams well without understanding what they're actually experiencing. Details matter in infrastructure.
Feedback Loop
The Core Product Principle
"If you have a mechanism to listen to users, get something in their hands quickly, and run feedback loops, you're very unlikely to go wrong."
Find the right early users aligned with your strategy
Get prototypes in their hands rapidly
Close the feedback loop continuously
At Stripe: ship to production continuously so users see changes immediately
If you don't have this loop, build it. If it's slow, make it faster.
Stripe's unfair advantageDeep developer tooling + infrastructure = changes reach users in hours, not weeks
Contrarian
What Stripe Gets Right That Others Don't
✗Hire fast, iterate culture laterINSTEAD →✓ Hire slowly, intentionally. Be patient enough to find people who share your mission and values.
✗PMs build products, engineers executeINSTEAD →✓ Engineers should be product-minded. Stripe went 200 people without a dedicated PM function.
✗Managers should stay away from codeINSTEAD →✓ Leaders must regularly build and ship to understand real friction their teams face.
✗User feedback is optional for buildersINSTEAD →✓ Tight user feedback loops are non-negotiable. If you don't have one, you're building blind.