Adobe Software Engineer candidates report technical interviews spanning live data-structures-and-algorithms coding, language or web fundamentals, and design discussions; the exact sequence varies by team and specialization.
$175K
Avg. Base Comp
$250K
Avg. Total Comp
4 rounds
Typical Rounds
4-10 weeks
Process Length
Adobe Software Engineer interviews in these reports are technically broad rather than built around a single standardized loop. Live problem solving and clear explanation recur across the Software Engineer accounts. Candidates describe a roughly hour-long coding screen centered on trees and dynamic programming, two easy-to-medium problems involving a repeating substring and backtracking, and a four-round process with several C++ and data-structures questions.
For web-oriented paths, candidates report JavaScript fundamentals alongside practical coding, including fetching API data with throttling and a TypeScript type-predicate question. Another discussion involved designing an API with error handling and startup considerations. One frontend-labelled conversation instead became a collaborative editor and drawing-tool system-design exercise, so state your assumptions and restate the agreed scope when requirements change.
C++ and systems depth also appears in the evidence. Reported topics include smart pointers, static variables, delete[], operating-system concepts, producer-consumer reasoning, and designing a binary-search tree with specified operations and complexity constraints. Prepare to explain trade-offs, complexity, and implementation choices aloud rather than only producing an answer.
The emphasis depends on the team and specialization. Some candidates encountered DSA-heavy screens, while others were tested on JavaScript, C++, API design, or systems reasoning. Prioritize the track named in your interview communication while retaining core DSA practice and preparing to adapt if the stated focus changes.
Synthesized from 12 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.
The coding screen was the part that mattered most in my process. After a recruiter reached out, I had an initial discussion and then spoke with the hiring manager to arrange a technical screen. That interview was about an hour and leaned heavily into DSA, especially trees and dynamic programming. The coding question felt in the LeetCode medium-to-hard range and was primarily a dynamic programming problem, so it was less about knowing a particular product stack and more about working through the algorithm clearly under time pressure.
I was told that clearing the screen would lead to an onsite with roughly four or five conversations involving the team and cross-functional partners, although I did not make it that far. From what I saw, communication was important alongside getting the code right: being able to explain the approach and tradeoffs seemed essential. I ultimately did not receive an offer. I would focus preparation on tree and dynamic-programming problems at a medium-to-hard level, and practice narrating your reasoning while you code rather than treating the solution as a silent exercise.
Prep tip from this candidate
Prioritize medium-to-hard dynamic-programming and tree problems for the technical screen, then practice explaining your approach and tradeoffs aloud while coding.
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 | |
| Decreasing Subsequent Values | |
| Confidence Interval Explanation | |
| 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 | |
| Monthly Customer Report | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Comments Histogram | |
| Upsell Transactions | |
| Raining in Seattle | |
| Customer Orders | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter outreach or an initial discussion before technical scheduling. One account included an easy SQL question and an easy-to-medium coding problem during an early screen, while another described a hiring-manager conversation used to arrange the technical screen. Exact early-screen content varies.
Candidates report algorithmic coding that ranged from easy-to-medium substring and backtracking problems to a medium-to-hard dynamic-programming problem with trees. Other accounts describe medium LeetCode-style problems, API pagination, or a grid shortest-path pseudocode exercise. Explain the approach, complexity, and tradeoffs while coding.
Some candidates report JavaScript fundamentals followed by API-fetching code with throttling, while another reported TypeScript type predicates. A separate Software Engineer process covered C++ static variables, delete[], and smart pointers. The language emphasis appears to depend on the team and role focus.
Candidates report an API-design conversation addressing error handling and boot-time considerations, and a frontend-labelled session that shifted to a collaborative editor/design-tool design. Another report described C++ and operating-system discussion, including producer-consumer reasoning. Clarify assumptions and adapt when the problem scope changes.
