Building A Remote Engineering Culture
summary
Stack Overflow is remote-first and runs a 70%-remote engineering org that hires for “smart and gets things done,” provides headsets, standing desks and internet subsidies, and requires new hires to push production code during a 6–8 week Stack University onboarding. Communication relies on internal chat, Google Hangouts/Zoom, Google Docs and Trello, with public by default weekly standups and automated CI/devops to avoid timezone gridlock. A nomadic test — 22 cities in 7 countries in three months — succeeds: work stays productive and deployments remain stable.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:03Why Remote
- 8:23Stack Overflow
- 10:57People
- 18:29Culture
- 18:50Empowerment
- 27:05Takeaway
- 27:43Synchronous Tools
- 31:09Public By Default
- 33:56Extreme Remote
- 39:06Questions
- 39:34How did you empower them
- 40:32How stable are your teams and projects
- 41:57Legal issues
- 42:59Communication in remote meetings
- 44:37Nonremote vs remote
- 46:01Building the company culture
related talks
30mEngineer's Lifecycle Management - Remote First Environment
42mSustaining Remote – First Teams.
40mBeing a remote developer
39mPerks and Pitfalls of Building a Remote First Team
36mRemote work is here to stay: and what's next?
27mRemote Team Management
01h 06mLeading successful remote teams
29mRemote(ly) Better Than Before