Leveling Up: Panel Discussion
summary
A candid panel on Android leadership lays out concrete practices and tradeoffs: orgs run Android teams of eight to seventy engineers; platform teams prioritize long‑term refactors while proving changes with a customer team; invest in lint, KTLint, and CI to get the green gutter culture that makes code reviews meaningful; adopt Kotlin standardization and coroutines; publish libraries like Lahi and Mavericks but expect night/weekend maintenance; run apprenticeships and mentor actively; promotions require operating at the next level for months.
AI-written summary · about
chapters (13)
- 0:00Introduction and panel setup
- 1:17Panelist introductions and career paths
- 10:29Day-to-day work of leaders
- 16:46Setting technical vision
- 25:53Balancing product and tech investments
- 35:43Mentoring engineers at different levels
- 47:41Career levels and terminal roles
- 55:30External leadership in the Android community
- 1:00:02First conference talks and tips
- 1:08:10Contributing to open source
- 1:15:09Audience Q&A on mentorship and remote culture
- 1:22:00Setting goals beyond your team
- 1:26:35Best mentor advice and closing remarks
related talks
01h 00mAndroid at Scale
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
47mRoundtable: process for your Android team
43mHow to Lead? Testimonial of a Lead Android Engineer
01h 28mApps at Scale: An Industry Discussion
51mBuilding Effective Teams of Competent, Friendly People
26mFacing the "Quality" Problem in Long-Lived Codebases
11mTips on scaling your leadership outside of your comfort zone