Adobe Software Engineer interviews typically run 3–5 rounds: recruiter screen, online assessment or HackerRank, technical interview(s), and a manager round. The process spans roughly one to two and a half months and is notably broad, mixing DSA, OOP, system design, and frontend fundamentals.
$119K
Avg. Base Comp
$291K
Avg. Total Comp
4-6
Typical Rounds
4-10 weeks
Process Length
What stands out most across Adobe's Software Engineer interviews is the sheer breadth of what they test — and how that breadth can catch even well-prepared candidates off guard. Multiple candidates reported that what looked like a focused coding screen quickly expanded into OS concepts, multithreading, API design, and system-level reasoning, often within the same 90-minute block. One candidate described a hiring manager round that started with BST design, pivoted to mathematical complexity proofs, and ended with a producer-consumer pseudocode problem — all in a single session. That's not a fluke; it's a pattern we see repeatedly.
The other thing worth understanding is that Adobe's process is genuinely inconsistent across teams. Some candidates saw a frontend-heavy HackerRank assessment with React and Node.js. Others got deep C++ fundamentals and smart pointer discussions. One process emphasized GenAI topics; another leaned hard into OOP theory and exception handling. This isn't a company where you can reverse-engineer a single prep path. What is consistent is that interviewers want you to explain your reasoning clearly — not just arrive at a correct answer. The candidate who was asked to write pseudocode for a non-optimal solution to a grid problem is a good example: Adobe often cares more about how you think through a problem than whether you nail the optimal approach immediately.
Finally, the frontend interviews deserve special mention. Candidates who made it to onsite rounds reported screen-sharing sessions with no search allowed, covering everything from JavaScript hoisting to function chaining on object arrays. The no-Google constraint made even routine questions feel high-stakes. Knowing your fundamentals cold — not just being able to look them up — is what separates candidates who clear these rounds from those who don't.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Adobe process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Adobe
Why would comments per user increase by 10% but posts go down 2%, and what metrics would prove your hypotheses
| Question | |
|---|---|
| Real-Time Transaction Streaming | |
| Google Maps Improvement | |
| Weekly Aggregation | |
| Hurdles In Data Projects | |
| Search Ranking | |
| Replace Words with Stems | |
| Success Measurement | |
| The Longest Journey | |
| Ticket Reservation Locking | |
| Confidence Interval Explanation | |
| Decreasing Subsequent Values | |
| Shortest Path Algorithms | |
| Text Editor With OOP | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Comments Histogram | |
| Upsell Transactions | |
| Find the Missing Number | |
| Raining in Seattle | |
| Customer Orders | |
| Bagging vs Boosting |
Synthesized from candidate reports. Individual experiences may vary.
An initial call where the recruiter or HR explains the role, asks about your background and experience, and assesses general fit. Some candidates were also asked an easy SQL or coding question at this stage.
A HackerRank-based assessment that may include multiple-choice questions on language basics, reasoning, and math, along with one to two coding problems ranging from easy to medium difficulty. Some versions are split into backend and frontend sections (e.g., Node.js and React) within a 90-minute window, and the assessment may be monitored with video and audio.
A video or phone-based technical interview covering DSA, OOP, operating systems, and core CS fundamentals, often drawing from the candidate's resume and projects. The round typically includes theoretical questions followed by one or two live coding problems on an online compiler or HackerRank, with an emphasis on clean code and clear explanation of design choices.
A call with the hiring manager to assess role fit, discuss background, and sometimes explore opinions on engineering tools or practices. This round may also include deeper technical questions on topics like system design, C++, or data structures depending on the team.
A series of two to four interviews typically covering coding (LeetCode-style medium problems), system design, frontend or backend technical knowledge, and a behavioral or managerial round. Coding is often done via screen share with no internet access allowed, and questions can span JavaScript fundamentals, API design, C++ internals, OS concepts, and low-level design.