Nov 2024–Nov 2026 Adobe Experienced-Hire First Technical Round: 69 Experiences (Part 11 :)
- Company
- Adobe
- Reports
- 7 interview reports
- Level
- Full-time
- Stages
- Phone screen
In this series
- Part 1: Machine learning engineers (01–03), then software engineers from Sep–Aug 2026 (04–06)
- Part 2: Software engineers, Aug–Jun 2026 (07–11)
- Part 3: Software engineers, May 2026–Nov 2025 (12–18)
- Part 4: Software engineers, Nov 2025–Jun 2025 (19–25)
- Part 5: Software engineers, Jun–Apr 2025 (26–31)
- Part 6: Software engineers, Apr–Feb 2025 plus year-only 2025 reports (32–37)
- Part 7: Software engineers, 2025 and Dec–Nov 2024 (38–43)
- Part 8: Last software engineers (44–45), then C++ engineers, Sep 2026–Sep 2025 (46–49)
- Part 9: C++ engineers, Aug–Apr 2025 (50–54)
- Part 10: Android engineers (55–57) and the newest frontend report (58)
- Part 11 (current): Frontend engineers, May 2026–Apr 2025 (59–65)
- Part 12: Last frontend reports (66–67), release engineering (68), product consultant (69), and patterns across all 69
Seven frontend rounds from May 2026 back to Apr 2025, from an eight-minute HTML task to a React app built test-first.
Coverage: Experienced hires at Adobe, first live technical round only (the first coding or technical interview after any online test or recruiter call). Later rounds get a short note at the end of each timeline. This part: reports 59–65 of 69, frontend engineers (Computer Scientist 1 and 2, Senior Computer Scientist, SDE-3, and a Principal Software Engineer whose first screen was front end), India and the U.S., May 2026–Apr 2025.
Other Adobe first-round roundups: interns · hiring level not reported
What came up
JavaScript or TypeScript questions came up in four of these seven rounds. Two rounds were about HTML and CSS layout, and two involved React.
| Topic | Reports | Most recent report |
|---|---|---|
| JavaScript and TypeScript | 4 of 7 | May 7, 2026 (report date) |
| Sorting and binary search | 1 of 7 | May 7, 2026 (report date) |
| HTML and CSS | 2 of 7 | about May 2026 |
| Resume and project deep dive | 1 of 7 | May 2026 |
| React | 2 of 7 | Sep 26, 2025 |
| Trees | 1 of 7 | May 12, 2025 (report date) |
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Unnamed binary search problem (topic only) | 1 report | May 7, 2026 (report date) |
| Biggest Number From Gluing Numbers Together (LC 179) | 1 report | May 7, 2026 (report date) |
| Unnamed two-part DSA problem (topic only) | 1 report | about May 2026 |
| Pick the set of trades that gives the minimum value (few details) | 1 report | May 2026 |
| Binary Tree Level-Order Traversal by Levels (with an undisclosed twist) | 1 report | Reports: May 12, 2025 (report date); Additional FastPrep history: Aug 16, 2026 |
Frontend / UI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build a CSS layout with flexbox (layout not shared) | 1 report | about May 2026 |
| Build a small React app with test-driven development | 1 report | Sep 26, 2025 |
| Debounced Call Times (write a debounce function) | 1 report | Jul 9, 2025 (report date) |
| Flatten a Nested Object Into Dot Keys | 1 report | Jul 9, 2025 (report date) |
Compose async functions with chaining (composeAsync) |
1 report | Jul 9, 2025 (report date) |
Polyfill for Array.prototype.reduce |
1 report | May 12, 2025 (report date) |
| Recreate a simple figure in plain HTML and CSS | 1 report | Apr 20, 2025 (report date) |
Language and CS Fundamentals
| Question | Frequency | All last seen dates |
|---|---|---|
| JavaScript questions, including try/catch (topic only) | 1 report | May 7, 2026 (report date) |
| TypeScript type predicates | 1 report | May 2026 |
| Nx monorepo tooling and current projects | 1 report | May 2026 |
| Basic front-end concepts (topic only) | 1 report | Sep 26, 2025 |
JavaScript core: closures, the event loop and this binding |
1 report | Jul 9, 2025 (report date) |
| Memory leaks in large React apps, garbage collection, retrying flaky APIs | 1 report | Jul 9, 2025 (report date) |
| UI stack trade-offs, performance work and in-depth JavaScript (topic only) | 1 report | May 12, 2025 (report date) |
7 detailed candidate timelines, loops, and screens
59: CS-1 frontend: largest number and JavaScript basics
Report date: May 7, 2026 · Role: Computer Scientist 1, frontend · Experience: 4 years · Result: Rejected after the final round
Round 1: JavaScript code and fundamentals (first technical round)
- A binary search question. The candidate didn't describe it.
- Arrange numbers so their concatenation forms the largest number (LC 179).
- JavaScript questions, including how try/catch behaves. No more detail was given.
- They cleared the round.
After round 1: Round 2 asked for all permutations of an array, plus debounce and throttle. The hiring manager round discussed past work and how to split a React single-page app by route. The director round went deep on UI performance, service workers and a backend-for-frontend layer, and ended in a rejection.
60: Computer Scientist frontend: a flexbox layout and a two-part problem
Interview date: about May 2026 (about six months before the Nov 2, 2026 report) · Role: Computer Scientist, frontend (referred) · Result: Rejected after this round
Initial round: DSA and JavaScript (first technical round)
- A very senior Computer Scientist ran it.
- A CSS layout to build with flexbox and related properties. The exact layout wasn't shared. The candidate hadn't expected CSS in this round and struggled with it.
- An unusual DSA problem with two levels to clear. The problem itself wasn't described. The interviewer gave hints, and the candidate needed them.
- The hints felt encouraging, but a rejection came after this round.
61: Senior CS frontend on a drive day: trades, type predicates, Nx
Interview date: May 2026 · Role: Senior Computer Scientist, frontend · Experience: 10 years · Location: Bengaluru, India
Round 1: Data structures, algorithms and coding basics (first technical round)
- This was a hiring-drive day with two rounds back to back. A request to reschedule was turned down.
- The candidate listed the questions without tying each one to a round, so these are probably from this round. The coding question: find the set of trades that gives the minimum value. No more detail was given.
- A question on TypeScript type predicates.
- Questions on Nx, the monorepo tool, and on current projects.
- The interviewer was patient and the questions felt relevant. The candidate thought it went well.
After round 1: Round 2 was billed as a frontend round but turned into system design: a real-time collaborative text editor that shifted into a collaborative drawing tool, with dropped items coming back into scope. The candidate found the expectations unclear. No result was reported.
62: Principal engineer: a front-end screen with React and TDD
Interview date: Sep 26, 2025 · Role: Principal Software Engineer (the first screen was front end) · Location: United States · Result: No offer
Initial screening: front end (first technical round)
- Basic front-end concepts. No specific questions were shared.
- Build a small React application using test-driven development.
- After the screen the candidate heard nothing back and got no feedback.
63: CS-1 frontend, offered MTS-2: debounce, flatten, async compose
Report date: Jul 9, 2025 · Role: Interviewed for Computer Scientist 1 (frontend); offered MTS-2 · Experience: 2 years 10 months · Result: Offer at MTS-2, accepted
Round 1: JavaScript fundamentals (first technical round)
- Core JavaScript: closures, the event loop, async behavior and how
thisgets bound. - Write a debounce function.
- Flatten a deeply nested object into dot-separated keys.
- Write
composeAsync, which chains async functions together. - Memory leaks in large React apps, garbage collection, and how to retry calls to a flaky API.
- Feedback was positive.
After round 1: Round 2 was a React build: a nested comment section with replies, likes, auto-saved drafts and keyboard access, then an infinite-scroll hook with cursor paging and memoization questions. Round 3 designed a content dashboard with live updates and access control. The manager round asked for search in a sorted 2D matrix and grid paths with at most one obstacle removed. The director round had reversing a linked list in groups of k and a spoken palindrome-partitioning question. The candidate was offered MTS-2 and accepted.
64: CS-2 frontend: level order with a twist and a reduce polyfill
Report date: May 12, 2025 · Role: Computer Scientist 2, frontend · Experience: 8+ years · Location: Bengaluru, India · Result: Not selected
R1: Coding (first technical round)
- Binary tree level-order traversal, grouped by level, with a twist the candidate didn't describe.
- Write a polyfill for
Array.prototype.reduce. - A deep dive into their UI stack and its trade-offs, how they improved performance, and in-depth JavaScript questions.
- Feedback for this round was positive.
After round 1: Round 2 asked them to move heavy input calculations into a Web Worker so a clock on the page wouldn't freeze, plus promises versus async/await and list virtualization. Round 3 was a design-and-code round for multiplayer Snakes and Ladders. The candidate felt rounds 2 and 3 went badly and was not selected.
65: SDE-3 frontend: an eight-minute HTML and CSS round
Report date: Apr 20, 2025 · Role: SDE-3, frontend (the candidate's label; the Adobe title wasn't given) · Experience: 4+ years · Location: Noida, India · Result: Rejected after all rounds
Before the first technical round: A recruiter reached out by email.
Round 1: HTML and CSS (first technical round)
- The rounds were virtual and back to back on the same day.
- Recreate a simple figure using only HTML and CSS. The candidate finished fast; the round took about 8 minutes.
After round 1: The DSA round asked for a stack that can delete an element at any position in O(1); a doubly linked list solved it in time. The managerial round covered the resume and the puzzle of finding the 3 fastest horses with a limited number of race tracks. The candidate was rejected.
Keep practicing
- Biggest Number From Gluing Numbers Together: practice problem from report 59.
- Debounced Call Times: practice problem from report 63.
- Flatten a Nested Object Into Dot Keys: practice problem from report 63.
- Binary Tree Level-Order Traversal by Levels: practice problem from report 64.
- Adobe coding questions: the company-filtered question bank (sign-in needed).
- Adobe interview guide: Adobe's interview overview page on FastPrep.
- Adobe hiring insights: hiring activity and trends for Adobe.
- Experience feed: more interview experiences and roundups.
Other Adobe first-round roundups: interns · hiring level not reported
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.