How to Lead? Testimonial of a Lead Android Engineer
summary
Leads Android team at Aircall for about three years and runs a five‑person team with two-week sprints, one release per sprint and a QA attached, using asynchronous dailies via Slack and occasional Zoom syncs. Shares how a junior grows into deep technical responsibility, how interview and retention choices matter, and how one afternoon per sprint is reserved for mob programming and experimentation. Describes building a small prototype with ML Kit document scanner for MMS and when to be technical versus managerial.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:38Leading means to you
- 9:12Career paths and lead role
- 13:07Empowering your team
- 19:14Building a new team
- 30:26Dual role of lead engineer
- 36:53Daily responsibilities
- 41:55Final thoughts & Q&A
related talks
36mBecoming a tech lead - Lessons learned
15mFirst Steps as a Lead
51mBuilding Effective Teams of Competent, Friendly People
16mLead Dev, 3 Years of Experience, So What?
50mMaking the Leap to Tech Lead
11mTips on scaling your leadership outside of your comfort zone
12mHow to Be a Leader? | Qualities and Secrets to Inspire
29mLeading Leads - Lessons from a growing team