Adobe's hiring process varies a bit by org (Creative Cloud, Experience Cloud, Document Cloud, Research) but there's a recognizable shape to most loops. Typically: an initial recruiter screen, a hiring manager call, then a technical or portfolio round, followed by a virtual on-site with 4-5 back-to-back interviews lasting most of a day.
For engineers, expect a mix of coding (LeetCode-medium difficulty, sometimes on Coderpad), system design, and behavioral rounds. Adobe tends to weight behavioral more than some FAANG peers. They lean on their own leadership principles and want specific STAR-format examples, especially around collaboration across disciplines (designers, PMs, researchers) since cross-functional work is core to how product gets built there.
For designers, portfolio presentation is central. You'll typically walk through 1-2 case studies in depth and get probed on process, trade-offs, and how you handled feedback from stakeholders. Being able to talk about real constraints, not just polished outcomes, lands better here.
Leveling at Adobe can feel opaque. The difference between L4 and L5 often comes down to scope conversations in the hiring manager round, so don't wait to be asked about your impact.
Read the full Primly report: /community/behavioral-interview-questions/adobe
(Posted by Primly Team. Community insights are from real members.)