Dear Spotify Talent Acquisition team,
I want to throw my hat in for the Mobile Engineer role you opened on your careers page. I have spent most of my career shipping mobile engineering work, and I would happily bring that to your team.
I looked into Spotify before writing, and what jumped out was your push into offline-first playback and the engineering posts on rewriting the player in a shared cross-platform layer. It feels like a great time to join, and I would be glad to aim my mobile engineering experience right at that.
Reading the posting, the three things you seem to weigh most are native mobile development on iOS and Android, app performance and reliability and a polished, accessible interface. Those are what a mobile hire is measured on, and I have real results behind each.
On native mobile development on iOS and Android, I build with Swift, Kotlin and React Native. As a Mobile Engineer at DoorDash, I shipped a rebuilt checkout flow in SwiftUI and Jetpack Compose that cut cold-start time from 2.8s to 1.1s. Plus, I shipped a shared design-system module the whole mobile team now builds on.
For app performance and reliability, I use profiling, crash reporting and offline caching. In my time as a Mobile Engineer at DoorDash, I tuned the crash path so crash-free sessions climbed from 98.2% to 99.7% through better error handling and offline caching.
On a polished, accessible interface, I work with SwiftUI, Jetpack Compose and accessibility APIs. Working as a Mobile Engineer at DoorDash, I rebuilt the onboarding screens with full VoiceOver and TalkBack support and raised the app-store rating from 4.1 to 4.6. Plus, I set up the snapshot tests the mobile team runs on every build.
I would be glad to talk it all through in an interview and show you why I would be a great fit. I am eager to dive in, help the team ship great apps, and grow right along with it.
Thanks for reading, and I hope to hear back soon.
Yours sincerely,
Theo Script
theo.script@gmail.com