Technical screening questions
Ask for one example per question and listen for specifics.
- How do you manage memory and avoid retain cycles? A good answer: ARC, weak references and capture lists.
- How do you choose between SwiftUI and UIKit? A good answer: Project needs, minimum OS and team skills.
- How do you structure an app? A good answer: MVVM or a similar pattern with clear boundaries.
- How have you handled an App Store rejection? A good answer: The guideline, the fix and resubmission.
- How do you test your code? A good answer: Unit tests, UI tests and dependency injection.
Quick screening questions
Use these when you have only a few minutes.
- SwiftUI, UIKit or both?
- Which apps did you ship?
- How do you manage app state?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds screens from designs.
- Mid: owns features and releases.
- Senior: defines architecture and performance.
Red flags
Any of these is a reason to probe further.
- No shipped app.
- Cannot discuss ARC.
- Only tutorial-level projects.
Tools you should hear mentioned
An iOS developer with real experience usually names several of these without prompting.
- Swift
- SwiftUI and UIKit
- Xcode and Instruments
- Core Data
- Combine or async/await
- TestFlight
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should an iOS developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.