iOS Developer CV in 2026: SwiftUI is the Floor

If you got cut in the last layoff wave and are now staring at your iOS Developer CV from 2022, sit down. The bar moved. Not by a little. "Swift, UIKit, MVVM, REST" used to be enough to clear a screening round. In 2026 that reads like a CV from a different era, and recruiters scroll past it inside fifteen seconds.

Below is what actually works in iOS hiring this year, with the bullet shapes hiring managers expect, the App Store metrics that move offers, and the awkward Obj-C question that still comes up.

SwiftUI plus UIKit is the floor, not the bonus

Two years ago you could write "strong UIKit, learning SwiftUI" and be taken seriously. Not anymore. Most product codebases shipped in the last 18 months are SwiftUI-first with UIKit hosting controllers wrapping the legacy 30% of screens. A recruiter reading your CV needs to see both, named separately, with the migration story between them.

What that looks like in a bullet: "Migrated 30+ screens from Storyboards to SwiftUI with zero user-facing downtime, kept five UIKit hosting controllers for camera and Apple Pay flows where SwiftUI was not stable enough." That single line tells the reader you know both, you know the limits, and you shipped the migration in production.

Swift Concurrency: the actual 2026 shift

If there is one technical thing that splits mid from senior on CVs this year, it is async/await and actors. Combine is still in codebases, but new code is being written with structured concurrency, and Swift 6 strict concurrency checking is now a real conversation on hiring loops. If your CV says "Combine, RxSwift" with no mention of async/await, Tasks, or actor isolation, you read as someone who stopped learning two years ago.

• Name the concurrency primitives you actually used: async/await, Task, TaskGroup, actors
• If you ported Combine pipelines to async sequences, that is a senior-tier bullet on its own
• Mention Sendable conformance work or strict concurrency migration if you touched it
• Skip the word "reactive" alone, in 2026 it tells the reader nothing

App Store metrics that move offers

Hiring managers for iOS roles look at one thing first: did you ship to humans, and did the numbers move. Generic engineering metrics ("reduced bundle size", "improved velocity") read as filler. App Store specific numbers read as proof.

• Crash-free users rate (App Store Connect or Crashlytics), with before and after numbers
• App Store rating maintained or improved, and over how many reviews
• Cold-start time in seconds, measured with MetricKit or Instruments, not by feel
• Downloads or MAU growth tied to a feature you shipped (not the whole app)
• Revenue numbers from StoreKit / Apple Pay / subscription flows if you owned that surface

Real shape: "Lifted crash-free users from 97.2% to 99.6% in one quarter by rewriting the camera pipeline and wiring structured Crashlytics logging." Numbers, mechanism, timeframe. That bullet alone usually gets a callback.

Public App Store apps vs enterprise iOS

Two iOS career tracks read very differently on a CV, and treating them the same is one of the most common mistakes. If your apps were live in App Store, link them. Direct link, App Store icon visible, the recruiter taps it and sees real reviews. That single link does more than a paragraph of self-praise.

If your work was enterprise (in-house distribution, MDM, custom B2B, NDA fintech), you do not get the App Store link, and that is fine. The format that works: name the product category, the audience size, your specific contribution, plus one technical detail that proves it was non-trivial. "Built the offline sync layer for a 12,000-seat field service app on private MDM distribution, handled conflict resolution across three devices per user." Recruiters see this format constantly and treat it as normal.

The Obj-C question, honestly

It still comes up. Not every day, but enough that ignoring it is a small risk. The honest split: if you are applying to startups and product companies founded after 2019, Obj-C is basically irrelevant and writing "Objective-C" on the CV without context can even make you look older than you are. If you are applying to banks, telcos, big enterprise, or any 10+ year old codebase, list it, calibrated.

Calibrated looks like: "Objective-C, read and debug, occasional bridging". That tells the reviewer you can survive a 2014 file when the linter screams, without claiming you want to write new Obj-C for the next two years.

Testing and CI: Xcode Cloud, Fastlane, the real answer

Senior iOS in 2026 is expected to have shipped a real CI/CD setup, not just "used Jenkins once". Two patterns dominate hiring loops: Xcode Cloud for teams that bought into the Apple ecosystem fully, and Fastlane plus GitHub Actions or Bitrise for everyone else. Either is fine to list. What is not fine is silence on the topic.

• Name the trigger and the artifact: "PR triggers unit tests on Xcode Cloud, main pushes a TestFlight build"
• Give XCTest coverage as a number for the critical module, not the whole app
• Mention snapshot tests (SnapshotTesting library) if you ran them, this is a senior signal
• If you cut release cycle time, write the before and after in hours, not adjectives

How the senior bar moved post-2023

Before the layoff wave, senior iOS often meant "5+ years, ships features, mentors juniors". Today the same title needs more. Hiring managers I talk to are checking for three additional signals: ownership of a critical surface end-to-end (payments, auth, sync, camera, push), at least one cross-functional decision that was visibly yours (chose StoreKit 2 over a third-party SDK and defended that in writing), and the ability to handle on-call or incident response on a live App Store app.

If your CV does not show at least two of those three, the title "Senior iOS" reads as inherited, not earned. Reorder your bullets so the ownership and the decisions sit at the top, not at the bottom under "other contributions".

Common iOS CV mistakes I keep seeing

• Listing "iOS development" as a skill. That is the job title, not a skill.
• Naming Swift version without context. "Swift 5" alone in 2026 looks like a copy-paste from 2020.
• App Store apps with no link. If it was public, link it. If you cannot, that is a separate sentence.
• Bullet shape "developed iOS application using Swift and Xcode". Tells the reader nothing, and uses 12 words for it.
• A mile-long list of pods. Three you owned beat thirty you imported.

Salary ranges for iOS in 2026

Useful as a sanity check before you write your expected number. These are 2026 iOS-specific bands, not the whole mobile market.

• Ukraine: junior $700-1,500, mid $2,000-3,800, senior $4,000-7,000 per month
• EU: junior 2,500-3,800, mid 4,200-6,500, senior 6,800-10,000 EUR per month
• USA: junior $85-115k, mid $120-170k, senior $175-260k per year, base only

Two notes. Western EU sits at the top of the EU band; Eastern EU is closer to Ukrainian top range. US numbers are base only, equity at product companies often adds 20-40% on senior. If your number lands in the bottom of your band but your CV has one strong end-to-end App Store bullet, you are probably under-asking by at least 15%.