Adobe · Software engineer · all levels
STAR-format project deep-dive on ownership, trade-offs and measurable impact
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
Adobe’s published process. Lime marks the stage this round runs.
Built from what Adobe publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
The five stages (application, Talent Partner conversation, hiring manager interview, skills assessments and team interviews, offer and onboarding); portfolio or GitHub advice for technical roles; the per-role assessment list (technical: coding challenges, system design discussions, portfolio reviews); measurable-impact prep guidance; the hiring-team debrief; and the offer conditions (proof of right to work, background check, conflict-of-interest questionnaire).
Be Genuine as a named Adobe company value; the instruction to lead with your own voice; and the rule that candidates should not use AI recording, live scribing, or conversation prompting tools during hiring conversations unless invited to.
Adobe organises hiring by function (Engineering and Product, Design, Research, Sales, Finance and Operations, IT, Customer Experience), not by product cloud, which is why one published process covers every product org.
Adobe SWE level ladder (P10 Software Engineer 1 through P40 Software Engineer 4, up to P60) and compensation structure. Carries no interview-process content.
The four dimensions coding rounds are scored on across big tech (communication, problem solving, technical competency, testing) and the strong hire / hire / no hire bands.
System design rounds are typically given to more senior candidates, and object-oriented design (classes, interfaces, design patterns) is a recognised system-design format.
The general shape of a big-tech software engineering loop, and that system design preparation applies at mid and senior levels.
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Friendly, conversational resume walk-through
One problem in a live shared editor, a second if the first goes fast
One or two problems in a live shared editor, with a push to optimize
A high-level design problem, sometimes with a smaller object-oriented design piece attached