Adobe Experienced Round 1: 69 Experiences (Part 1 of 12)
- Company
- Adobe
- Level
- Unknown
- Stages
- Phone screen
Adobe experienced-hire round 1 from Nov 2024 to Nov 2026 was usually two coding problems, plus deep C++, JavaScript or ML questions for those roles.
At a glance
- Process: for software engineers, round one was a coding round, with two or more problems in 27 of 42 reports. Three had an online test first (33, 35, 36), and 11 had several rounds on one day or at a hiring drive. Later rounds were mostly LLD or system design, then a hiring manager and often a director.
- Asked recently: among the 42 software engineers, résumé or past-work questions came up in 13, trees in 10, dynamic programming in 8 and sliding windows in 5. Four problems were named twice: Least Frequently Used Cache Simulator, Merge Overlapping Intervals, Longest Stretch With At Most K Different Letters and Most Cash From Non-Neighboring Houses.
- Difficulty: most named problems are LeetCode mediums, but interviewers often asked for optimal, running code and edge cases (Part 5's pattern). C++, frontend and Android rounds spent as much time on the language as on the coding (Parts 8–10).
- Practise first: the four problems above, plus Least Recently Used Cache With O(1) Calls and Rain Water Held Between Bars (each also named in a C++ or release-engineering round).
Coverage: 69 experienced hires, first technical round only (the first live coding or technical interview after any online test or recruiter call); later rounds get a short note at the end of each entry. Software engineers make up 42 reports (MTS-1/2, Computer Scientist 1/2, senior CS, SDE and senior engineers), plus 9 C++ engineers, 10 frontend, 3 Android, 3 ML engineers and 2 other roles. Mostly India (Noida, Bengaluru), a few in the U.S. Reports before Nov 2024 are in the Adobe experienced-hire series that covers every round. Other Adobe first-round roundups: interns · hiring level not reported.
In this series
- Part 1 (current): overview
- Part 2: MTS-2, Jun 2025–Sep 2026 — 8 MTS-2 reports, entries 01–08
- Part 3: MTS-1 and MTS-2, Nov 2024–May 2025 — 7 more MTS reports, entries 09–15
- Part 4: Computer Scientist 1, Jul 2025–Aug 2026 — 8 CS-1 reports, entries 16–23
- Part 5: Computer Scientist 1, Dec 2024–Aug 2025 — 7 more CS-1 reports, entries 24–30
- Part 6: CS-2 and Senior Computer Scientist — 4 reports, entries 31–34
- Part 7: SDE, SE2 and senior engineers — 8 reports, entries 35–42
- Part 8: C++ engineers — 9 reports, entries 43–51
- Part 9: frontend engineers — 10 reports, entries 52–61
- Part 10: Android engineers — 3 reports, entries 62–64
- Part 11: machine learning engineers — 3 reports, entries 65–67
- Part 12: release engineering and product consultant — 2 reports, entries 68–69
What came up
These counts cover the 42 software engineers (Parts 2–7); each other role has its own table in its part. Talk about the candidate's own work came up more often than any coding topic.
| Topic | Reports | Last seen |
|---|---|---|
| Résumé, projects and past work | 13 of 42 | Aug 2026 (report date) |
| CS fundamentals (databases, OS, language) | 11 of 42 | Aug 2026 (report date) |
| Trees and hierarchies | 10 of 42 | Sep 2026 (report date) |
| Dynamic programming | 8 of 42 | Sep 2026 (report date) |
| Sliding window | 5 of 42 | Jul 2026 (report date) |
| Heaps and streams | 5 of 42 | Nov 2025 (report date) |
| Caches (LFU, LRU, cache design) | 4 of 42 | Aug 2026 (report date) |
| Design work in round 1 | 4 of 42 | Aug 2026 |
| Intervals | 3 of 42 | Aug 2026 (report date) |
| Graphs (BFS, connectivity) | 3 of 42 | Apr 2026 |
| Stacks and queues | 2 of 42 | May 2025 (report date) |
Questions we found
The full tables are in each role's part. These are the problems that more than one software engineer named in round one.
| Question | Reports | Last seen |
|---|---|---|
| Least Frequently Used Cache Simulator (LeetCode 460) | 2: 02, 22 | Aug 2026 (report date) |
| Longest Stretch With At Most K Different Letters (LeetCode 340) | 2: 17, 37 | Jun 2026 |
| Merge Overlapping Intervals (LeetCode 56) | 2: 02, 33 | Aug 2026 (report date) |
| Most Cash From Non-Neighboring Houses (LeetCode 198) | 2: 26, 36 | Jun 2026 (report date) |
Patterns across the reports
- Two problems is the norm for software engineers. 27 of the 42 first rounds had two or more coding problems; the exceptions were mostly résumé-heavy rounds (03, 16) or design-first rounds (31, 39).
- Same-day loops. Eleven software engineers had several rounds on one day or at a hiring drive (03, 07, 09, 16, 17, 18, 21, 22, 24, 37, 41).
- The offer level can move. Candidate 30 applied for MTS-2 and was offered CS-1; two frontend candidates interviewed for CS-1 and were offered MTS-2 (57, 61); 19 was told the team wanted more experience and an MTS-2 level was discussed.
- The same questions across roles. Rain water and the long-ID store with O(1) operations came up for a CS-1 (27) and a C++ MTS-2 (49); the stream median came up for an SE2 (40) and a release engineer (68); LRU came up for an MTS-2 (08) and the release engineer (68).
Common questions
How many interview rounds does Adobe have for experienced hires?
Often four or five. After round one, most loops had one or two design rounds (LLD or system design), a hiring manager and often a director, for example 04, 11, 23 and 49. Some ended after round one (07, 14, 25).
Is there an online test before the Adobe technical interview?
For a few. Three software engineers had one (33, 35, 36), and the product consultant had an 80-minute coding test (69). Most went straight from a recruiter call to round one.
What does the Adobe director round ask?
The reports vary: a stack-based rewrite of working code (02), full KMP and Kadane code (11), a secret-vault design with encryption (12), how the candidate reviews a PR (22) and a sales-related system design (16).
How hard is the Adobe first round?
Mostly LeetCode medium. Candidate 01 called both problems hard and 36's ran easy to hard, while CS-2 candidates described warm-ups (32, 33). Strict grading mattered as much as difficulty (25, 27).
What to practise
- Least Frequently Used Cache Simulator and Least Recently Used Cache With O(1) Calls. Caches came up in 4 of 42 software-engineer rounds (02, 08, 16, 22), most recently Aug 2026, and LRU again for the release engineer (68).
- Longest Stretch With At Most K Different Letters. Named twice (17, 37), most recently Jun 2026; sliding windows came up in 5 of 42.
- Merge Overlapping Intervals. Named twice (02, 33); intervals came up in 3 of 42.
- Most Cash From Non-Neighboring Houses. Named twice by software engineers (26, 36) and once by a C++ engineer (48); dynamic programming came up in 8 of 42.
- Rain Water Held Between Bars and Long-ID Store Without Hashing. Both asked together in two rounds (27, 49).
Keep practicing
- Adobe coding bank: every Adobe algorithm problem in the question bank (sign-in needed).
- Adobe design banks: low-level design and system design questions.
- Adobe ML modeling bank: the ML modeling questions.
- Other Adobe roundups: experienced hires before Nov 2024, interns, new grads, and the first-round roundups for interns and hiring level not reported.
- Adobe overview: the Adobe interview page and Adobe hiring insights.
- More reports: the Experience feed.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.