Building Stripe’s remote hub: scaling distributed teams
summary
Stripe launches a remote hub in January 2019 and treats remote work as a coequal engineering hub, aiming to expand teams hiring remotely, improve remote experience, and recruit more engineers. Concrete moves: a three‑month Bay Area pilot, codified norms like an all-remote weekly meeting and a silent meeting format, simplified hiring rules for senior roles, and tooling emphasis on GitHub, JIRA and Google Docs. Outcome: by year end nearly 200 remote hires—about one‑fifth of engineering—plus fully remote internships in summer 2020.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:00Building Stripe's Remote Hub: Scaling Distributed Teams
- 3:54The best practices for operating remotely at scale are the best practices for operating at scale, period.
- 7:52Working at home during a pandemic is different from working remotely
- 10:44Expand the breadth of teams hiring remote engineers
- 14:48Hypothesis: A remote landing team can help cement your team's culture
- 14:58Data: 3-month pilot of San Francisco engineers working from home
- 16:03Hypothesis w2: Being distributed remotely is not that different from being distributed across offices in different cities
- 19:01Result: The best engineering workflows create discoverable records
- 19:45Recruit and hire more remote engineers
- 20:17Data: We codified and simplified requirements for working remotely
related talks
31mDavid Singleton of Stripe presents with Q&A from Shweta Saraf of Packet at Elevate2020
48mBuilding A Remote Engineering Culture
42mSustaining Remote – First Teams.
50mScaling Teams Through Remote Work
27mRemote Team Management
36mRemote work is here to stay: and what's next?
52mWork Anywhere: Managing Remote Engineering Teams at Airbnb
40mBeing a remote developer