Company guides
🟥 Adobe — Frontend Interview Guide
Emphasis: Complex, stateful UIs — editors, canvas, tools. Strong JS fundamentals and performance for rich interactive apps.
Related: Company index · ROADMAP
The loop (typical)
| Round | Focus | Prep section |
|---|---|---|
| Phone screen | JS/DSA | 03-javascript |
| Coding | UI component | 16-machine-coding |
| Frontend system design | Editor/tool "Design X" | 15-system-design |
| Behavioral | Collaboration | — |
What they emphasize
- Complex state — editors, undo/redo, tools, selection.
- Canvas / graphics — rendering, transforms, performance.
- JS depth — closures, prototypes, event handling.
- Performance for heavy interactive UIs.
Frequently asked (community-sourced)
Machine coding
- Build a Whiteboard / drawing canvas → 16-machine-coding
- Build an Image crop/zoom tool → 16-machine-coding
- Build undo/redo (command pattern) → design patterns
- Build a color picker → 16-machine-coding
System design
- Design a Rich Text Editor / Figma-like tool → 15-system-design
- Design Google Docs (collaboration) → flagship
JS
- Prototypes,
this, closures → 03-javascript - Event Bus / Observer → flagship
Prep plan (2 weeks)
- Build a canvas-based tool (draw/select/transform).
- Implement undo/redo with the command pattern.
- Review JS internals deeply.
- Study a collaborative-editor design.
🟢 Green flags · 🔴 Red flags
🟢 Do: model complex editor state cleanly · implement undo/redo · keep canvas/transform work performant · show deep JS fundamentals. 🔴 Avoid: shallow state modeling · ignoring performance on heavy canvases · weak grasp of closures/prototypes/events.
📝 Sample interviewer prompts
- "Build a drawing canvas with undo/redo."
- "How would you model selection and transforms in an editor?"
- "Implement an event bus for tools to communicate."
Interviewed at Adobe? Add the questions you got (role + year) via a PR.