Work Anywhere: Managing Remote Engineering Teams at Airbnb
summary
Airbnb shifts to a remote-first live and work anywhere policy and runs a 13-engineer Viaduct team supporting its GraphQL edge. Concrete practices include RFCs numbered in a public folder with draft vs published states that create searchable design trails and help recruiting, a 90-minute weekly tech brainstorm with a prioritized agenda instead of many ad hoc meetings, bi-weekly status updates, digital sticky-board retrospectives for anonymous, parallel feedback, calendar-blocked core overlap hours and explicit DM/notification expectations.
AI-written summary · about
chapters (9)
- 0:00Intro
- 4:17Agenda
- 5:04Remote manager responsibilities
- 8:48Team norms
- 32:33Intentional culture
- 42:24What's next?
- 44:03Takeaways
- 45:22Outro
- 45:50Q&A
related talks
30mEngineer's Lifecycle Management - Remote First Environment
48mBuilding A Remote Engineering Culture
27mRemote Team Management
50mScaling Teams Through Remote Work
01h 06mLeading successful remote teams
39mPerks and Pitfalls of Building a Remote First Team
13mManaging Remote Teams
30mBuilding Stripe’s remote hub: scaling distributed teams