Did the Adobe frontend engineer interview loop last month for a role on the Creative Cloud web team. Here's exactly what happened.
Recruiter screen (30 min): Intro, role overview, basic "why Adobe" chat. She mentioned the team works primarily in React with some legacy Angular they're slowly migrating. Good to know.
Technical phone screen (60 min): One coding problem, JavaScript-specific. They had me implement a debounce function from scratch, then asked me to extend it with a leading edge option. I've done this on LeetCode-adjacent sites before but the extension caught me slightly off guard. Then they asked a CSS question: explain how stacking contexts work and when z-index doesn't do what you expect. That one separated people I think.
Onsite round 1: UI implementation (75 min): Build a paginated list component. No frameworks, vanilla JS and HTML in a CodeSandbox-type environment. They cared a lot about accessibility: keyboard nav, ARIA labels, focus management. This was the hardest round for me personally. If you're a React dev who hasn't written vanilla JS in a while, spend some time there.
Onsite round 2: system design for frontend (60 min): Design a drag-and-drop editor (fitting, given Adobe's products). We talked about state management approach, undo/redo history stack, performance for large canvases, and how I'd handle collaborative editing at a high level. Very relevant to what they build.
Onsite round 3: behavioral (45 min): Standard STAR format. Cross-functional collaboration, technical disagreements, a time you had to make a tradeoff under pressure.
HM round (30 min): More of a conversation. She asked about my career goals and whether I wanted to stay individual contributor or move toward tech lead.
Overall impression: they take frontend craft seriously. This isn't "just get the backend working" frontend. If accessibility, performance, and component design are your thing, the vibe is good.