Growing Your Team While Remaining Efficient
summary
Peloton scales Android from 3 to 20 engineers in 18 months by running weekly "town square" meetings with an agenda doc, tracked action items, and enforced decisions through tooling and code review. A three‑week proof‑of‑concept effort finds MVVM causes state sync issues on dense screens; the fix is unidirectional data flow, delivered as a homegrown MVI-on-MVVM Kotlin framework with mandatory reviewers and pairing sessions. Tooling includes Google Java Format, code owners, Danger, PR labels and a Redux DevTools integration; result: smoother onboarding, consistent code, fewer defects.
AI-written summary · about
chapters (8)
- 0:00Introduction and team growth
- 2:35The town square process
- 9:53Peloton's town square in action
- 11:38Architecture decision example
- 15:16Iterating on previous decisions
- 25:31Benefits and smaller rollouts
- 27:16Considerations for large teams
- 28:41Conclusion and hiring
related talks
51mBuilding Effective Teams of Competent, Friendly People
01h 00mAndroid at Scale
43mThe Engineering Playbook for Growing Android Teams
41mScaling Productivity: How we have improved our dev experience
47mRoundtable: process for your Android team
01h 32mLeveling Up: Panel Discussion
39mLearnings from fast growing
39mMoving fast and staying aligned how automation powers progress