2026 update
A few things have changed in 2026. AI is now allowed in coding rounds at Canva and Meta, detection has improved at companies that still ban it, comp has split at staff+, and the post-onsite wait got longer. Read what changed in 2026 →
What you'll be expected to do
The bar they grade against- Own a feature or screen end-to-end: spec, implementation, A/B test, staged rollout
- Write production Swift: Swift Concurrency (async/await, actors), Combine, UIKit and/or SwiftUI
- Partner with backend on API contracts; handle offline and degraded-network paths explicitly
- Participate in on-call for the app; debug crashes and ANRs in production
- Optimise for app size, battery, and cold-start time; write the relevant Instruments reports
- Code-review junior engineers; raise the team's Swift conventions over time
The loop, round by round
5 rounds · 3–5 weeksMost companies follow a similar shape for iOS Engineer interviews. Total calendar time is 3–5 weeks from recruiter screen to offer.
Background, role calibration, motivation, comp expectations
Live coding a small problem, usually a UI + data manipulation task (e.g. parse JSON, render a list, handle a search filter). Algorithm bar lighter than backend, iOS-pattern bar heavier
Design a feature with iOS-specific constraints: offline-first sync, image-loading cache, push-notification handling, background fetch. Probing on lifecycle, threading, network resilience
Walk through something you've shipped, design choices, edge cases, performance work, App Store review issues. Common at the senior-leaning L4 bar
Past projects, cross-functional collaboration with backend / design / PM, shipping war stories
Sample questions you should be ready for
9 of the ones that decide itRepresentative of what companies ask at this level. Every question here is drillable out loud, which is the fastest way to find out whether your answer holds up under follow-ups. Calibrd adds voice practice with coaching on every answer, and a full voice mock interview: a live round with an AI interviewer who has read the role and your CV, then an honest debrief.
- 01“Implement a class that downloads images from a list of URLs concurrently, caches them by URL, and never has more than 4 downloads in flight at once. Use Swift Concurrency.”Practise this →
- 02“An iOS app is growing memory steadily during a scroll session, not crashing, just climbing. Walk me through how you'd identify whether it's a leak, a retain cycle, or cache growth. Which Instruments tools do you reach for, in what order?”Practise this →
- 03“Given a UIScrollView that's dropping frames when scrolling, walk through how you'd profile the issue. What tools, what would you look at first?”Practise this →
- 04“Design an offline-first to-do app that syncs to a backend when the device comes online. Cover conflict resolution and what happens during a sync mid-flight.”Practise this →
- 05“Design an image-loading library like SDWebImage or Kingfisher. Cover memory cache vs disk, cancellation, and how you'd handle a 10MB image arriving on a list cell.”Practise this →
- 06“Design a push-notification handler that needs to update local data and surface a custom UI before the user opens the app. Cover background-mode behaviour and the silent-push path.”Practise this →
- 07“Tell me about a feature you shipped that broke in production. How did you find out, and what did you change in your team's practices?”Practise this →
- 08“Walk me through a time you pushed back on a designer or PM on a feature you thought wouldn't work on iOS.”Practise this →
- 09“Describe an app-size or performance optimisation you made. What was the metric, and what did you measure to prove it worked?”Practise this →
These are the general ones. Paste a real posting and Calibrd predicts the questions that company asks for that exact role, then interviews you on them.
Predict my questions →Compensation benchmark
US majors · USD · medianMedian compensation for iOS Engineer at major US tech companies, headline numbers in USD. Pay in markets like London, Berlin and Singapore tends to be meaningfully lower in base terms, and equity ratios vary by company stage.
FAANG L4 iOS total comp at 50th percentile is $260–340k. Tracks the L4 SWE band closely at Meta / Google / Stripe. Apple iOS pays slightly above this band at the equivalent ICT3 level, and the loop is structurally different.
How to prep
5 tactical tipsLead behavioural answers with the STAR method: Situation, Task, Action, Result. The tips below build on that structure for this specific role.
- 01Drill Swift cold, closures, async/await, actors, value vs reference semantics, generics. The coding round assumes fluency that take-home practice can't fake
- 02Know one architecture pattern deeply (MVVM, MVC, or Composable Architecture) and be able to defend it without falling back to "that's what the team uses"
- 03Be ready to walk through a feature you've shipped: lifecycle decisions, the edge case that bit you, what you'd do differently. The deep-dive round expects specifics
- 04Watch the WWDC sessions from the last 2 years for the platform features the company uses (Observation, Swift Macros, MainActor isolation, SwiftUI Observable)
- 05Practise 2–3 iOS system designs cold: offline-first sync, image cache, push notification handler. Pattern-match from there
Where iOS Engineer candidates fail
Spot it in a mock firstA few common mistakes that get iOS Engineer candidates rejected even when they are otherwise strong. Worth catching in a mock interview before they show up in a real one.
Solving the coding problem optimally but ignoring the iOS-specific parts, no main-thread awareness, no value-vs-reference reasoning, no mention of where retain cycles could form.
Why it fails
At L4 the bar isn't whether you can code. It's whether you write Swift like someone who's shipped to production. A correct solution that doesn't mention weak-self in a closure, or reaches for a class where a struct fits, signals "generic engineer who learned Swift recently." The interviewer is waiting for the iOS layer commentary, not the algorithm.
Fix
After every solution, narrate the iOS layer out loud: where this would dispatch, whether the type should be a struct or class, where memory leaks could form (retain cycles in closures or Combine pipelines), and where you'd reach for an actor vs a serial queue.
Designing an iOS feature as if it were a web feature, happy path, perfect connectivity, server always reachable.
Why it fails
Mobile system design has different constraints than backend. Offline, flaky network, app lifecycle (foreground / background / terminated), background app refresh, push wake-ups, these aren't optional. Designs that ignore them read as "thinks like a backend engineer who happens to write Swift." The interviewer is waiting for the clarifying question about offline behaviour, not for you to plough ahead with a server-first design.
Fix
Within the first five minutes of any iOS system design, ask the offline questions: what happens with no connectivity, what's the sync strategy, what's the conflict-resolution rule, what background work runs and when. Then build the design around the answers.
Describing past iOS work in terms of features built, no DAU, no crash rate, no App Store rollout story, no A/B numbers.
Why it fails
iOS interviewers calibrate against shipping experience. "I built the new onboarding screen" tells them nothing. "I built the onboarding flow used by 800k DAU, cut funnel drop-off from 22% to 14% via the third-screen redesign, and the v2.4.1 staged rollout flagged a crash on iOS 16 that we patched in two days" lets them peg you. The shipping numbers separate L4 candidates from L3 candidates more than the technical depth does.
Fix
For your top 3–4 stories, attach three numbers each: scale (DAU or downloads), impact (the metric that moved), and an operational detail (crash rate, rollout, App Store review feedback). Rough numbers beat no numbers.
Recommended resources
No affiliate linksBooks, courses, and tools that come up most often in iOS Engineer prep.
- 01WWDC video archive (Apple Developer) →
Canonical reference for iOS internals. Watch Concurrency, Performance, and SwiftUI sessions from the last 2 WWDCs, interview rounds often probe recent platform updates.
- 02Swift Programming Language (free, swift.org) →
Official Swift reference. Skim the Concurrency, Memory Safety, and Generics chapters before any Swift-heavy loop.
- 03Hacking with Swift (Paul Hudson) →
The most-cited practitioner tutorials on iOS. Useful for the patterns and sample apps that come up in coding rounds.
- 04iOS Dev Weekly newsletter →
Curated weekly newsletter. Skim recent issues before interviews to pattern-match current iOS engineering norms and pull-requests in flight.
- 05App Architecture (objc.io) →
Compact reference for iOS architecture patterns (MVC, MVVM, ViewModels with Coordinators). Useful for defending an architecture choice in the system design round.
- 06App Store Connect: phased release documentation →
The release mechanics the rollout stories in this guide assume: phased release percentages, pausing, and what you can and cannot halt.
Frequently asked questions
Is this guide useful if I'm a backend / web engineer moving into iOS?
Yes, the L4 / IC3 bar described here applies whether you came from web, backend, or directly through iOS. SWE-to-iOS transitions usually have the algorithmic coding base but need to drill the iOS-specific patterns (lifecycle, threading, value semantics, retain cycles). The biggest delta is the coding round expecting fluent Swift idioms, not just correct code. Prep that gap first.
How long should I prep before my iOS Engineer onsite?
The process takes 3–5 weeks. Add 4–6 weeks of prep if you're rusty on current Swift / SwiftUI; 2–3 weeks if you're shipping iOS daily. Watching the last 2 WWDCs for the company's platform features is the highest-leverage single move at this level.
What's the most common mistake candidates make at the iOS Engineer bar?
Treating iOS coding rounds as algorithm tests. The interviewer is grading whether you write Swift like a production iOS engineer, value semantics, weak-self, MainActor, the lifecycle hooks. Algorithmic correctness without that layer reads as a backend engineer playing iOS.
What if my interview process is different from what's listed?
Most variation is at the edges. Major tech companies (FAANG, scale-ups, mid-size SaaS) follow processes within 1–2 rounds of what's described. Smaller startups often run fewer rounds (3–4) but the bar at each round is similar; less-tech-mature companies sometimes skip system design or behavioural rounds entirely. Read the JD and ask the recruiter at the screen, they'll tell you what's coming.
How does this guide compare to running a free scan?
This guide covers the general bar at L4 / IC3. The free scan reads your specific job description and returns predicted questions for that exact role + company, a calibrated comp benchmark, and (with your CV) experience-gap analysis and an ATS resume check. PDF emailed.
Walk in ready
Walk into your iOS Engineer interview ready.
Paste your actual job and Calibrd shows you exactly what that company asks, where your CV is thin, and what it should pay. Then rehearse the round out loud with honest feedback until you're confident. Any tech role. Free to start.
Free to start · No credit card · Your CV stays on your device