Adobe Software Engineer interviews reported here commonly combine an assessment or screen with live technical discussion. Prepare for algorithm reasoning, core CS or language fundamentals, and a resume- or project-focused conversation.
$156K
Avg. Base Comp
$309K
Avg. Total Comp
4 rounds
Typical Rounds
4-10 weeks
Process Length
Adobe Software Engineer candidates describe several different routes, but the recurring preparation theme is breadth: an assessment or first screen may test coding alongside fundamentals, and later conversations may probe how you reason aloud. Do not prepare only for a standard algorithm screen. One candidate reported a timed assessment with coding, aptitude, English, and logical reasoning; another reported multiple-choice questions spanning operating systems, databases, networks, computer organization, and language fundamentals.
Technical formats vary materially by team and candidate. Reported exercises include BFS-based graph work, binary-search-tree validation, live debugging, and questions about Java collections or concurrency. Several candidates also described resume and project discussion, including follow-ups about project outcomes, engineering tradeoffs, contributions to a large codebase, or turning a personal project into a viable product. Explain your approach, edge cases, and tradeoffs rather than treating the answer as a silent coding exercise.
One candidate described four phases, but that is not a universal format. Reported processes can include an assessment or recruiter conversation, technical interviews, then a manager, panel, or behavioral discussion. Exact sequencing varies across reports, and the supplied accounts do not establish a consistent end-to-end timeline.
Synthesized from 41 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 | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Comments Histogram | |
| Upsell Transactions | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report online assessments and early screens that can mix coding with aptitude, logical reasoning, English, language questions, or core CS subjects. Reported coding difficulty ranges from straightforward math-oriented problems to medium graph work, so practice implementing carefully under a clock rather than assuming a coding-only format.
Technical discussions reported by candidates range from tree validation, BFS, dynamic programming, and substring/backtracking work to debugging an unfamiliar application. Other accounts include OOP, databases, operating systems, Java collections, concurrency, or language-specific questions. State assumptions, edge cases, complexity, and tradeoffs as you work.
Candidates report later conversations with a hiring manager, a panel, or behavioral interviewers. These may cover resume projects, internships, engineering tradeoffs, large-codebase contributions, motivation, and ambiguous situations; some accounts also include technical follow-ups or puzzles. Prepare concise examples with a clear personal contribution and outcome.
