DSA in Swift, then the rounds only iOS gets
Big-tech iOS loops still include LeetCode-style problems in Swift. What separates candidates is the iOS part: a deep-dive on memory and concurrency, a design round about the app rather than the servers, and at some companies a live build or debug in Xcode. Capture a problem, and the Code tab gives an approach and working code.
An iOS loop at a glance
Big-tech iOS loops still include LeetCode-style rounds in Swift. The rounds that separate candidates are iOS-specific: a platform deep-dive, a design round about the app rather than the servers, and at some companies a hands-on build or debug in Xcode. DoorDash, 2021 (opens in a new tab); r/iOSProgramming, 2025 (opens in a new tab); Glassdoor, 2026 (opens in a new tab); Glassdoor, 2025 (opens in a new tab)
- Uber’s first round, every level
- A 60-minute Business Phone Screen, per a prep site’s summary
- Calibrd (Uber), 2026 (opens in a new tab)
- Apple, one 2026 review
- A 30-minute hiring manager call, a 45-minute phone screen, then five virtual rounds
- Glassdoor, 2026 (opens in a new tab)
- Robinhood senior screen, one report
- About 50 minutes building in Xcode on a shared screen
- Taro (Robinhood), 2025 (opens in a new tab)
- Zomato SDE-1, one report
- Two back-to-back technical rounds of about an hour
- Medium (Zomato), 2025 (opens in a new tab)
The iOS deep-dive, topic by topic
This is the round backend and Android candidates don’t get. Here’s what iOS candidates say they were asked, grouped by topic, with where each one came up. Each line is one candidate’s account unless it says otherwise.
ARC and retain cycles
Weak versus unowned, and what ARC does and doesn’t manage.
- Zomato SDE-1
Show how a weak reference breaks a retain cycle. Weak or unowned? Do structs have ARC? Medium (Zomato), 2025 (opens in a new tab)
- Meta screen
iOS memory management, asked alongside two-sum, in one 2025 report. Taro (Meta), 2025 (opens in a new tab)
- Senior candidate
“What’s a retain cycle?”, which one senior candidate remembers as a very common phone-screen quiz. r/swift, 2025 (opens in a new tab)
- Swiggy, Apple
ARC in Swiggy’s second deep-dive round, and in the iOS-domain round of one 2026 Apple review. Glassdoor, 2026 (opens in a new tab); Medium (Swiggy), 2025 (opens in a new tab)
- Zomato SDE-1
Value and reference types
Struct versus class, and when Swift copies.
- Zomato, Oracle
Classes versus structs. Medium (Zomato), 2025 (opens in a new tab); GeeksforGeeks, 2024 (opens in a new tab)
- Swiggy SDE-2
Copy-on-write. Medium (Swiggy), 2025 (opens in a new tab)
- Zomato, Oracle
GCD and threading
Queues, barriers and keeping work off the main thread.
- Swiggy SDE-2
Write a thread-safe singleton with read and write methods using DispatchQueue: concurrent reads, serial writes, a barrier. Medium (Swiggy), 2025 (opens in a new tab)
- Meta screen
A dispatch-queue question about not blocking the main thread during a network call. r/iOSProgramming, 2025 (opens in a new tab)
- Oracle
Multithreading, on a 2024 on-site day. GeeksforGeeks, 2024 (opens in a new tab)
- Swiggy SDE-2
async/await and Swift Concurrency
The newer model, often set against GCD.
- Apple
GCD versus async/await, in the iOS-domain round of one 2026 review. Glassdoor, 2026 (opens in a new tab)
- Senior candidates
Swift 6 topics, next to the classic retain-cycle quiz. r/swift, 2025 (opens in a new tab)
- r/iOSProgramming
Concurrency questions are “all the rage”, according to candidates on r/iOSProgramming. r/iOSProgramming, 2025 (opens in a new tab)
- Apple
SwiftUI and UIKit
Lifecycles, property wrappers, and when to pick which.
- Apple
The lifecycles of UIKit and of SwiftUI, in one 2026 review. Glassdoor, 2026 (opens in a new tab)
- Swiggy SDE-2
@State, @Binding, @ObservedObject and @Environment, and when not to use SwiftUI. Medium (Swiggy), 2025 (opens in a new tab)
- Zomato, Oracle
The view controller lifecycle; the app and UI lifecycle. Medium (Zomato), 2025 (opens in a new tab); GeeksforGeeks, 2024 (opens in a new tab)
- Meta
A former interviewer retired a UIKit-internals question as SwiftUI grew. r/iOSProgramming, 2025 (opens in a new tab)
- Apple
Architecture patterns
MVVM most often, and why it fits.
- Swiggy SDE-2
MVVM, in the second deep-dive round. Medium (Swiggy), 2025 (opens in a new tab)
- Meta
A former interviewer warns against calling MVVM “industry standard” without giving reasons. r/iOSProgramming, 2025 (opens in a new tab)
- Uber, 2021
A candidate who chose VIPER for the design round was asked how it would absorb new features. LeetCode Discuss, 2021 (opens in a new tab)
- DoorDash
Its 2021 guide wants class, struct and interface-level designs that cover testing and data flow, with no third-party libraries. DoorDash, 2021 (opens in a new tab)
- Swiggy SDE-2
Networking and storage
Where the data lives on the device, and how it arrives.
- Meta
Storage, networking and real-time sync, in one 2025 candidate’s design round. Taro (Meta), 2025 (opens in a new tab)
- Apple
Local storage and memory limits, in the design round of one 2026 review. Glassdoor, 2026 (opens in a new tab)
- DoorDash, 2022
Use the provided networking code with async/await, Combine or completion handlers, per replies in a Blind thread. Blind (opens in a new tab)
- Meta
Not in any candidate report behind this page: Swift actors and The Composable Architecture (TCA). They turn up on prep-site question lists only, so weigh them below the topics above.
Coding rounds run from LeetCode to Xcode
“The coding round” means five different things across iOS loops. Find out where yours sits before you choose between practising in a shared editor and practising in Xcode. Each example is one candidate’s report unless it says otherwise.
DSA in a shared editor
LeetCode-style problems, written in Swift, graded like any coding round.
Live. Capture the problem, and the Code tab gives an approach and working code.
- Meta: reverse a linked list, in one 2025 report. In an undated Blind post, an E6 candidate estimated about 18 minutes a problem, with at least two per round. Taro (Meta), 2025 (opens in a new tab); Blind (opens in a new tab)
- Apple: an LRU cache. Uber senior: an N-ary tree boundary and the closest BST value. PhonePe: 3Sum and Add Two Numbers. Taro (Apple), 2025 (opens in a new tab); Taro (Uber), 2025 (opens in a new tab); Taro (PhonePe), 2025 (opens in a new tab)
- Flipkart’s SDE-3 problem-solving round used a shared doc, not an IDE. r/leetcode, 2025 (opens in a new tab)
Swift with an iOS slant
Short tasks that test the language and the platform rather than algorithms.
Live. The same as DSA: one screenshot for an approach and working code.
- Uber, 2021: implement and test an Iterator protocol, then make it generic. LeetCode Discuss, 2021 (opens in a new tab)
- Zomato: a 10-minute weak-reference task. Swiggy: the thread-safe singleton in the panel above. Medium (Swiggy), 2025 (opens in a new tab); Medium (Zomato), 2025 (opens in a new tab)
Build a screen live in Xcode
Start from an empty project on a shared screen and build while the interviewer prompts.
Live. Capture the brief for an approach and code to build from.
- Robinhood senior screen: about 50 minutes to build a UIKit or SwiftUI list with fixed rows and tap handling, then zip the project and send it. Taro (Robinhood), 2025 (opens in a new tab)
- Pinterest: three onsite rounds building a sample app from a verbal description, with Apple’s docs and Stack Overflow allowed. Glassdoor, 2025 (opens in a new tab)
- Uber, 2021: rebuild two weather-app screenshots in code only, with no storyboards or XIBs, in a 1-hour screen share. Zomato: two screens and an animated box in 25 minutes. LeetCode Discuss, 2021 (opens in a new tab); Medium (Zomato), 2025 (opens in a new tab)
- A senior candidate calls a paginated list of cells with optional images the long-standing typical exercise. r/swift, 2025 (opens in a new tab)
Extend or debug an existing project
You’re handed a working or broken Xcode project and asked to change it.
Live. Capture the code on screen for an approach and working code.
- DoorDash, one 2025 report: coding on an existing project, debugging it and extending it. Taro (DoorDash), 2025 (opens in a new tab)
- DoorDash’s 2021 guide: implement the design from the architecture round, then debug a flawed Xcode app. DoorDash, 2021 (opens in a new tab)
- Airbnb, 2025: a debug round and a separate “iOS project” round. Blind, 2025 (opens in a new tab)
Take-home or timed submission
Built alone against a deadline and handed in. Nobody is on the call.
Not live. Assisted Voice doesn’t help with take-homes, timed submissions or online assessments.
- DoorDash, one 2025 report: a take-home extending an Xcode project, about 5 hours. Taro (DoorDash), 2025 (opens in a new tab)
- Flipkart SDE-3: a machine-coding problem with a strict 3-hour submission window. r/leetcode, 2025 (opens in a new tab)
- Online assessments opened the Uber senior and Swiggy SDE-2 loops. Amazon’s iOS assessment ran on HackerRank, where one candidate couldn’t import a Swift Queue. Taro (Uber), 2025 (opens in a new tab); r/leetcode, 2025 (opens in a new tab); Medium (Swiggy), 2025 (opens in a new tab)
DoorDash: two accounts, four years apart
They don’t agree on whether there’s a take-home. Both are shown here, with their dates.
2021
DoorDash’s own interview guide
No take-home for iOS. The phone screen has you finish a partially built app instead. DoorDash, 2021 (opens in a new tab)
2025
One candidate’s report
A take-home extending an Xcode project, about 5 hours, then a phone screen discussing it. Taro (DoorDash), 2025 (opens in a new tab)
The guide may be out of date, or teams may differ, so ask your recruiter. Assisted Voice won’t help with the take-home itself. A follow-up call about it on Zoom, Google Meet or Microsoft Teams is a live conversation, and that’s where it helps.
- SwiftUI or UIKit?
- Ask. DoorDash let candidates choose in a 2022 interview described on Blind, and Robinhood accepted either. Uber’s 2021 build round wanted code-only UI. One Zomato candidate picked UIKit for a 25-minute task and ran out of time. LeetCode Discuss, 2021 (opens in a new tab); Taro (Robinhood), 2025 (opens in a new tab); Blind (opens in a new tab); Medium (Zomato), 2025 (opens in a new tab)
- Xcode, or something else?
- Not always Xcode. An Apple new-grad candidate was told both technical rounds would use only an online IDE. An Airbnb senior candidate worried about writing Combine and SwiftUI outside Xcode, and the screen turned out to be iOS-specific. r/iOSProgramming, 2025 (opens in a new tab); Blind, 2025 (opens in a new tab)
In mobile system design, the app is the system
One Apple review and one Meta candidate describe a design round about the client: state, local storage, networking and sync. An aggregation of candidate reports agrees, and counts opening with servers and databases as a slip. Taro (Meta), 2025 (opens in a new tab); Glassdoor, 2026 (opens in a new tab); Calibrd (mobile design), 2026 (opens in a new tab)
Prompts iOS candidates were given
- A flight booking appMeta, one 2025 report, with follow-ups on real-time data sync Taro (Meta), 2025 (opens in a new tab)
- A Tinder-like dating appUber senior, 2025, alongside a rate-limiting algorithm and its iOS side Taro (Uber), 2025 (opens in a new tab)
- Swiggy’s “Track My Order” screenSwiggy SDE-2, 2025: live status by sockets or polling, state-driven UI, Swift data models Medium (Swiggy), 2025 (opens in a new tab)
- A feature from a given design, at class and struct levelDoorDash’s 2021 guide: whiteboarded, with no third-party libraries DoorDash, 2021 (opens in a new tab)
- InstagramUber, 2021: answered with VIPER, then probed on adding features LeetCode Discuss, 2021 (opens in a new tab)
- Twists on a public list of mobile design exercisesMeta E6, one undated Blind post; the candidate prepared by reading image-loading libraries Blind (opens in a new tab)
What Uber’s guides put in scope
From a prep site’s summary of Uber’s per-track guides, where design rounds start at L4. Calibrd (Uber), 2026 (opens in a new tab)
From L4
- An app or a library
- MVVM, MVC or MVI
- Caching
- Pagination
- Debouncing
- Image loading
Added at L6 and above
- Push versus pull
- Dependency injection
Usually a follow-up, not the prompt
None of the 2025–26 iOS reports behind this page had an offline-first feed or image caching as the main prompt. An aggregation of candidate reports found offline and sync arriving as follow-ups, and pagination as a common one: “you’re on page 2 and an item on page 1 changes”. One Meta candidate’s flight-booking round probed real-time sync. Taro (Meta), 2025 (opens in a new tab); Calibrd (mobile design), 2026 (opens in a new tab)
The same as Android’s round, or not?
- Same
Uber’s guides use the same round names for iOS and Android, according to a prep site’s summary; Android’s Depth in Specialization round is in Kotlin, in Android Studio. An aggregation of candidate reports treats mobile design as one format for both. Calibrd (Uber), 2026 (opens in a new tab); Calibrd (mobile design), 2026 (opens in a new tab)
- Differs
DoorDash’s 2021 guide says its iOS loop “differs slightly”: the design from the architecture interview is then built in a coding round, and an Xcode debugging round replaces the domain-knowledge round. Its Android design round may be a library instead, such as an image loader like Glide. DoorDash, 2021 (opens in a new tab)
- Differs
The platform questions. iOS rounds ask about ARC and retain cycles, GCD and Swift Concurrency, and UIKit and SwiftUI. Glassdoor, 2026 (opens in a new tab); Medium (Swiggy), 2025 (opens in a new tab); Medium (Zomato), 2025 (opens in a new tab)
- Differs, one report
On one Oracle on-site day in 2024, Android candidates got more DSA and iOS candidates got more platform questions. GeeksforGeeks, 2024 (opens in a new tab)
For the Android side of the same round, see Android architecture interviews.
Formats reported at companies
| Company | Format reported | Build or debug round | Source |
|---|---|---|---|
| MetaiOS, 2025; E6 mobile, undated | A 45-minute initial technical interview. One 2025 candidate’s full-day loop then had two coding rounds, a conversational app design round, behavioral and team collaboration; an undated E6 report had two design rounds. Meta says its design interview almost never involves coding. Meta’s hiring FAQ says outside AI tools aren’t allowed; only the tools inside its interview environment may be used. | Build or debug round: None reported. Coding rounds were algorithms, some iOS-flavoured. | Meta Careers (opens in a new tab); Meta Careers (opens in a new tab); Taro (Meta), 2025 (opens in a new tab); Blind (opens in a new tab); Meta Careers (opens in a new tab) |
| AppleMid-level iOS, 2025–26 | Two coding rounds, one system design and behavioral with the manager. One 2026 review describes a five-round virtual onsite with separate iOS-domain and app-design interviews. Formats vary by team. | Build or debug round: One new-grad candidate was told both technical rounds would use an online IDE. | Taro (Apple), 2025 (opens in a new tab); r/leetcode (opens in a new tab); r/iOSProgramming, 2025 (opens in a new tab); Glassdoor, 2026 (opens in a new tab) |
| UberSenior iOS, 2025, and new grad, 2026: one report each | An online assessment, a live DSA round on trees and recursion, then an applied system design session with iOS questions. New-grad finals were DSA, Depth in Specialization (iOS), and Collaboration and Leadership. | Build or debug round: A 1-hour screen-shared app build, in a 2021 report. | Taro (Uber), 2025 (opens in a new tab); r/leetcode, 2026 (opens in a new tab); LeetCode Discuss, 2021 (opens in a new tab) |
| AirbnbMid-level mobile, one 2025 report | Two technical screens, then an onsite with a technical round, a debug round, an iOS project round, a project deep-dive and a core-values interview. A senior candidate’s first screen was iOS-specific, not LeetCode. | Build or debug round: A debug round and an iOS project round. | Blind, 2025 (opens in a new tab); Blind, 2025 (opens in a new tab) |
| DoorDashiOS engineer, one 2025 report | A take-home extending an Xcode project (about 5 hours), a phone screen about it, then coding on an existing project, an LC medium-hard round, iOS architecture design and behavioral. DoorDash’s 2021 guide describes no iOS take-home. | Build or debug round: Debug and extend an existing project, live. | DoorDash, 2021 (opens in a new tab); Taro (DoorDash), 2025 (opens in a new tab) |
| PinterestiOS engineer, one 2025 report | A recruiter screen and a LeetCode-style tech assessment, then five onsite rounds with no LeetCode: three app-building rounds, one iOS system design and one behavioral. | Build or debug round: Build a sample app from a verbal description, with Apple’s docs and Stack Overflow allowed. | Glassdoor, 2025 (opens in a new tab) |
| SwiggySDE-2 iOS, one 2025 report | An online assessment (DSA plus Swift and SwiftUI multiple choice), an iOS deep-dive on a thread-safe singleton, system design of an order-tracking screen, then a second deep-dive on ARC, GCD, MVVM and SwiftUI property wrappers. | Build or debug round: None separate. Code is written inside the deep-dive rounds. | Medium (Swiggy), 2025 (opens in a new tab) |
Where iOS candidates slip
Some of these rest on a single candidate’s report, and say so.
Designing the servers instead of the app
Starting with backend servers and databases instead of the app’s architecture. One 2026 Apple review says its design round cared about state, local storage and memory limits.
Glassdoor, 2026 (opens in a new tab); Calibrd (mobile design), 2026 (opens in a new tab)
Naming a pattern without a reason
A former Meta iOS interviewer warns against calling MVVM “industry standard” without saying why it fits the problem.
r/iOSProgramming, 2025 (opens in a new tab); Calibrd (mobile design), 2026 (opens in a new tab)
Treating coding as the whole bar
The same former interviewer says coding only shows a baseline, and system design decides seniority. In an undated Blind post, an E6 candidate whose API design details fell short was levelled E5.
Blind (opens in a new tab); r/iOSProgramming, 2025 (opens in a new tab)
UIKit boilerplate on a short clock
One Zomato candidate chose UIKit for a 25-minute two-screen task, didn’t finish, and wasn’t selected.
Being slow in a basic app-coding round
One candidate named this among the mistakes in a failed Turo loop, avoided it next time and got a Lyft offer. They describe that Lyft loop only as five “very domain-specific” rounds.
At big tech, usually. Meta, Apple and Uber iOS candidates all report LeetCode-style rounds in Swift. Not everywhere, though: one Pinterest candidate’s five onsite rounds had no LeetCode, and one Airbnb senior candidate’s first screen was iOS-specific instead.
Keep preparing
- iOS developer questionsCommon questions with sample answers.
- Mobile developer questionsQuestions across iOS and Android.
- Android architecture interviewsThe same design round, from the Android side.
- DSA coding roundsThe LeetCode rounds big tech still runs.
- Project deep divesTalking through an app you shipped.
- Apple interviewsQuestions and process for Apple roles.
Sources
Last reviewed . Candidate reports are paraphrased, and formats vary by team, location and year.
- Preparing for your initial interview (iOS)Meta Careers (opens in a new tab)
- Preparing for your software engineering interview at MetaMeta Careers (opens in a new tab)
- How to prepare for a technical interview (iOS architecture, coding and debugging)DoorDash, 2021 (opens in a new tab)
- Meta iOS engineer interview, Menlo Park (accepted offer)Taro (Meta), 2025 (opens in a new tab)
- Meta interview experience, E5/E6 mobile loopBlind (opens in a new tab)
- iOS interviews at “LeetCode” companies? (r/iOSProgramming)r/iOSProgramming, 2025 (opens in a new tab)
- Apple iOS engineer interview, Cupertino (accepted offer)Taro (Apple), 2025 (opens in a new tab)
- An offer from Apple, mid-level iOS (r/leetcode)r/leetcode (opens in a new tab)
- The technical component of Apple’s iOS onsite (r/iOSProgramming)r/iOSProgramming, 2025 (opens in a new tab)
- Apple iOS engineer interview questionsGlassdoor, 2026 (opens in a new tab)
- Uber senior iOS developer interview, San Francisco (no offer)Taro (Uber), 2025 (opens in a new tab)
- Uber interview: a summary of Uber’s per-track engineering guidesCalibrd (Uber), 2026 (opens in a new tab)
- Uber new grad SWE (iOS) final round (r/leetcode)r/leetcode, 2026 (opens in a new tab)
- Uber iOS engineer SE2, Canada, April 2021 (offer)LeetCode Discuss, 2021 (opens in a new tab)
- Pinterest iOS engineer interview questionsGlassdoor, 2025 (opens in a new tab)
- Robinhood senior iOS developer interview (no offer)Taro (Robinhood), 2025 (opens in a new tab)
- DoorDash iOS engineer interview, San Francisco (declined offer)Taro (DoorDash), 2025 (opens in a new tab)
- iOS onsite interview at DoorDash (replies describe a 2022 interview)Blind (opens in a new tab)
- Airbnb SWE interview process (a mid-level mobile candidate’s reply)Blind, 2025 (opens in a new tab)
- A Lyft iOS offer, after a failed Turo loop (r/leetcode)r/leetcode, 2025 (opens in a new tab)
- Interview experience for SDE-II iOS at SwiggyMedium (Swiggy), 2025 (opens in a new tab)
- Zomato SDE-1 (iOS) interview experienceMedium (Zomato), 2025 (opens in a new tab)
- Interview experience at Flipkart, SDE-3 iOS (r/leetcode)r/leetcode, 2025 (opens in a new tab)
- PhonePe iOS engineer interview, India (accepted offer)Taro (PhonePe), 2025 (opens in a new tab)
- Mobile system design interview: how Meta, Google, Uber and others test itCalibrd (mobile design), 2026 (opens in a new tab)
- Anyone interviewed for senior+ iOS roles recently? (r/swift)r/swift, 2025 (opens in a new tab)
- Oracle senior software engineer, iOS, BangaloreGeeksforGeeks, 2024 (opens in a new tab)
- Airbnb mobile interviewBlind, 2025 (opens in a new tab)
- Hiring process FAQMeta Careers (opens in a new tab)
Ready for the rounds only iOS gets
Your first 30 minutes are free. After that it’s $5 an hour, pay as you go, with no subscription.
Start free — 30 minutes, no card