Adobe Interview Questions
& Process for Software Engineers

Adobe's reputation for a humane loop is earned, and it is the reason people walk in underprepared. The difficulty is not concentrated in one brutal round. It is spread thin across more ground than most loops cover. The screen that gates the onsite pairs two medium coding problems with a block of multiple-choice questions on operating systems, databases, and networking, and that fundamentals section has been getting heavier each cycle. Linked lists come up far more here than at the companies you are probably comparing against. None of it is hard, and all of it is easy to have not thought about in six years. A recruiter screen opens the process, the onsite runs four to five rounds, and the whole thing takes a few weeks end to end.

After the onsite the interviewers debrief together and settle it in conversation rather than averaging a set of scores. Once that lands your way, team matching and the offer follow. Passing generally means consistent signal across the rounds with no hard no on anything core and technical, which is a lower bar than a FAANG committee and a harder one to game. Adobe lists its open engineering roles on its own careers site.

The split shifts with the team and the level. New-grad loops usually drop system design, Staff loops sometimes add a second one, and Adobe runs no standardized question set, so your interviewers are picking their own problems rather than pulling from a company bank. Whatever the mix, you spend most of the day typing in a shared editor, and in at least one seat you are holding a design together out loud while somebody pushes on it.

The object-oriented design round is the seat that catches people out. You get a real feature to model, a parking lot or an elevator or a card game, and you build the classes for it in a shared editor while the requirements keep growing under you. Nobody is timing your algorithm. They are watching whether the third change request breaks everything you wrote in the first ten minutes.

Coding

Broad medium difficulty data structures and algorithms: clean, working code with the edge cases handled

Object-oriented designDistinctive round

Model a real feature with classes and interfaces, then extend it as requirements grow

System design

A generic-leaning design problem: a document editor, asset management, typeahead, or a rate limiter

Behavioral

Collaboration, ownership, and alignment with Adobe’s values

The coding rounds run on CoderPad with your code executing against real tests, and the problems sit at the easy-to-medium tier: arrays, strings, trees, graphs, and the occasional dynamic-programming or heap question. Adobe is unusually explicit that it grades clean, readable, optimized code above a perfect test sheet. Clear seven of ten hidden cases with something an interviewer can follow and you are in good shape, which is not the habit an online judge spends years training into you.

The design round rewards a different rhythm. Something small and working on the screen inside the first ten minutes buys you the rest of the hour, and from there the job is narrating the model rather than the code inside it. SOLID and the standard patterns are the vocabulary here, and the candidates who do well leave obvious seams where the next requirement is going to land.

Every interviewer files a written rating for the round they ran, and then they argue it out together. The specifics are what travel. A round somebody described in detail keeps its weight in that conversation, while a strong score with two thin sentences behind it falls apart the moment another interviewer asks what you actually did.

Consistency is what carries a borderline case, and it is the thing candidates spend the least effort on. Most people have one round they are proud of and one they treated as a formality on the way to it. The formality round is the one that produces a shrug in the debrief, and a shrug from any seat is enough to stall a packet that would otherwise sail through.

Your interviewers are the only people in that room who ever met you, which makes them advocates by default, though they can only advocate with what they wrote down. The reasoning you narrated is the reasoning that reaches the notes. Anything you worked out silently, however good, is gone by the time the debrief starts.

Offers combine base salary, equity, and a bonus, and because Adobe is a public company the equity is tradable stock you can price at today's number instead of guessing at a private valuation. The complication is the band. Adobe sets pay by level and location and almost never goes above it, so the ceiling on your negotiation is already set before anyone says a number out loud.

Average total compensation by level per Levels.fyi (US, October 2026), across 2,223 US reports; self-reported and updated continuously. Adobe labels these rungs both as Software Engineer 1 to 5 and as pay grades P10 to P60, and the overall software-engineer median is about $213K.

There is real room inside that band, and knowing which pieces move is most of the work. The signing bonus has the most give in it, and it is the one lever you can pull without a competing offer in hand. Base moves less, though every dollar there also lifts the bonus riding on top of it. A competing offer is still the strongest thing you can bring, and its job is to carry you to the top of your band rather than past it.

Open the conversation a day or two after the offer lands, while the manager who interviewed you still has a say in the number. Ask where the top of the band sits, because Adobe recruiters are often willing to tell you. Then do the arithmetic on the pieces the offer letter never quotes, since the ESPP alone changes how an Adobe total compares against a bigger-looking one somewhere else.