The Inside Job
Mobile Engineer - IOS
Builds and maintains the customer-facing iOS app for Gymshark, writing production Swift (mostly SwiftUI, with an ongoing UIKit migration) using Clean Architecture and MVVM, with unit tests, observability and App Store delivery. Hybrid role requiring at least 3 days a week in Solihull, UK.
- Compensation
- Not disclosed
- Location
- Solihull
- Work setup
- Hybrid
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- Not specified
- Category
- Mobile
- Posted
Skills
Must have
- Several years writing Swift in a production app used by customers
- SwiftUI work you have written is live in the App Store
- Experience working in an established codebase alongside other engineers
- You write unit tests for your own production code as a matter of routine
- You have been responsible for resolving a production issue
Nice to have
- Worked on consumer or e-commerce apps at scale
- Experience of a UIKit to SwiftUI migration
- Experience of feature flagging and experimentation in production
- Kotlin, or another second platform, sufficient to collaborate with the Android team
Full description
**OVERVIEW:
This role exists to build and maintain the iOS app that a large share of Gymshark customers shop through, at a standard that holds under peak load. You will turn refined product work into features that are shipped, tested and observable, and improves the quality of the code you touch.
WHAT YOU'LL BE DOING:CRAFT
- Writes production Swift confidently. Most new work is SwiftUI; the app still contains UIKit that is being migrated, so both are relevant.
- Works effectively in a modular codebase. Understands why a type belongs in one module rather than another, and adds features without crossing module boundaries.
- Applies Clean Architecture and MVVM as standard, can explain the separation of concerns, and identifies where a pull request breaks it.
- Writes unit tests as part of the work rather than afterwards, and is comfortable building test doubles. Some of the team work test-first, and we want to increase that.
- Understands Swift concurrency sufficiently to avoid data races, and raises it when a problem exceeds their experience.
- Diagnoses production issues from crash reporting and analytics, and identifies the root cause independently.
- Treats performance, accessibility and app size as part of completing a piece of work.
- Understands the path their code takes after merge: CI, review, distribution and App Store submission, and the common failure points at each stage.
- Uses a branching strategy consistently and writes pull requests that are straightforward to review.
- Raises design specifications that conflict with the Human Interface Guidelines rather than implementing them unchanged.
- Considers security and dependency risk routinely, and can assess whether a third-party SDK should be added
DELIVERY
- Contributes actively to Agile ceremonies, and raises when one is no longer useful.
- Helps Product Owners refine stories into buildable work, and raises when a story is not ready.
- Breaks work into increments that each deliver value, rather than a sequence that only delivers at the end.
- Demonstrates their own work to non-technical stakeholders and explains its value in plain language.
- Raises problems early, while they are still inexpensive to fix.
CULTURE
- Uses their 10% time and shares what comes out of it.
- Cross-skills beyond iOS sufficiently to work with adjacent teams.
- Shares what they learn through an appropriate channel.