Dear Hiring Manager,
After several years in an adjacent role, I am moving deliberately into mobile engineer work because the strongest part of my recent job has been native patterns, app architecture, device testing, accessibility, performance, and release follow-through. Over the last year I have built hands-on evidence with Swift, Kotlin, React Native, offline state, push notifications, crash reporting, and app store release flows, so this is a planned move rather than a loose interest.
I am not asking you to infer the connection between my old title and this role. Your team needs mobile UI judgement, performance care, platform constraints, release discipline, and API integration, and my strongest examples sit in that exact area. I would use this letter to show the connection with one specific project, the constraints I worked under, and the judgement I brought to the decision points.
A recent example is that I rebuilt an account recovery flow, reduced crash reports on older devices, and improved completion on small screens. That work required Swift, Kotlin, React Native, offline state, push notifications, crash reporting, and app store release flows, but the more important point is how I made decisions, explained tradeoffs, and followed the result through after release.
I would welcome the chance to talk through how this transition maps to your team needs. mobile teams look for evidence that product quality holds up across real devices and release cycles, so I would keep the letter concise, evidence-led, and tied to the outcomes the hiring team is likely to care about.
Yours sincerely, Alex Morgan