JPJobPrepfull-stack interview
RoadmapsJS CompilerStar on GitHub
Career Roadmaps · iOS

Career roadmap

iOS Engineer

Swift, SwiftUI and the Apple frameworks — build apps that feel like they belong on the platform.

Time
7-10 months part-time
Entry bar
Programming experience in any language, plus access to a Mac.
Stages
5 · 25 topics
0/25 studied0%
All roadmaps

Before you start iOS

  • A Mac running current Xcode
  • Object-oriented programming fundamentals
  • Willingness to read Apple's documentation directly

Swift the language

5-6 weeks · 0/5 topics

Swift's type system and memory model are interview territory in their own right.

  1. Value semantics and optionals are the two things every iOS interview checks first.

    • Optionals, unwrapping and guard
    • Structs vs classes, value vs reference semantics
    • Protocols and protocol-oriented design
    • Generics and associated types

  2. ARC, retain cycles and capture lists — the classic iOS whiteboard question.

    • ARC and reference counting
    • Strong, weak and unowned
    • Retain cycles in closures and delegates
    • Capture lists and memory graph debugging

  3. async/await and actors replaced GCD as the expected answer. Data races are the interview angle.

    • async/await and structured concurrency
    • Tasks, task groups and cancellation
    • Actors and the main actor
    • Sendable and data race safety

  4. Swift's typed error handling plus XCTest basics before you build anything large.

    • throws, Result and error propagation
    • XCTest and async test support
    • Dependency injection for testability
    • Test doubles without a mocking framework

  5. Build settings and schemes are where iOS newcomers lose days.

    • Targets, schemes and build configurations
    • Swift Package Manager
    • Debugging with LLDB and breakpoints
    • Instruments overview

BuildA command-line tool and a single-screen app that exercise optionals, protocols and generics deliberately.

SwiftUI and UIKit

6-8 weeks · 0/5 topics

SwiftUI for new work, UIKit because the job will involve a codebase older than SwiftUI.

  1. Declarative UI plus the observation system. State management is where candidates struggle.

    • View composition and view builders
    • @State, @Binding, @Observable, @Environment
    • Layout system: stacks, frames, alignment guides
    • Navigation stack and programmatic routing

  2. Every established iOS codebase has UIKit in it, and interviews still ask about the lifecycle.

    • View controller lifecycle
    • Auto Layout and constraints in code
    • UITableView and UICollectionView with diffable data sources
    • Bridging UIKit and SwiftUI both directions

  3. MVVM is the common answer; being able to critique it is the senior answer.

    • MVC, MVVM and unidirectional patterns
    • Coordinator pattern for navigation
    • Modularisation with Swift packages
    • Keeping views free of business logic

  4. SwiftData and Core Data, plus knowing when a plain file is the right answer.

    • SwiftData models and queries
    • Core Data stack and contexts
    • Migrations and versioning
    • Keychain for secrets

  5. URLSession with async/await, plus caching and offline behaviour.

    • URLSession and async requests
    • Codable and decoding strategies
    • Caching, ETags and offline fallbacks
    • Certificate pinning basics

BuildA multi-screen app in SwiftUI with a custom UIKit view bridged in, plus navigation and forms.

Platform features

4-6 weeks · 0/5 topics

The frameworks that make an app feel native and that appear in job descriptions.

  1. Background execution rules on iOS are strict and frequently misunderstood.

    • UserNotifications and permission flow
    • Rich and actionable notifications
    • Background tasks and refresh limits
    • Silent push and its constraints

  2. WidgetKit, Live Activities and App Intents are current, visible surface area.

    • WidgetKit timelines
    • Live Activities and Dynamic Island
    • App Intents and Shortcuts
    • App groups and shared containers

  3. Apple takes it seriously, and so do interviewers at companies that ship to the App Store.

    • VoiceOver labels, traits and rotors
    • Dynamic Type and layout that scales
    • Reduce Motion and contrast settings
    • Accessibility auditing in Xcode

  4. Privacy manifests and tracking rules are now a hard gate on App Store review.

    • Permission prompts and usage descriptions
    • Privacy manifest and required reason APIs
    • App Tracking Transparency
    • Data minimisation in practice

  5. Pick the ones your target companies use rather than learning all of them.

    • AVFoundation for camera and playback
    • MapKit and CoreLocation
    • HealthKit or CoreMotion
    • Vision and CoreML on device

BuildAdd a widget, push notifications and one system integration such as share sheet or Siri shortcut.

Performance and release

4-5 weeks · 0/5 topics

Instruments literacy and a real App Store release are strong senior signals.

  1. Time Profiler, Allocations and Leaks. Being able to drive Instruments is rare and valued.

    • Time Profiler and hangs
    • Allocations and memory growth
    • Leaks and abandoned memory
    • Launch time and hitches

  2. App launch time and scroll smoothness are the two things users and reviewers notice.

    • Cold, warm and hot launch
    • Main thread discipline
    • Image decoding and caching
    • SwiftUI view identity and redraws

  3. Signing is where iOS builds break. Understanding it is a genuine differentiator.

    • Certificates, provisioning profiles, capabilities
    • TestFlight and internal distribution
    • App Store review and common rejections
    • Phased release and version strategy

  4. Xcode Cloud or Fastlane, with tests running on every pull request.

    • Xcode Cloud or GitHub Actions with macOS runners
    • Fastlane lanes for build and upload
    • Automated UI tests in CI
    • Build time optimisation

  5. MetricKit and Xcode Organizer give you production truth for free.

    • Xcode Organizer crash reports
    • MetricKit for launch and hang data
    • Symbolication and dSYM management
    • Crash-free rate targets

BuildProfile an app with Instruments, fix one real problem, and ship a build through TestFlight to the store.

Interview preparation

4-5 weeks · 0/5 topics

iOS loops are language-heavy, framework-heavy, and increasingly include a live build.

  1. ARC, value vs reference, and the view controller lifecycle come up almost every time.

    • Retain cycles: spot and fix
    • Struct vs class decision with reasons
    • SwiftUI state property wrapper choice
    • GCD vs Swift Concurrency migration

  2. Usually building a screen with networking and a list, in Xcode, while talking.

    • Fetch, decode and display in 45 minutes
    • Handling loading and error states
    • Writing testable code under time pressure
    • Xcode fluency without the internet

  3. Design an offline-capable feed or a photo uploader — mobile constraints are the point.

    • Local persistence and sync design
    • Image pipeline and caching
    • Background upload strategy
    • Modularisation for a large team

  4. Present at product companies; usually lighter than a backend loop.

    DSA Coding Questions
    • Arrays, strings and hash maps
    • Trees and recursion
    • Complexity analysis
    • Swift-specific idioms in solutions

  5. One polished app on the store, with source available, beats a folder of samples.

    • Published app with screenshots
    • Open-source repo with tests
    • Accessibility support demonstrated
    • Written architecture rationale

BuildA published app plus a written note on the architecture and the trade-offs you chose.

iOS tools on your CV

  • Swift
  • SwiftUI
  • UIKit
  • Xcode
  • Swift Concurrency
  • SwiftData
  • Instruments
  • TestFlight
  • Fastlane

What iOS employers ask to see

  • An app on the App Store with accessibility support
  • An Instruments profiling case study with before/after numbers
  • A Swift package published with tests and documentation
  • A UIKit-to-SwiftUI migration write-up

Smaller hiring pool than web, but far less competition per role and consistently higher pay bands. Fintech, health and consumer product companies hire steadily.

Content last reviewed 2026-08-31. Guidance only — no institute or paid placement is endorsed anywhere in this book.