Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
How we scaled Stripe from 4 to 94 employees
Search
Greg Brockman
April 02, 2014
Technology
2
1.6k
How we scaled Stripe from 4 to 94 employees
My talk from BV.IO 2014.
Greg Brockman
April 02, 2014
Tweet
Share
More Decks by Greg Brockman
See All by Greg Brockman
How cryptocurrencies can succeed
gdb
2
1.6k
Rescuing Ruby
gdb
1
1.1k
Building better software through mathematics
gdb
4
1.6k
Shipping at Stripe
gdb
1
790
Building a Culture Where Software Projects Get Done
gdb
3
1.2k
Other Decks in Technology
See All in Technology
Bill One 開発エンジニア 紹介資料
sansan33
PRO
4
16k
MySQL AIとMySQL Studioを使ってみよう
ikomachi226
0
130
Design System Documentation Tooling 2025
takanorip
1
860
ページの可視領域を算出する方法について整理する
yamatai1212
0
150
IPv6-mostly field report from RubyKaigi 2026
sorah
0
250
Databricksによるエージェント構築
taka_aki
1
110
AI開発の定着を推進するために揃えるべき前提
suguruooki
1
470
一億総業務改善を支える社内AIエージェント基盤の要諦
yukukotani
9
2.6k
Dify on AWS の選択肢
ysekiy
0
120
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
970
TypeScript 6.0で非推奨化されるオプションたち
uhyo
15
5.9k
MS Ignite 2025で発表されたFoundry IQをRecap
satodayo
3
220
Featured
See All Featured
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
The Illustrated Children's Guide to Kubernetes
chrisshort
51
51k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
119
20k
GraphQLの誤解/rethinking-graphql
sonatard
73
11k
Facilitating Awesome Meetings
lara
57
6.6k
How to Ace a Technical Interview
jacobian
280
24k
Principles of Awesome APIs and How to Build Them.
keavy
127
17k
We Have a Design System, Now What?
morganepeng
54
7.9k
Leading Effective Engineering Teams in the AI Era
addyosmani
8
1.2k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
9.8k
Navigating Team Friction
lara
191
16k
Faster Mobile Websites
deanohume
310
31k
Transcript
How we scaled Stripe from 4 to 94 employees Greg
Brockman Stripe CTO // @thegdb
You only get to pick one top priority
None
Tier 1: 4 → 8
Tier 1: 4
“Learn it on the job” is just a nice way
of saying “make it up as you go” Tier 1: 4
How Stripe got its name Tier 1: 4
Communication, communication, communication Tier 1: 4
In January 2011, we went on a “hack trip” to
Rio Tier 1: 4
Tier 1: 4
Tier 1: 4
Tier 1: 4
Friends make great candidates, if you can get the timing
right Tier 1: 4
Tier 2: 8 → 20
Tier 2: 8
First time we didn’t magically know what everyone else was
working on Tier 2: 8
The Great API Debate Tier 2: 8
Tier 2: 8
Launch was just a month away… ! (for 11 months)
Tier 2: 8
ISO8583 Night Tier 2: 8
Launch day! Tier 2: 8
Teams as buckets of work Tier 2: 8
CTF Tier 2: 8
Tier 2: 8
Tier 2: 8
Tier 3: 20 → 50
Tier 3: 20
Tier 3: 20
Build vs run Tier 3: 20
Teams as organizational units Tier 3: 20
“Org scaling” meetings Tier 3: 20
First investments in cultural documentation Tier 3: 20
We’re still learning on the job… Tier 3: 20
Tier 3: 20
Tier 3: 20
Tier 4: 50 → 94
Tier 4: 50
Teams as units of identity Tier 4: 50
Organizations have emergent behaviors. Pay attention, and tune the behaviors
that don’t make sense. Tier 4: 50
Lack of structure used to help us get things done.
! Now lack of structure was getting in the way. Tier 4: 50
If it’s not written down, it’s lost Tier 4: 50
Tier 4: 50
Tier 4: 50
Team hacktrips: Hawaii, Mexico, Montreal, North Dakota… Tier 4: 50
Tier 5: 94 → ??
Talk to lots of people who have done it Tier
5: 94
High risk, high reward system improvement projects Tier 5: 94
Will let you know in a year Tier 5: 94
Greg Brockman Stripe CTO // @thegdb