Sources checked
Adobe
Adobe publishes one hiring process for every product org, and what changes is the role: technical candidates get coding challenges, system design discussions or portfolio reviews, creative candidates get briefs and design exercises. Be Genuine is a named company value, and Adobe asks candidates to lead with their own voice.
The Adobe process
3 of 5 stages you can practise here
- 01Application
Resume plus, for technical roles, a portfolio or GitHub link. Adobe asks for work that shows impact and creativity, not just responsibilities.
- 02
Friendly, conversational resume walk-through
communicationmotivationbackground fit - 03
STAR-format project deep-dive on ownership, trade-offs and measurable impact
ownershipproblem-solvingimpact - 04Skills Assessments & Team Interviews
Interviews with potential team members, stakeholders and partners. For technical roles Adobe lists coding challenges, system design discussions, or portfolio reviews, and says some candidates are asked to complete other assessments depending on the role or function.
3 rounds you can practise
One problem in a live shared editor, a second if the first goes fast
data structures & algorithmscomplexitycode cleanlinessOne or two problems in a live shared editor, with a push to optimize
dsa depthoptimizationcomplexityA high-level design problem, sometimes with a smaller object-oriented design piece attached
requirements scopingarchitecturedata modeling - 05Offer & Onboarding
The hiring team debriefs and makes a final decision. An offer letter and new hire documents arrive in your candidate profile, then proof of your right to work, a background check, and a conflict-of-interest questionnaire.
Common questions
- How many interview stages does Adobe have?
- Adobe's How We Hire page describes a five-stage process: application, a Talent Partner conversation, a hiring manager interview, skills assessments and team interviews, and finally offer and onboarding. The skills-and-team stage is where the multiple technical rounds live.
- Does Adobe's interview loop differ by product org?
- Adobe publishes a single hiring process and organises its careers site by function rather than by Creative Cloud, Document Cloud or Experience Cloud. The variation Adobe documents is by role: technical, design and creative, and sales candidates each get a different set of assessments, and some candidates get extra ones depending on the role or function.
- Should I submit a portfolio or GitHub?
- Yes. For creative or technical roles Adobe's careers site tells candidates to showcase work that illustrates impact and creativity, not just responsibilities, and to consider including a portfolio or GitHub link with the application.
- What do Adobe's technical rounds cover?
- Adobe says technical candidates should expect coding challenges, system design discussions, or portfolio reviews, plus interviews with additional team members and stakeholders. Design rounds are generally reserved for candidates with a few years of experience, so early-career loops usually stay on coding.
- What does the hiring manager look for?
- Adobe advises preparing specific examples that demonstrate measurable impact. Expect a deeper dive on your background, your problem-solving, and how your experience aligns with the role, and treat it as a two-way conversation: Adobe tells candidates to come with questions about the team.
- Can I use AI during an Adobe interview?
- Adobe asks candidates not to use AI recording, live scribing, or conversation prompting tools during hiring conversations unless invited to. It encourages using AI to sharpen your thinking beforehand and to talk about how AI shows up in your work, but wants your own voice in the room.
Sources
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.