Android engineer with five years shipping consumer apps in Kotlin, most recently for a grocery chain with 2.3 million monthly shoppers. Took store pickup from a 34% abandon rate to 11% by rebuilding it around an offline-first cart, and teaches Kotlin to career changers on weeknights.
Experience
Android Engineer, Puget Harvest Markets · October 2022 – present
Shopping and pickup in an app used by 2.3 million people a month.
Rebuilt store pickup around an offline-first cart in Room and WorkManager, taking abandonment from 34% to 11% in two releases.
Migrated 90 screens from XML layouts to Jetpack Compose across three quarters, cutting UI code 38% and halving the time to build a new screen.
Brought app size from 61MB to 24MB with dynamic feature modules, which lifted install completion 9% on prepaid devices.
Set up the baseline profiles and macrobenchmark run that keep p90 cold start under 1.2s; a regression now fails the build.
Android Developer, Northstack Mobile · June 2020 – September 2022
Built the barcode-scanning inventory app used by 400 warehouse staff, retiring handheld scanners that cost
20 each to replace.
Cut crashes from 2.4% to 0.3% of sessions by rewriting the fragment lifecycle handling that leaked an open camera session.
Wrote the pipeline that publishes an internal test build on every merge, removing a two-day wait for testers.
Android Developer (part-time), Fernpath Media · September 2019 – May 2020
Twenty hours a week alongside the final year of a computer science degree.
Shipped the podcast download queue, taking offline listening from 4% to 22% of sessions.
Converted the last 30 Java classes to Kotlin, ending null-pointer crashes across the next two releases.
Education
B.S. Computer Science · Western Washington University · September 2016 – May 2020
Practice: Offline-first design, Store releases, Macrobenchmark profiling, A/B experiments
Why this Android Engineer résumé works
Every bullet carries a number the product team also tracked: abandonment from 34% to 11%, app size from 61MB to 24MB, p90 cold start under 1.2s. That reads as an engineer who ships for users, not one who collects libraries.
Tools appear inside results rather than in a list: the offline-first cart is built “in Room and WorkManager”, and 90 screens move to Jetpack Compose with UI code cut 38%, so each skill is shown in use.
The Fernpath Media role is labelled “part-time” with its twenty hours a week stated, which keeps the five-year claim honest and still lets the Java-to-Kotlin conversion count.
The Rainier Code Collective teaching, with 34 of 41 graduates in paid engineering work, adds mentoring evidence that a mid-level engineer aiming at senior roles needs.
Android Engineer résumé: common questions
What should an Android developer resume include?
Kotlin and the Jetpack libraries you have shipped with (Compose, Room, WorkManager, Hilt), the size of the apps you worked on, and the performance or product numbers you moved: crash rate, cold start, app size, conversion. A Play Store or GitHub link helps if the work is public.
Should an Android resume list every library used?
No. Keep one short Android skills line with the libraries that matter for the role and let the bullets show them in use. A long list of every dependency tells a reviewer little about what you can build.
