Adobe Software Engineer candidates report a mix of online assessments, DSA-heavy technical rounds, core CS and OOP questions, project discussion, and sometimes low-level or system design, ending with a manager or HR conversation.
$166K
Avg. Base Comp
$213K
Avg. Total Comp
2-6 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Adobe's Software Engineer interviews as DSA-centered, with core CS fundamentals and project discussion layered on top. Several report an online assessment first, including one with greedy and dynamic-programming problems plus core-CS multiple-choice questions. Technical rounds then often pair a coding problem with questions on OOP, operating systems, databases, or C++ internals.
The coding problems reported are mostly easy-to-medium, though one candidate described a screen as medium-to-hard dynamic programming and tree work. Reported examples include longest substring without repeating characters, LRU cache, linked-list intersection, lowest common ancestor, meeting rooms, deleting the nth node from the end of a list, and next larger element. Some interviewers asked for pen-and-paper solutions or explicit time and space complexity, so practice narrating your reasoning.
Design shows up in different forms. One candidate reported two low-level design rounds and received an offer. Others described a distributed news feed, a testing-phase design, an API design with error handling, and a real-time collaborative editor. Expect the format to vary by team: one candidate got JavaScript and TypeScript questions, another got a Python OOP screen, and a third was pushed on thread safety.
Outcomes in the reported experiences are mixed, with offers and rejections both represented. Be ready to discuss your resume and projects in depth, since that came up in many accounts.
Synthesized from 74 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 whole process moved surprisingly fast for a company of Adobe's size. From start to finish it took less than a week, and I had three interviews in that window. The first was with two developers from the team, and the question that stuck with me was how I had managed technical people. I did not expect that from a developer panel, so it's worth thinking about before you go in. The second interview was with a project manager and the hiring manager, and the third was with the org director, who seemed to be looking at the bigger picture of how I would fit into the organization.
What I'd tell someone preparing is not to assume the loop will be purely technical. Each interviewer seemed to be checking a different angle, so I'd recommend having a few concrete examples ready about working with and guiding other engineers, and adjusting them depending on who is in the room. The quick timeline also means there's little room to catch up if you're underprepared, so get your stories organized before you start.
I ended up receiving an offer and accepting it.
Prep tip from this candidate
Prepare concrete stories about managing or leading other engineers, since the first round with two developers centered on how you've managed technical people.
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 | |
| Success Measurement | |
| Replace Words with Stems | |
| Search Ranking | |
| RAG Strict Source Control | |
| Ticket Reservation Locking | |
| The Longest Journey | |
| Confidence Interval Explanation | |
| Decreasing Subsequent Values | |
| Shortest Path Algorithms | |
| Text Editor With OOP | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Prime to N | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Upsell Transactions |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. Some describe an online assessment mixing core-CS multiple-choice questions with greedy or dynamic-programming coding problems, and one intern described a monitored version. Others report a recruiter or hiring-manager call, sometimes with an easy SQL or coding question. Not every candidate describes this stage.
Candidates typically describe one or more rounds of live coding on arrays, strings, linked lists, trees, or dynamic programming, usually easy-to-medium. Reported problems include LRU cache, longest substring without repeats, and meeting rooms. Interviewers sometimes gave hints and asked for time and space complexity, and some asked for pen-and-paper work.
Alongside coding, candidates report questions on OOP, operating systems, databases, networking, or C++ internals, plus detailed questions about resume projects. Depth appears to vary by interviewer and team, with one candidate reporting concurrency and thread-safety follow-ups after an object-oriented design problem.
Some candidates describe design discussions, such as two low-level design rounds, a distributed news feed, API design with error handling, or a collaborative editor. These may not appear in every loop. Candidates suggest clarifying scope early and stating tradeoffs, since requirements reportedly shifted in at least one round.
Candidates report a closing manager or HR conversation covering background, team fit, motivation, and behavioral questions. One described a hiring-manager round that turned into deep DSA, C++ and operating-systems questions instead, so prepare for technical content there too.
