A senior frontend engineer documented a 4-round interview process at Adobe for a Computer Scientist 1 (Frontend) role on the Adobe Express team. The loop covered DSA, React machine coding, a managerial design discussion, and a Director-level system design + culture round. The candidate was selected. Specific questions are not disclosed due to an NDA with Adobe.
Medium
A focused live coding round on classical algorithms and data structures.
What was tested:
Bar at senior level: Solving the problem is the minimum. The expectation is stating the approach upfront, discussing time/space complexity, identifying trade-offs, and refactoring cleanly when the problem evolves.
Topics covered: BFS, DFS, Dijkstra-style graph traversal, prefix sums, array grouping techniques.
Tip: Don't just grind one problem type. Pattern recognition across categories — knowing "this is a graph problem" within 30 seconds of reading the prompt — is the actual skill being tested.
Hard
A live coding round in React with a JavaScript fundamentals conversation woven throughout.
What was tested:
Senior bar expectations:
Notable moment: The interviewer referenced a React Nexus talk the candidate had given — they had looked it up beforehand. The conversation briefly became a peer discussion between engineers. Public work (talks, open source, writing) directly influenced the interview dynamic.
Tip: Build things in public. Talks, open source contributions, and writing are visible to interviewers and can change the texture of a round from evaluation to conversation.
Medium
A conversational round with an Engineering Manager, mixing career discussion with open-ended technical design thinking.
What was tested:
Senior bar: Having opinions backed by real experience, not stubbornness. The AI conversation specifically tested judgment — whether the candidate had thought carefully about AI tooling in practice.
Tip: Before any senior frontend interview in 2025+, have a thoughtful, nuanced position on AI in your workflow. "I use Copilot" is not an answer. "Here's where I've found it helps and here's where I've learned to distrust it" is.
Hard · Longest round in the loop
A combined system design and culture conversation with a Director-level interviewer.
System design structure: The candidate used the RADIO framework:
The design discussion went deep on:
AI in engineering: The Director's questions on AI were not theoretical — they focused on how the candidate would plan, debug, and execute differently with AI tools in an actual engineering context.
Culture component: Questions were not scripted or catchable by preparation. They asked the candidate to honestly examine their own working style, growth patterns, and blind spots. The candidate describes this as the most memorable part of the loop.
What the Director was assessing: Would this person be valuable in real design reviews? Do they push thinking forward without ego? Can they hold a 90-minute design conversation, take pushback gracefully, and still be energised at the end?
Tip: The RADIO framework (Requirements → API → Data model → Implementation → Optimisations) is publicly documented and worth internalising for any senior frontend system design round.
The candidate was selected for the Adobe Express team. Difficulty: 4/5. The loop was described as intentional and human — each round had a clear purpose, every interviewer was engaged, and the process felt respectful throughout. The personal moment in Round 2 (the interviewer referencing a public talk) was highlighted as evidence that public work pays off. The candidate strongly recommends Adobe for engineers who want a challenging but thoughtful process that feels like a genuine assessment of craft, not a filter-by-attrition marathon.
This experience was originally published on Medium. Support the author by visiting the original post.
Read on Medium