Mobile Engineer resume example

• Implemented an iOS booking flow with a typed API client, cancellation handling, and cached itinerary state; preserved the booking reference when the app resumed after a network interruption.
• Used performance traces and device testing to find main-thread image decoding on the itinerary screen; moved decoding off the main thread and tested slow-network, offline, and accessibility states.
• Compared crash reports with device and OS versions, reproduced a background-to-foreground navigation failure, and checked offline recovery before the staged mobile release.
• Owned an iOS state-restoration fix using API failure fixtures, resolved duplicate navigation after background recovery and completed offline regression testing.
• Built performance monitoring using device-specific traces, reduced cold-start time from 2.8 to 1.9 seconds and released the change through a staged rollout.

• Shared validated business logic across iOS and Android through a portable module. Kept the lower-effort process in place after handoff.
• Reviewed a proposed change against the existing interface contract, reproduced a reviewer’s edge case, and added the missing test or example before merging the change.
• Investigated a failure reported by a downstream team using the exact version and input they supplied. Reduced it to a reproducible test, delivered the fix with compatibility notes, and confirmed the original case passed before closing the report.

• Introduced staged releases and crash guardrails for 4 critical journeys
• Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
• Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
• Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.

Relevant coursework: Algorithms, operating systems, databases, computer networks

Crash analysis · Application lifecycle · Offline recovery · Staged releases

• Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.