Adobe Other Roles Round 1: 2 Experiences (Part 12 of 12)
- Company
- Adobe
- Reports
- 2 interview reports
- Level
- Full-time
- Stages
- Phone screen
Two Adobe round 1 reports outside the main engineering titles: a release engineering role behind an MTS-2 posting, and a product consultant.
At a glance
- Process: candidate 68 had a 70-minute round mixing DSA, OOP and databases, with pseudo-code accepted. Candidate 69 took an 80-minute online test, then a 50-minute face-to-face round.
- Asked: Median of a Number Stream and Least Recently Used Cache With O(1) Calls in pseudo-code plus broad system fundamentals (68); networking and OS questions (69).
- Difficulty: candidate 68 found the interviewer friendly and cleared three rounds before declining; 69 was rejected after the face-to-face round.
Coverage: 2 reports from 2025: an MTS-2 posting that turned out to be release engineering (68) and an Associate Technical Product Consultant in India (69). The series covers 69 experienced-hire reports, first technical round only.
In this series
- Part 1: overview — the process, most-asked problems and a guide to every role
- 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 (current): release engineering and product consultant
What came up
Both rounds leaned on fundamentals; only 68's included coding.
| Topic | Reports | Last seen |
|---|---|---|
| System and database fundamentals | 2 of 2 | Jul 2025 (report date) |
| Heaps | 1 of 2 | Jul 2025 (report date) |
| Caches | 1 of 2 | Jul 2025 (report date) |
| Networking | 1 of 2 | Jan 2025 |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Median of a Number Stream (LeetCode 295) | 1: 68 | Jul 2025 (report date) |
| Least Recently Used Cache With O(1) Calls (LeetCode 146), pseudo-code only | 1: 68 | Jul 2025 (report date) |
Language and CS Fundamentals
| Question | Reports | Last seen |
|---|---|---|
| Fundamentals: scaling, load balancers, CAP, DB locking, SQL vs NoSQL, normalization, OS locks | 1: 68 | Jul 2025 (report date) |
| Networking: OSI and TCP/IP models; how an API works | 1: 69 | Jan 2025 |
| OS: deadlock conditions; virtual memory | 1: 69 | Jan 2025 |
2 round 1 reports from other roles
68: MTS-2 that turned out to be release engineering, median and LRU in pseudo-code
Report date: Jul 24, 2025 · Role: Applied for MTS-2; the role turned out to be release engineering · Result: Cleared three rounds, then declined before the director round
Round 1 (first technical round, about 70 minutes)
The round mixed DSA, system design, OOP and databases. The interviewer was friendly and gave time to think.
- Find the median of a stream of integers (LC 295). The candidate explained two heaps and how to rebalance them, with O(log n) inserts and an O(1) median. Only an explanation and pseudo-code were needed.
- A broad fundamentals talk: scaling, performance, concurrency, load balancers, the CAP theorem, database locking, SQL vs NoSQL and when to pick each, normalization, OS locks and atomicity.
- Implement an LRU cache (LC 146) in pseudo-code, using a hash map plus a doubly linked list.
The invite for round 2 came the same day.
After round 1: Round 2 had a long medium problem solved with backtracking, the friends-by-age request problem (LC 825), and questions on Jenkins, CI/CD, AWS, Kubernetes, Docker and Kafka from past work. The hiring manager round covered projects and ownership, plus finishing jobs on two single-task schedulers, with a follow-up for job dependencies. At some point the role turned out to be release engineering, and the candidate declined before the director round.
69: Associate Technical Product Consultant, networking and OS basics
Interview date: Jan 17, 2025 · Role: Associate Technical Product Consultant · Experience: 0 to 2 years · Location: India · Result: Rejected
Before the first technical round: An 80-minute online coding test in Oct 2024 with two problems: the left view of a binary tree and the longest common subsequence.
Round 2: Face to face (first live technical round, 50 minutes)
- Networking: the OSI model, the TCP/IP model and its layers, and how an API call works.
- Systems: what a deadlock is and the conditions it needs, and what virtual memory is.
The candidate was rejected after this round.
Common questions
What does Adobe ask in a release engineering round?
In the one report, a 70-minute round mixed the median of a stream and an LRU cache in pseudo-code with fundamentals: scaling, CAP, database locking, SQL vs NoSQL and OS locks (68). Later rounds added Jenkins, CI/CD, AWS, Kubernetes, Docker and Kafka.
Keep practicing
- Practice from these reports: Find the median of a stream of integers (68); Implement an LRU cache (68).
- Adobe coding bank: every Adobe algorithm problem in the question bank (sign-in needed).
- 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.