Adobe Frontend and QA Interviews: 14 Experiences (Part 6 of 6)
- Company
- Adobe
- Level
- Full-time
- Stages
- Phone screen
Three 2023-24 Adobe frontend and test-automation first rounds all included data-structure coding; only one also asked JavaScript and React questions.
At a glance
- Process: FE 01 met JavaScript, React and DSA in round one; FE 02 had DSA only, with JavaScript and React in round three the next day. Both had two to four more rounds. The test-automation candidate had a coding round, then a testing round (QA 01). FE 01 got an offer; FE 02 and QA 01 did not.
- Asked in these reports: an event-loop scenario plus two unnamed DSA problems (FE 01), linked lists and hash maps (FE 02), the n-stairs problem (QA 01).
- Difficulty: FE 01 called its two first-round problems medium and easy-medium, and its React build medium; FE 02 and QA 01 gave no rating.
- Practise first: Ways to Climb n Stairs (QA 01).
Coverage: 14 experienced candidates outside general software engineering: five frontend, six quality and test, one build and release, two managers, in India where a place is given, plus one in California. Three are current (Dec 2023 to Sep 2024); 11 from 2022 to Sep 2023 sit in History.
In this series
- Part 1: overview and question tables
- Part 2: MTS-1 and MTS-2
- Part 3: SDE and senior software engineers
- Part 4: Computer Scientist 1
- Part 5: CS2 and senior Computer Scientist
- Part 6 (current): frontend, quality, release and manager roles
Roles in this part: frontend engineers (FE 01–02, FE H01–H03) · quality and test engineers (QA 01, QA H01–H05) · build and release (RE H01) · engineering managers (EM H01–H02).
Frontend engineers
What came up
Both current frontend first rounds included DSA: FE 02's was DSA only (linked lists and hash maps), and FE 01's added two unnamed tree and array problems after JavaScript and React questions.
Questions we found
Coding
| Question | Reports | Last seen |
|---|---|---|
| A tree's bottom view | 1: FE 01 | Sep 2024 (report date) |
| "Aggressive cows" binary search | 1: FE 01 | Sep 2024 (report date) |
| First n Fibonacci terms without storing them | 1: FE 01 | Sep 2024 (report date) |
Design and performance
| Question | Reports | Last seen |
|---|---|---|
| Cache invalidation in your project | 1: FE 01 | Sep 2024 (report date) |
| How your project reaches millions of users | 1: FE 01 | Sep 2024 (report date) |
| Frontend optimisations your project uses | 1: FE 01 | Sep 2024 (report date) |
| A high-level design of your own project | 1: FE 01 | Sep 2024 (report date) |
UI and JavaScript builds
| Question | Reports | Last seen |
|---|---|---|
| A medium React build | 1: FE 01 | Sep 2024 (report date) |
| A lodash helper written by hand | 1: FE 01 | Sep 2024 (report date) |
JavaScript and React concepts
| Question | Reports | Last seen |
|---|---|---|
| An event-loop scenario | 1: FE 01 | Sep 2024 (report date) |
| Closures | 1: FE 01 | Sep 2024 (report date) |
| React fundamentals | 1: FE 01 | Sep 2024 (report date) |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| A project you are proud of, and why | 1: FE 01 | Sep 2024 (report date) |
| Walk through your current project | 1: FE 01 | Sep 2024 (report date) |
| Why leave your current job (practice) | 1: FE 02 | May 2024 |
Puzzles
| Question | Reports | Last seen |
|---|---|---|
| Painted 4x4x4 cube | 1: FE 01 | Sep 2024 (report date) |
2 detailed candidate timelines, loops, and screens
FE 01: event-loop questions, then four more rounds
Report date: Sep 2024 · Role: MTS 2, frontend · Result: Offer
Round 1: JavaScript, then two data-structure problems
- The interviewer described a scenario and asked the candidate to explain what the event loop would do.
- Closures and React basics.
- Two coding problems, not named: a medium tree problem and an easy-to-medium array task.
Later rounds
- How the candidate's project handles cache invalidation, how it reaches millions of users each day (from release until it runs on a user's device), the frontend optimisations it uses, and another medium tree problem.
- Hiring manager: explain a project you are proud of and why; code a tree's bottom view with no library help, then a binary search in the style of "aggressive cows".
- Senior hiring manager: the current project, a medium React build, a puzzle about a 4x4x4 painted cube cut into small cubes (how many have three painted faces), and a tree problem.
- Design: the proud-project question again, with a high-level view of that project; one lodash helper written by hand; printing the first n Fibonacci terms without holding the sequence in memory.
FE 02: a DSA-only first round for a frontend job
Interview date: May 2024 · Role: Frontend Software Engineer · Location: Noida · Result: No offer
- Round 1 was only data structures: questions on linked lists and hash maps. The candidate's topic list also names queues and trees.
- Round 2, the same day, mixed more coding with why the candidate wanted to leave their job; round 3, the next day, covered JavaScript and React.
History (before Nov 2023)
FE H01: a pure JavaScript round with polyfills
Interview date: Dec 2022 · Role: CS-1, frontend (7+ years) · Location: Noida · Result: Offer
- Recruiter call (about 20 minutes): the role, the process and why Adobe.
- Round 1 (about 70 minutes, no DSA): HTML5, CSS3 and ES5, async versus defer, how a page renders; output questions on hoisting, deep cloning, composition and currying; polyfills for Promise.allSettled and Array.prototype.map. The interviewer helped when the candidate got stuck.
- Round 2 (about 80 minutes): a method-chaining class, a pub-sub class with unsubscribe, a DP problem based on LeetCode 122 (Best Time to Buy and Sell Stock II), and two-sum without extra space.
- Later: a game app's UI with performance and i18n; with the hiring manager, the current role, behavioral questions and a UI widget in plain JavaScript.
FE H02: closures, a form and Jump Game
Report date: Nov 2022 · Role: Front end developer · Result: Rejected after round 2
- Round 1: a closure output question (missed); call, apply and bind with a bind polyfill; centring in CSS and accessibility; the single sign-on flow from the resume; a React form with validation; LeetCode 55 (Can You Jump to the Last Index).
- Round 2: LeetCode 46 permutations and an infinite-scroll feed.
FE H03: version strings on a phone screen
Interview date: 2022 (report date Feb 2022) · Role: UI engineer screen, then a backend opening (10+ years) · Location: California · Result: Rejected
- After a recruiter call on the process, a phone screen with a UI engineer: React questions and LeetCode 165 (Compare Two Version Strings).
- A second screen, for a backend role, covered AWS Lambda, JavaScript, object-oriented design patterns and REST APIs, with no DSA or behavioral questions.
Quality and test engineers
What came up
The one current report paired the n-stairs problem with an unexplained "spiral" linked-list check, then moved to test design (QA 01).
Questions we found
Coding
| Question | Reports | Last seen |
|---|---|---|
| Ways to Climb n Stairs | 1: QA 01 | Dec 2023 |
| Is a linked list a "spiral" | 1: QA 01 | Dec 2023 |
Testing
| Question | Reports | Last seen |
|---|---|---|
| Write test scenarios, then cases for one | 1: QA 01 | Dec 2023 |
1 detailed candidate timeline
QA 01: stairs and an unclear list question
Interview date: Dec 2023 · Role: Senior Test Automation Engineer · Location: India · Result: No offer
- Round 1: the n-stairs problem (Ways to Climb n Stairs), and how to check whether a linked list is a "spiral" (the term was not explained).
- Round 2: write test scenarios, then cases for one scenario the interviewer set.
History (before Nov 2023)
QA H01: a framework deep dive and Decode String
Report date: Nov 2022 · Role: CS1, SDET (5 years 4 months) · Location: Bengaluru · Result: Offer
- Round 1: the frontend and backend test frameworks the candidate had built, and how to write one in Python from nothing; then LeetCode 394 (Expand an Encoded String) with a stack, plus test cases. Some edge cases did not pass, and the interviewer accepted that.
- Later: indexes and B-trees, a medium SQL query and a test framework for a book-reading service; Python, CI/CD with Jenkins, test metrics, reading a large file line by line and an easy binary-tree task; past projects and an API framework, talked through with the manager.
QA H02: camelCase and a BST successor
Interview date: Apr 2022 · Role: Senior Quality Engineer · Location: Noida · Result: No offer
- One hour of coding: Convert Text to camelCase and the next larger node in a BST (Next Larger Node in a BST).
QA H03: two puzzles and two string checks
Interview date: Apr 2022 · Role: Senior QA Automation Engineer · Location: Hyderabad · Result: No offer
- Round 1: measure 30 minutes with a rope that burns in 60; relabel three wrongly labelled fruit boxes after one draw; count repeated characters in a string; tell even from odd without division; Selenium, tiered architecture and RDBMS basics.
- Round 2 focused on TestNG; the rejection came after it.
QA H04: three easy-to-medium problems for a lead role
Interview date: Mar 2022 · Role: Lead SDET · Location: Bengaluru · Result: Offer accepted
- After an HR call, a screening round of three easy-to-medium LeetCode-style problems in any language, judged on approach and optimisation. The problems are not named; the candidate suggested reviewing strings, regular expressions and maths such as square roots, powers, GCD and LCM. Then a senior QE round on frameworks and build quality, and a manager round on expectations and goals.
QA H05: linked lists and strings for a mobile tester
Report date: Mar 2022 · Role: Software Quality Engineer, Document Cloud mobile · Result: Offer
- Round 1: Java questions, a linked-list problem (solved with help) and a string problem, then SQL and a puzzle. Three more rounds repeated Java and coding, ending with writing test cases.
Build and release
History (before Nov 2023)
RE H01: a build and release round with no DSA
Report date: Sep 2023 · Role: build and release engineer, interviewed under a CS-1 title (5+ years) · Result: No reply after round 2
- Round 1 with a senior manager: a Jenkins pipeline in Groovy, Dockerfiles and Docker commands, Splunk, CRUD endpoints and REST versus SOAP, AWS and DynamoDB. The candidate found the interviewer rude.
- Round 2: the clock-hand angle in code, the eight-balls puzzle, DDoS, Git, rate limiting, SQL versus NoSQL, the k-th largest value, daemon threads, and how to trigger a CI build on each commit.
Engineering managers
History (before Nov 2023)
EM H01: three string and array checks for a manager
Interview date: Jun 2022 · Role: Technical Manager · Location: India · Result: No offer
- Is the String a Palindrome, duplicates in an array (Values That Appear Twice), every unique substring (Every Distinct Substring in Order), and applying a strikethrough CSS class in a live example.
EM H02: Remove K Digits on a camera-off call
Interview date: Jan 2022 · Role: Engineering Manager · Location: India · Result: No offer
- Round 1 on video, with the interviewer's camera off: LeetCode 402 (Smallest Number After Removing k Digits) and an unnamed binary tree problem.
Keep practicing
- Why do you want to leave your current company?: behavioral question, FE 02.
- Why do you want to work at Adobe?: behavioral question, FE H01.
- Can You Jump to the Last Index: FE H02.
- Compare Two Version Strings: FE H03.
- Ways to Climb n Stairs: QA 01.
- Expand an Encoded String: QA H01.
- Convert Text to camelCase: QA H02.
- Next Larger Node in a BST: QA H02.
- Count Repeated Characters in a String: QA H03.
- Even or Odd Without Division: QA H03.
- K-th Largest Value in an Array: RE H01.
- Is the String a Palindrome: EM H01.
- Values That Appear Twice: EM H01.
- Every Distinct Substring in Order: EM H01.
- Smallest Number After Removing k Digits: EM H02.
- Adobe coding questions: all of Adobe's coding problems (sign-in needed).
- Adobe behavioral questions: Adobe's behavioral questions (sign-in needed).
- Adobe system design questions: Adobe's system design cases (sign-in needed).
- Adobe interview guide: the company's interview overview.
- Adobe hiring insights: hiring activity over time.
- Experience feed: more interview reports and roundups.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.