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.
Synthetized from 7 candidates 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.
I had a pretty mixed process with Adobe, and the part that stood out most was how much it varied by round. I first went through a phone screen, and then I was invited to a technical assessment on HackerRank. That assessment was split into backend and frontend sections and had to be done in a 90-minute window. The backend portion was a Node.js problem, and the frontend portion was React. I don’t work much with vanilla Node, so that round was where I struggled and ultimately didn’t make it through.
What surprised me was that the process didn’t stop there for everyone. I also heard of a path that started with a behavioral interview first, with a very warm interviewer, and then moved into a two-part final round that was technical followed by behavioral. That technical round included general technical questions plus a few whiteboard-style exercises, including parsing HTTP code, while the behavioral side leaned into system design-style discussion. Another process I saw was more interview-heavy, with around six 30-minute interviews over about a month, mostly technical, and another candidate described four total interviews spread across virtual and in-person rounds over roughly two and a half months. So the overall feel is that Adobe can be pretty thorough and can stretch out over time.
For me, the biggest takeaway was that they seemed to care about both practical coding and broader engineering fundamentals like API design, system design, and web development basics. If I were doing it again, I’d make sure I was comfortable with Node/React implementation details and also ready for whiteboard questions that test how you think through HTTP and system-level behavior. In my case, I didn’t get an offer, but the process itself was professional and fairly well organized.
Prep tip from this candidate
Be ready for a HackerRank-style assessment that can split into backend Node.js and frontend React within a tight 90-minute window. Also practice whiteboard questions around HTTP parsing and be comfortable discussing API design and system design in later rounds.
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.
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Replace Words with Stems | |
| Search Ranking | |
| Weekly Aggregation | |
| Confidence Interval Explanation | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Prime to N | |
| Random SQL Sample | |
| Comments Histogram | |
| Subscription Overlap | |
| Upsell Transactions | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Weighted Keys | |
| Largest Salary by Department | |
| First Touch Attribution | |
| String Shift | |
| P-value to a Layman | |
| Customer Orders | |
| Find Bigrams | |
| Last Transaction | |
| Scrambled Tickets | |
| Minimum Change | |
| Rectangle Overlap | |
| Closest SAT Scores | |
| The Brackets Problem |
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.