David Singleton of Stripe presents with Q&A from Shweta Saraf of Packet at Elevate2020
summary
Claims that preparing earlier paid off: a remote hub launched May 2019 after remote hiring since 2013, teams stay small (about 7±2 people), and remote engineers drive local product changes. Built tooling includes an internal intranet called Home, Slack automations for deploys and an incident response tooling that spins up virtual war rooms. Social tools include a Donut pairing bot and company-wide no-meeting Wednesday. Pulse surveys every few weeks show remote staff feel as — or more — connected, and twice‑yearly in‑person meetups normally occur.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:11Understanding Who Your Users Are
- 10:36Incident Management Tooling
- 17:14Lessons You Learned from Working with Your Customers
- 19:28How Do You Prioritize User Feedback and Decide Which Feedback To Focus on for Your Work
- 20:00What We'Ve Learned at Stripe
- 21:21What Strategies Do You Use To Resolve Conflicts within the Team When They Are all Remote
- 28:48Time Zones
related talks
30mBuilding Stripe’s remote hub: scaling distributed teams
39mPerks and Pitfalls of Building a Remote First Team
30mEngineer's Lifecycle Management - Remote First Environment
48mBuilding A Remote Engineering Culture
45mSquads assemble! keeping engagement high when teams go remote...
13mManaging Remote Teams
01h 10mLeading successful remote teams
38mDistributed Sys Teams