Adobe · Software engineer · all levels
Hiring Manager Interview
STAR-format project deep-dive on ownership, trade-offs and measurable impact
What they actually ask
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.
- “Walk me through the hardest technical decision you made on a project and the trade-offs involved.”
- “Tell me about a time you took ownership of a problem end to end.”
- “Describe a time you built or introduced something new, such as a tool, framework, or approach.”
- “Tell me about a cross-team or cross-functional initiative you drove.”
- “Tell me about a disagreement or conflict with a teammate and how you handled it.”
- “Why Adobe?”
What this round is judged on
- Ownership · drove a problem end to end
- Problem-solving · how you worked through the hard part
- Impact · measurable customer or creator outcomes
- Collaboration · cross-functional teamwork
- Trade-off reasoning · the why behind decisions
Where this round sits
Adobe’s published process. Lime marks the stage this round runs.
- 01Application
- 02Talent Partner Conversation
- 03Hiring Manager Interviewthis round
- 04Skills Assessments & Team Interviews
- 05Offer & Onboarding
What happens in each stage›
- Application
- Resume plus, for technical roles, a portfolio or GitHub link. Adobe asks for work that shows impact and creativity, not just responsibilities.
- Talent Partner Conversation
- An in-depth conversation with a Talent Partner about your background and career goals, the role, team dynamics, and what success looks like. Your chance to ask about culture and growth.
- Hiring Manager Interview
- A deeper dive on your background, your problem-solving, and how your experience aligns with the role. Adobe tells candidates to prepare specific examples that demonstrate measurable impact.
- Skills 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.
- Offer & 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.
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.
Other Adobe rounds
- Recruiter / Talent Partner Screen
Friendly, conversational resume walk-through
- Coding Screen
One problem in a live shared editor, a second if the first goes fast
- Onsite Coding / DSA
One or two problems in a live shared editor, with a push to optimize
- System Design & OO Design
A high-level design problem, sometimes with a smaller object-oriented design piece attached