Open to Senior Android / Lead Android / Mobile Engineering Leadership opportunities
Senior Android Engineer & Mobile Engineering Leader
I build reliable Android products, lead engineering teams, and improve the systems and practices that help engineers ship better software.
Android · Kotlin · Jetpack Compose · Architecture · Technical Leadership · Engineering Productivity
99.8%
Crash-free shortly after the Android rewrite shipped
40–60%
Faster release cycles via CI/CD and trunk-based development
5 engineers
Mobile engineering organization led, Android and iOS
7 months
From rewrite kickoff to full production cutover
I'm an Android engineer who grew into mobile engineering leadership, without leaving the technical roots behind.
I started with products: owning an Android app end to end, modernizing legacy Java, shipping features used at large scale. Good architecture and testing became the lens through which I judged everything I built.
At Good Doctor Technology I led the ground-up rewrite of a flagship health-tech Android app, in Kotlin, Jetpack Compose, modular Clean Architecture, and Hilt. It shipped in 7 months and reached 99.8% crash-free shortly after release. Then I built the organization around it: an Android team turned into a mobile engineering organization spanning Android and iOS, with shared practices, release processes, and AI-driven internal tooling.
Today my focus is engineering systems: architecture conventions, CI/CD, developer productivity, and AI infrastructure. The things that let teams move fast without sacrificing quality.
Designing and modernizing Android applications with Kotlin, Jetpack Compose, modular architecture, testing, and scalable engineering practices.
Modular Clean Architecture with explicit ownership boundaries, predictable data flow, and testability that keeps teams shipping independently.
Turning ambiguous technical problems into architecture, execution plans, standards, and sustainable delivery.
CI/CD, developer tooling, automation, release processes, and internal tooling that make engineers faster.
I create processes, visibility, expectations, and feedback loops so engineers can operate independently. Show & Tell is the example: a lightweight ritual that creates real awareness without turning leadership into status-checking.
Engineers propose solutions before they receive guidance. Delegating technical ownership builds decisions inside the team instead of handing them down.
TDD, Compose UI testing, architecture conventions, CI/CD pipelines, technical-debt ownership, and release processes designed so quality doesn't depend on heroics.
Psychological safety, recognition, and mentoring: environments where junior engineers ask questions freely and senior engineers keep growing.
Android Engineer
Built products end to end and developed deep Android expertise, from health-tech apps to streaming platforms at large scale.
Senior Android Engineer
Owned architecture, complex features, quality, and technical direction, leading a 100% Kotlin + Compose greenfield rewrite.
Android Lead
Led Android engineers and contractors through modular Clean Architecture, establishing testing, release, and review practices.
Mobile Engineering Leader
Expanded scope across Android and iOS: people leadership, delivery, engineering culture, and organizational systems.
Senior Android Engineer → Android Lead → Lead Mobile Engineer · July 2023 – Present · Jakarta
I joined when the Android product depended heavily on an external development vendor. I led the complete ground-up rewrite in Kotlin and Jetpack Compose: modular Clean Architecture, MVVM, Hilt, TDD, full unit test coverage, with a cross-functional team of 7 engineers across in-house, contractors, and vendors.
7 months
rewrite kickoff to cutover
99.8%
crash-free after release
100%
unit test coverage at delivery
Then I built the engineering system around the product, not just the application: architecture conventions, testing practices, a release-train process with staged rollouts (10% → 100%, immediate halt on regressions), technical-debt ownership, engineering rituals, mentoring, and collaboration across the mobile organization.
40–60%
reduction in CI/CD queue times
10% → 100%
staged rollout with halt-on-regression
Beyond the Android app, I led the mobile organization: 5 engineers across Android and iOS. Shared retrospectives, Show & Tell, and joint learning across platforms. I drove the Huawei AppGallery integration, bringing the app to 1.5M potential new users, and created Skola, an internal marketplace for reusable AI Skills and MCP servers.
5 engineers
mobile organization, Android + iOS
1.5M users
reach via AppGallery integration
Owned core components of Indonesia's #1 OTT streaming Android app at tens of millions of monthly active users. Designed and built a shared ExoPlayer-based core player library used by both mobile and Android TV apps. Stabilized and refactored the Android TV app using the Leanback UI toolkit. Daily TDD, pair programming, and extreme programming practices.
Took full ownership of the Lawyer Connect Android app within months of joining. Migrated legacy Java to Kotlin + MVVM + RxJava. Shipped VoIP calling (Twilio) and in-app chat (SendBird). Later founded and led the Android Chapter: hired and onboarded engineers, led greenfield development of Client Connect, and rewrote the flagship app with Flutter + Riverpod. Built the mobile code review process the mobile org still uses.
I build tools because I encounter engineering problems and want to solve them, not because a job description says so.
Publishing to Google Play is slow, click-heavy, and easy to get wrong. MCP server covering the publishing workflow: artifacts, release tracks, staged rollouts, testing, and Play Console operations.
AppGallery operations have no good automation story. MCP server for app metadata, AAB uploads, phased and scheduled releases, testing, and reporting.
CI/CD state lives in a dashboard engineers have to keep checking. MCP server exposing Codemagic builds, artifacts, logs, environment variables, and caches to AI agents.
The official Sentry MCP doesn't cover everything engineers need. Companion MCP server with extra Sentry tooling for triage workflows.
AI agents can't naturally act where teams actually communicate. MCP server that reads channels and threads and sends bot messages inside AI workflows.
I'm interested in engineering roles where I can stay close to technology while expanding my impact through technical leadership and team leadership.
Roles where that fits:
Currently: building MCP servers for Google Play, Huawei AppGallery, Codemagic, and Sentry, turning developer infrastructure into things AI agents can operate directly.