Skip to content
All books
Stage 3 · Interview

The senior signal

Senior Android interviews in 28 chapters, with a 510-question bank and 100 worked answers for the 2026 platform wave.

5.0 · 2 reviews on Gumroad

A senior Android interview system for Engineers who already know Android.

The Senior Signal is built around the difference interviewers actually hear: not whether you can name the API, but whether you can explain the ownership model, the lifecycle boundary, the failure mode, the measurement plan and the trade-off behind the answer.

The five-part structure moves from Foundations, through the Interface, the Machine and the Adversary, into Systems, the World and the Room. It covers Android contracts, Kotlin, Coroutines and Flow, Compose, Views, accessibility, offline-first architecture, networking, battery, performance, memory, security, privacy, modularization, testing, shipping, debugging, localization, system design, migrations, the human interview and the 2026 frontier.

This is not a list of definitions. It is a blueprint for reasoning that stays clear when the interviewer asks what happens next, what fails, how you measure it and what trade-off you chose.

What you get

  • 28 deep Android interview chapters in five parts
  • 510 senior-level questions in Appendix A, grouped by area
  • 100 worked answers for the 2026 platform wave, with common mistakes, senior signal and source links
  • 27 case studies written at interview tempo
  • A one-page rapid revision per chapter and 14 diagrams

A page from the book

Copied as printed, so you can judge the format before you buy.

Appendix C, page 379

You bump targetSdk to 36 and your app suddenly draws behind the status bar with content clipped under the camera cutout. What changed in Android 16, and what is the correct edge-to- edge migration for a Compose app: insets, scaffolds, and the IME?

Answer

Android 16 removes the edge-to-edge opt-out for apps targeting SDK 36: the window always draws behind the system bars, so any screen that assumed an inset content rectangle now slides under the status bar and camera cutout. The migration is insets discipline, not padding hacks: call `enableEdgeToEdge()`, let `Scaffold` consume `contentWindowInsets`, apply `windowInsetsPadding(WindowInsets.safeDrawing)` at the boundary that owns each screen, and handle `WindowInsets.ime` on input screens so the keyboard resizes content instead of covering it. Then audit every screen against cutouts and landscape, because insets are now a correctness surface.

Common mistakes and senior signal

Hardcoding a status-bar height as top padding: it is wrong across devices, breaks in landscape cutouts, and does nothing for the gesture area or IME. Senior signal: applying insets once at the screen boundary rather than sprinkling them per widget, testing with keyboard open near every edge, and naming which surfaces may draw behind bars versus which content must stay clear.

Want more pages?

Before and after

Android lifecycle

Before

Use ViewModel because it survives rotation.

After

I would separate configuration changes from process death.

ViewModel helps with in-memory UI state across configuration changes, but durable state still needs saved state, persistence or a reload strategy.

Coroutines and cancellation

Before

Launch it in a coroutine scope.

After

I would first decide who owns the work and how cancellation should propagate.

Then I would choose the scope, dispatcher and recovery path based on lifetime, user intent and failure mode.

What is inside

  1. 1The interview you are actually inp. 10
  2. 2Platform citizenship · contracts that narrow every yearp. 17
  3. 3The system owns your processp. 28
  4. 4Kotlin · what the compiler knows, and what it generatesp. 40
  5. 5Coroutines and Flow · who owns this work?p. 61
  6. 6Compose · the framework that re-runs your codep. 88
  7. 7Views · the stack where nothing is automaticp. 109
  8. 8Accessibility · the parallel interfacep. 122
  9. 9Jetpack · libraries as encoded scar tissuep. 133
  10. 10Offline-first · the database is the truth, the network is a rumorp. 145
  11. 11Networking · reliability on a transport that promises nothingp. 158
  12. 12Battery · working inside a shrinking budgetp. 171
  13. 13Performance · measured, or imaginedp. 182
  14. 14Memory · the heap never liesp. 192
  15. 15Security · the client is in enemy handsp. 203
  16. 16Privacy · the data you never collectp. 213
  17. 17Architecture · decisions that outlive their authorsp. 223
  18. 18Modularization · the org chart, compiledp. 233
  19. 19Dependency injection · who knows what, and for how longp. 242
  20. 20Testing · suites that earn their keepp. 252
  21. 21The build · engineered, not accumulatedp. 262
  22. 22Shipping · the release is the unit of engineeringp. 271
  23. 23Debugging · truth from partial evidencep. 280
  24. 24The world · localized, not translatedp. 289
  25. 25System design · composing everything at the whiteboardp. 299
  26. 26Migrations · the long campaignp. 310
  27. 27The human interview · evidence about yourselfp. 319
  28. 28The frontier · 2026's newest questionsp. 327
  29. Appendix A. The question bankp. 336
  30. Appendix C. The 2026 wave, worked answersp. 378

