Nov 2024–Nov 2026 Adobe Experienced-Hire First Technical Round: 69 Experiences (Part 10 :)
- Company
- Adobe
- Reports
- 4 interview reports
- Level
- Full-time
- Stages
- Phone screen
In this series
- Part 1: Machine learning engineers (01–03), then software engineers from Sep–Aug 2026 (04–06)
- Part 2: Software engineers, Aug–Jun 2026 (07–11)
- Part 3: Software engineers, May 2026–Nov 2025 (12–18)
- Part 4: Software engineers, Nov 2025–Jun 2025 (19–25)
- Part 5: Software engineers, Jun–Apr 2025 (26–31)
- Part 6: Software engineers, Apr–Feb 2025 plus year-only 2025 reports (32–37)
- Part 7: Software engineers, 2025 and Dec–Nov 2024 (38–43)
- Part 8: Last software engineers (44–45), then C++ engineers, Sep 2026–Sep 2025 (46–49)
- Part 9: C++ engineers, Aug–Apr 2025 (50–54)
- Part 10 (current): Android engineers (55–57) and the newest frontend report (58)
- Part 11: Frontend engineers, May 2026–Apr 2025 (59–65)
- Part 12: Last frontend reports (66–67), release engineering (68), product consultant (69), and patterns across all 69
Three Android rounds that looked nothing alike, then the newest frontend report.
Coverage: Experienced hires at Adobe, first live technical round only (the first coding or technical interview after any online test or recruiter call). Later rounds get a short note at the end of each timeline. This part: reports 55–57 (Android engineers: MTS-2, Computer Scientist 1, Senior Android Design Engineer; Aug 2026–Oct 2025) and 58 (MTS-2 frontend, Jul 2026) of 69.
Other Adobe first-round roundups: interns · hiring level not reported
Android engineers come first, then the newest frontend report. The frontend section continues in Parts 11 and 12.
Android engineers: what came up
Two of the three Android rounds were about the platform itself: Kotlin coroutines, memory leaks and Compose state. The third was a single shape-packing problem.
| Topic | Reports | Most recent report |
|---|---|---|
| Android and Kotlin | 2 of 3 | Aug 9, 2026 (report date) |
| Resume and project deep dive | 1 of 3 | Aug 9, 2026 (report date) |
| Low-level and object-oriented design | 1 of 3 | Aug 9, 2026 (report date) |
| Concurrency and threads | 1 of 3 | Aug 9, 2026 (report date) |
| Arrays and strings | 1 of 3 | May 28, 2026 (report date) |
Android engineers: questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Place rectangles on an m x n sheet to waste the least space | 1 report | May 28, 2026 (report date) |
Low-Level Design (LLD/OOD)
| Question | Frequency | All last seen dates |
|---|---|---|
| Write a basic singleton in Java; make it thread-safe; singletons in Kotlin | 1 report | Aug 9, 2026 (report date) |
Android / Mobile
| Question | Frequency | All last seen dates |
|---|---|---|
| Measure and diagnose Android app performance (leaks, jank, ANRs, crashes, slow I/O) | 1 report | Aug 9, 2026 (report date) |
| Android memory leaks: causes and prevention; AndroidViewModel vs ViewModel | 1 report | Aug 9, 2026 (report date) |
| Kotlin coroutines: scopes, launch vs async, cancellation, when Deferred starts | 1 report | Aug 9, 2026 (report date) |
| Compose: draw objects on screen and keep them across rotation | 1 report | Oct 2, 2025 (report date) |
| Compose: remember vs rememberSaveable, custom Saver | 1 report | Oct 2, 2025 (report date) |
Android engineers: 3 detailed candidate timelines
55: 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)
- Intro: career path, open-source work, team structure, Android team size, and a typical day.
- 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.
- 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.
- Memory leaks: what they are, Android examples, common causes and how to avoid them. Also AndroidViewModel vs ViewModel.
- 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.
56: CS-1 Android, packing shapes on a sheet
Report date: May 28, 2026 · Role: Computer Scientist 1 (Android)
Round 1 (first technical round)
- 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.
57: 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)
- Write a Compose function that draws objects on the screen and keeps them when the device rotates.
- 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.
Frontend engineers: what came up
This one frontend round mixed two counting problems with a JavaScript event-loop question.
Frontend engineers: questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Count Subsets with Sum K | 1 report | Jul 30, 2026 (report date) |
| Count Pairs with Absolute Difference K (LC 2006 family) | 1 report | Jul 30, 2026 (report date) |
Language and CS Fundamentals
| Question | Frequency | All last seen dates |
|---|---|---|
JavaScript output question: promise and setTimeout order (event loop) |
1 report | Jul 30, 2026 (report date) |
Frontend engineers: 1 detailed candidate timeline
58: MTS-2 frontend: two counting problems and an event-loop puzzle
Report date: Jul 30, 2026 · Role: MTS-2, frontend (JavaScript and React) · Experience: 3 years · Result: Offer
Before the first technical round: An HR call covered the candidate's stack, daily work, reasons for leaving, pay and notice period.
Round 1: Data structures and JavaScript (first technical round)
- Another MTS-2 ran the round. The first task was to count the subsets of an array that add up to k. The candidate talked through brute force, moved to dynamic programming, and coded it in C++.
- Next came counting pairs whose absolute difference is exactly k (LC 2006 family). A hash map did the job, again in C++.
- The round closed with a JavaScript output question: predict the print order of code that mixes promises and
setTimeout. It tests the microtask and macrotask queues. - They passed.
After round 1: Round 2 (data structures and React) had summing the even nodes on the path between two nodes of an array-indexed binary tree, a check for numbers with exactly three divisors, and a debounced typeahead in React. Round 3 mixed React internals with a pub/sub exercise for adding books from anywhere in an app, plus a question on how they use AI in daily work and which Claude skill they would write. Round 4 was behavioral, including a production issue they faced, plus a design for a PDF search box; it was repeated for another team after the first position closed. Round 5 brought a stakeholder pushing to halve the timeline, ways to control this, counting occurrences in a sorted array with hand-written lower and upper bounds, and a trie's add-word method. The candidate got the offer.
Keep practicing
- Farthest Affordable Shop per Query: practice problem from report 55.
- Minimum Removals for a Nice Array: practice problem from report 55.
- Count Subsets with Sum K: practice problem from report 58.
- Count Pairs with Absolute Difference K: practice problem from report 58.
- Tell me about a production issue you faced.: behavioral question from report 58.
- How do you use AI in your daily work?: behavioral question from report 58.
- If you wanted to write one Claude skill, what would you write?: behavioral question from report 58.
- You are on a tight timeline and a stakeholder pressures you to cut development time in half, even after you used AI to estimate. How do you respond?: behavioral question from report 58.
- Count Occurrences in a Sorted Array: practice problem from report 58.
- Numbers with Exactly Three Divisors: practice problem from report 58.
- Sum of Even Nodes on a Path in a Numbered Binary Tree: practice problem from report 58.
- Trie: Add and Search Words: practice problem from report 58.
- Adobe coding questions: the company-filtered question bank (sign-in needed).
- Adobe low-level design questions: the company-filtered question bank (sign-in needed).
- Adobe interview guide: Adobe's interview overview page on FastPrep.
- Adobe hiring insights: hiring activity and trends for Adobe.
- Experience feed: more interview experiences and roundups.
Other Adobe first-round roundups: interns · hiring level not reported
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.