Cross-platform · Staff systems

Altitude

Staff mobile systems engineering

Build the systems judgement, scope and technical influence expected from staff mobile engineers.

5.0 · 1 verified Gumroad review

“No motivational b***s***, just practical insights that made a lot of things click for me.”
Nick R. · Gumroad verified purchase

556 pages · 30 chapters in 5 parts · PDF and EPUB · 3 case studies

Mike SalariMike Salari · Staff mobile engineer · 500+ technical interviews from the hiring side

Read on your phone (20 pages)

Secure checkout on Gumroad.Instant PDF and EPUB download.Lifetime updates.

Altitude cover

What is inside

Altitude in its own order: what each part teaches, so you can see whether it covers the round you have next.

  1. 01

    Part 1: Foundations (chapters 1 to 5)

    The role, the mobile client as a node in a distributed system, the design framework and domain boundaries.

  2. 02

    Part 2: Client architecture (chapters 6 to 10)

    Modules, server-driven UI, super apps, performance and governance.

  3. 03

    Part 3: Contracts and data (chapters 11 to 20)

    API and BFF design, API evolution, caching, offline-first, sync and conflict resolution, distributed systems, resilience and events.

  4. 04

    Part 4: Real time, trust and operations (chapters 21 to 26)

    Real-time delivery and push, authentication, security, observability, the delivery system, and cloud and Kubernetes.

  5. 05

    Part 5: The role and the cases (chapters 27 to 30)

    Becoming the staff mobile engineer, then three case studies: ride-hailing, global messaging and a high-assurance financial platform.

Is it the right book for you?

Who gets the most from it, and when a different book is the better use of your time. The last list is as important as the first.

Use it when

  • Your next step is staff or a mobile architecture role and interviewers keep asking about backend, auth and reliability.
  • You are preparing for a staff mobile system design interview and need to connect client, BFF, security and operations in one answer.
  • You lead designs that cross team lines and have to argue trade-offs with backend, platform and security engineers as an equal.
  • You want to understand offline sync, conflict resolution and real-time delivery as distributed systems problems.
  • Your team is debating a BFF, server-driven UI or an API versioning policy and you need the trade-offs laid out.

Skip it when

  • You are still learning mobile fundamentals; the book assumes a strong senior engineer.
  • You only want LeetCode-style practice for coding rounds.
  • You want to become a backend or DevOps engineer; the book explains those systems only as far as the app depends on them.
  • You need quick answer triage the night before an interview rather than a curriculum.

By level

Senior
The bridge a strong senior needs when the job descriptions start asking for system design, BFF and threat modelling.
Lead
Governance, team topologies and ownership chapters for leads whose designs cross team lines.
Staff
A chapter on the Staff role itself, and the systems breadth a Staff mobile system design interview expects.
Architect
The full picture from device to cloud, with case studies and ADR-style trade-offs to defend in reviews.

What a page looks like

Chapters start from concrete examples before the theory and close with key takeaways and further reading from primary engineering sources; several add exercises. Read it in order once, then keep it as a reference for design reviews and interviews.

The facts

556 pages
30 chapters in 5 parts
PDF and EPUB
3 case studies
Levels: senior, lead, staff, architect

What readers wrote

★★★★★

this book was the gap I didn't even know I had.,, and is the reason I came back and bought Mike's other books. No motivational b***s***, just practical insights that made a lot of things click for me. A f***ing great read. I recommended.
Nick R. · verified purchase on Gumroad

Questions buyers ask

Short answers about Altitude, from the book itself and the store page.

How long is it?

556 pages, 30 chapters in 5 parts and 3 case studies, in PDF and EPUB, second edition, version 2.1. The purchase also includes a 410-page Engineering Companion in 4 PDF volumes.

Who is it for?

Strong senior iOS or Android engineers who feel the ceiling and want staff-level systems judgement. It is not a beginner text.

Does it help with the Staff interview itself?

Yes, indirectly: it builds the breadth a Staff design round probes, from backend contracts to reliability and security. For question by question practice, pair it with the Mobile System Design Blueprint.

Can I read a sample?

Yes. A free sample is linked from this page: 15 pages for desktop and 20 pages for your phone. It has a week in the staff job, one section of chapter 22 and Companion worksheet 22.

How much is it?

$259, as listed on Gumroad.

How is it different from Mobile System Design Blueprint?

Altitude covers the whole system the app lives in, including backend contracts, auth, cloud and the staff role, as a curriculum. The Blueprint goes deeper on evolving, releasing and operating the mobile system itself through scenarios and 50 exercises.

Where is it sold?

On Gumroad, at the price shown there ($259 when this page was built). Gumroad handles payment, the receipt and the download.

Often read with it