Adobe Android Engineer Round 1: 3 Experiences (Part 10 of 12)

Shared by janebeingjane ·
Company
Adobe
Reports
3 interview reports
Level
Full-time
Stages
Phone screen

Adobe Android engineer round 1 reports from 2025–2026 focus on Android and Kotlin knowledge, with one packing problem and one Compose coding task.

At a glance

  • Process: one technical round. Candidate 62's was an hour on MS Teams, and 64's came after a hiring-manager chat. Later rounds were DSA on HackerRank, Android LLD and architecture, and a hiring manager (62), or more Android coding in Android Studio (64).
  • Asked: singletons, app performance, memory leaks and coroutines (62); placing shapes on a sheet with the least waste (63); a Compose function that keeps state across rotation (64).
  • Difficulty: none of the three rated the round. Candidate 62 got an offer, and 64 heard nothing after round 3.

Coverage: 3 Android reports from Oct 2025 to Aug 2026: MTS-2 (62), Computer Scientist 1 (63) and a Senior Android Design Engineer on the Spectrum Design team (64). The series covers 69 experienced-hire reports, first technical round only.

In this series

What came up

Each report named different questions, so the table lists them once each. Android platform knowledge was the common thread.

Topic Reports Last seen
Android platform (performance, leaks, coroutines) 1 of 3 Aug 2026 (report date)
Singletons and thread safety 1 of 3 Aug 2026 (report date)
Packing and placement 1 of 3 May 2026 (report date)
Jetpack Compose state 1 of 3 Oct 2025 (report date)

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Place rectangles on an m x n sheet to waste the least space 1: 63 May 2026 (report date)

Low-Level Design (LLD/OOD)

Question Reports Last seen
Write a basic singleton in Java; make it thread-safe; singletons in Kotlin 1: 62 Aug 2026 (report date)

Android / Mobile

Question Reports Last seen
Measure and diagnose Android app performance (leaks, jank, ANRs, crashes, slow I/O) 1: 62 Aug 2026 (report date)
Android memory leaks: causes and prevention; AndroidViewModel vs ViewModel 1: 62 Aug 2026 (report date)
Kotlin coroutines: scopes, launch vs async, cancellation, when Deferred starts 1: 62 Aug 2026 (report date)
Compose: draw objects on screen and keep them across rotation 1: 64 Oct 2025 (report date)
Compose: remember vs rememberSaveable, custom Saver 1: 64 Oct 2025 (report date)

3 Android round 1 reports

62: MTS-2 Android, an hour of Android and Kotlin basics

Report date: Aug 9, 2026 · Role: MTS-2, Android · Experience: 2 years · Result: Offer

Round 1: Android basics deep dive (first technical round, 1 hour on MS Teams)

  1. Intro: career path, open-source work, team structure, Android team size, and a typical day.
  2. What is a singleton class? Write a basic one in Java. Follow-ups: is it thread-safe, and how do you write singletons in Kotlin (object declaration, Java style, a synchronized block)? The talk also touched on JVM-only locking versus locking in Kotlin Multiplatform.
  3. How do you measure an Android app's performance? Cover memory leaks, UI jank, ANRs, crashes, and slow database, disk or compute work, and how you find the cause. The candidate mentioned Crashlytics and Android Studio's App Inspection.
  4. Memory leaks: what they are, Android examples, common causes and how to avoid them. Also AndroidViewModel vs ViewModel.
  5. Coroutines: what and why, threads vs coroutines, runBlocking, launch and async, CoroutineScope, viewModelScope and lifecycleScope, cancellation, and when an async Deferred actually starts running.

After round 1: Round 2 was DSA at the office on a live HackerRank session: the Nice Array removal count (pseudo-code and a dry run) and the farthest shop each query can reach, coded with prefix sums and binary search but with some failing tests when time ran out. Round 3 covered dependency injection with Dagger and Hilt, low-level designs for a search bar with suggestions and an infinite scroll list, and app architecture. The hiring manager round had 12 to 15 culture questions and a design for a promo processor that decides when Acrobat Reader shows promotions. The candidate got an offer.


63: CS-1 Android, packing shapes on a sheet

Report date: May 28, 2026 · Role: Computer Scientist 1 (Android)

Round 1 (first technical round)

  1. You get an m x n rectangular sheet and a list of shapes, each with a width and height. Place the shapes so the least space is wasted. Output each placement as width, height, x and y.

Only this one question was shared, with no notes on duration, format or result.


64: Senior Android Design Engineer, Compose state across rotation

Report date: Oct 2, 2025 · Role: Senior Android Design Engineer (Spectrum Design team) · Result: No reply after round 3

Before the first technical round: A friendly hiring manager chat about past work, Jetpack Compose, design systems, and mixing Views with Compose.

Round 2: Coding Android (first technical round)

  1. Write a Compose function that draws objects on the screen and keeps them when the device rotates.
  2. Concepts: remember vs rememberSaveable, and writing a custom Saver.

After round 2: Round 3 was more Android coding in Android Studio, with autocomplete allowed: fetch data from an endpoint and show it in a list, plus questions on Compose stability and immutability, pagination and lazy loading. After that the candidate heard nothing back.


Common questions

What Android questions does Adobe ask in the first round?

Candidate 62 had a full hour of them: thread-safe singletons in Java and Kotlin, measuring app performance, memory leaks, AndroidViewModel vs ViewModel, and coroutine scopes and cancellation. Candidate 64 had Compose state questions: remember vs rememberSaveable and a custom Saver.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesAdobe ML Engineer Round 1: 3 Experiences (Part 11 of 12)
0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.