What readers say

  • “Wow. Just wow. Mike recommended this book during my CV audit, and I grabbed it as part of the deal. Best decision. I've been doing Android for 6 years, and this book made me feel like I was discovering Android again. So many interesting questions and topics that made me stop and think. Highly recommended.”

    Emilio D.
    Gumroad verified purchase

  • “As mobile developer, I can honestly say this is the best Android book I've ever had!!! The content is excellent, the design is beautiful, and it's been incredibly useful. Huge thanks to Mike for putting together such an awesome resource!!”

    Ivan G.
    Gumroad verified purchase

Reader reviews from Gumroad, word for word.

Who this is for

This is for you ifYour Android knowledge is correct, but the follow-up does not yet read as senior judgment.

  • Senior Android engineers preparing for serious interviews
  • Mid-level Android engineers trying to move into senior roles
  • Staff, lead and architect candidates who need stronger system design answers
  • Mobile engineers switching into Android-heavy roles
  • Interviewers who want sharper Android follow-up questions
  • Engineers tired of definition-based prep

Not for

  • Complete beginners learning Android from zero
  • Developers who only want syntax exercises
  • Candidates looking for memorized one-line answers
  • Engineers who are not preparing for interviews, leveling or senior technical conversations
The library pathWhere this fits
  1. 01Get foundThe Silent Rejection
  2. 02Build the record and negotiateThe iOS Engineer playbook · Leverage
  3. 03InterviewThe iOS interview blueprint · The senior signal · Top 300 React Native interview questions · 500 Flutter interview questions · The senior SDET interview handbookYou are here
  4. 04Answer practice and live roundsThe 24-hour iOS interview answer book · The 24-hour Android interview answer book · Share your screen
  5. 05Architecture and qualitySwiftUI under load · Mobile System Design blueprint · Security is a feature · The second pass
  6. 06Staff systems and ownershipAltitude · Ticket taker, outcome owner
  7. 07Build with AIBuild with your brain on (coming soon)
  8. 08LeadLeadership blueprint (coming soon)
  9. 09ArchitectArchitect blueprint (coming soon)
Portrait of Mike Salari

About the author

Mike Salari

Staff Mobile Engineer · Mobile Architect · Technical Author

I wrote this for Android engineers who need interview answers that survive follow-up: not definitions, but ownership, lifecycle boundaries, failure modes, measurement and trade-offs.

15 years building production mobile software, with experience across Apple, Adobe, Cisco, Mastercard and Visa. 500+ technical interviews from the hiring side.

Read the full story

Before or after you buy

Not ready yet? Use the Android answer card →

Already know the material and need to practise saying it? Interview Runtime: iOS and Android interview practice books with a practice dashboard, $59 each or $89 for both. Start with this book if the material itself is still new.

Already own it? After Senior Signal, rehearse the answers you need under time pressure. Add deadline rehearsal →

Free guides: Staff mobile engineer resume guide · Resume metrics for mobile engineers

FAQ

The senior signal: questions before you buy

Is this only for senior Android engineers?

No. It is strongest for mid-level, senior, staff, lead and architect-level candidates. Mid-level engineers can use it to understand what senior answers sound like.

Is this a question bank or a full book?

Both. The full edition includes 28 chapters, 119 worked deep-answer scenarios and a 401-question Android interview bank.

Does it include answers?

Yes. The main chapters teach the reasoning behind strong answers, including traps, follow-ups, case studies and senior framing. The appendix gives the wider question bank for self-testing.

Does it cover Jetpack Compose?

Yes. It covers Compose, state, recomposition, stability, lifecycle-aware collection, side effects, UI architecture and Compose-related interview traps.

Does it cover system design?

Yes. It includes mobile system design, offline-first architecture, sync, feature flags, migrations, architecture, modularization and senior-level design trade-offs.

Prepare for the Android interview you are actually in.

Get the full Senior Signal. 28 chapters. 119 worked deep-answer scenarios. 401 Android interview questions. Source notes through July 2026. PDF and EPUB. Updated editions included.

Get the book, From $59

Share this book

XLinkedInBlueskyThreadsHacker News