MySTC: Leading a Five-Person Android Team
I led five senior Android engineers on MySTC, working in Kotlin and Java across account, ordering, support, and multilingual flows.
[delivery dossier] 2 sections
Five engineers, one busy Android app
I led a team of five senior Android engineers on MySTC. This was an established telecom app with account management, ordering, and support journeys already in production. We extended it while customers were using it.
The Android code mixed Kotlin and Java and followed MVVM patterns. Firebase integrations were part of the stack, and some flows used SQLite-backed local data. A feature could touch an older Java class, a newer Kotlin module, a remote response, cached state, and translated layouts in the same change.
What the lead role looked like day to day
A lot of my time went into splitting work so five experienced engineers could move in parallel without inventing five versions of the same solution. I reviewed implementation boundaries, unblocked people when a dependency crossed teams, and stayed hands-on with performance and stability work.
Multilingual behavior and unreliable connections were regular acceptance concerns. I checked that a change still made sense when text expanded or changed direction, and that the screen did something understandable when fresh data wasn't available. Those checks were part of the feature, not cleanup after it.
The role combined technical leadership with hands-on delivery. I kept five experienced engineers aligned on the same architecture and release path while continuing to ship Android work alongside them.