2026 Adobe AI Coding Interview, Experienced Backend Director and LLD Rounds plus Take-Home: 3 Experiences
- Company
- Adobe
- Reports
- 3 interview reports
- Level
- Full-time
- Stages
- OA → Onsite
At Adobe, AI showed up at the end of these two experienced backend loops, not the start: a fifth-round design exercise done with an AI assistant on HackerRank, and a director round where AI was a single step.
Coverage: 2 experienced backend engineers (MTS-2 with 3 years; Computer Scientist 1 with 5.8 years, one round in person in Noida), reports from May and August 2026 · The rounds that involved AI, with the rest of each loop in a line · A separate supplement adds 1 Coderbyte take-home (July 2026) whose role and level aren't stated
What came up
In both experienced reports, AI arrived in the last round of the loop, after the coding and design rounds were done, and both candidates say that round went badly. How much of the round was about AI differed a lot.
| Topic | Reports | Most recent report |
|---|---|---|
| AI in the final round of the loop | 2 of 2 | Aug 26, 2026 (report date) |
| AI as one step inside an ordinary round: improve your own code with Claude | 1 of 2 | Aug 26, 2026 (report date) |
| Running code, with the interviewer expecting a different approach | 1 of 2 | Aug 26, 2026 (report date) |
| Behavioral and project questions in the same round | 1 of 2 | Aug 26, 2026 (report date) |
| Trees, without AI | 1 of 2 | Aug 26, 2026 (report date) |
| A whole round built around AI: a low-level design on HackerRank | 1 of 2 | May 21, 2026 (report date) |
| Judged on AI use, iteration speed, checking the AI's output and completeness | 1 of 2 | May 21, 2026 (report date) |
One report can sit in several rows.
Questions we found
These cover only the rounds where AI came up.
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Reverse the sentences in a file word by word and print them (running code), then hand the code to Claude to optimize | 1 report | Aug 26, 2026 (report date) |
| Design a feature flag service with an AI assistant: rollouts by user or context, app-version targeting, conditional on/off rules | 1 report | May 21, 2026 (report date) |
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Flip a BST (Mirror a Binary Tree) | 1 report | Reports: Aug 26, 2026 (report date); Additional FastPrep history: Dec 11, 2024 |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Why did you use this technology in your project? (practice) | 1 report | Aug 26, 2026 (report date) |
| Tell me about on-call incidents you've handled. (practice) | 1 report | Aug 26, 2026 (report date) |
| What challenges have you faced? | 1 report | Aug 26, 2026 (report date) |
| Tell me about a conflict with your manager. | 1 report | Aug 26, 2026 (report date) |
2 detailed candidate timelines
01: MTS-2 backend, director round: "now give it to Claude"
Report date: Aug 26, 2026 · Role: MTS-2, backend (Java) · Experience: 3 years at a product company · Applied: Careers portal · Result: Rejected the day after the director round
This is the borderline case. AI was one instruction inside a regular director round, not a round designed around it.
Rounds 1–3
- A DSA and Java round on HackerRank, a design and problem-solving round, and a hiring manager round. The candidate felt all three went very well.
Round 4: director
- Project discussion and behavioral questions: why they used a particular technology (practice), challenges they had faced, on-call incidents (practice), and a conflict with a manager. The candidate felt the interviewer wasn't very interested in the answers and was listening for particular keywords.
- Reverse the sentences in a file word by word and print them. The code had to run.
- The candidate wrote an in-place version. The interviewer had a stack-based approach in mind.
- The interviewer then told the candidate to give the code to Claude and optimize it. The report doesn't say what Claude changed or how this step was judged.
- Flip a BST, which reads as mirroring it, close to Mirror a Binary Tree.
The rejection email came the next day. The candidate's own summary: the first three rounds went very well, and the last one didn't.
Round 1 of this loop is written up in Adobe Experienced-Hire First Technical Round, Part 1.
02: Computer Scientist 1 backend, round 5: a feature flag service built with AI
Report date: May 21, 2026 · Role: Computer Scientist 1, backend · Experience: 5.8 years at a large investment bank · Applied: Recruiter reached out · Location: Noida (round 3 in person) · Result: Not reported; the candidate felt rounds 4 and 5 went badly
Rounds 1–4
- Two DSA rounds on HackerRank on the same day, a project deep dive with a high-level design in person, then a hiring manager round with a harder high-level design that didn't go well.
Round 5: AI-driven LLD
- The candidate described this as a new AI-assisted round on HackerRank.
- The task: design a feature flag service. Requirements included rollouts based on the user or context, targeting by app version, and conditional logic for turning features on and off.
- They handled it like any LLD round, laying out entities and classes first and structuring the whole design by hand before involving the AI.
- That wasn't what the interviewer was grading. The evaluation looked at how well the candidate used the AI, how fast they iterated, how they checked what the AI produced, and how complete the solution ended up.
- The round went badly. Looking back, the candidate said they should have brought the AI in much earlier.
Adobe has no feature flag exercise on FastPrep to link here. The earlier rounds of this loop are in Adobe Experienced-Hire First Technical Round, Part 3.
Supplement: hiring level not reported
This candidate didn't give a role or level, so the report sits outside the experienced counts above.
03: A 4–6 hour take-home that Claude finished in 15 minutes
Report date: Jul 12, 2026 · Role and level: Not stated · Stage: Take-home assessment on Coderbyte · Result: Not reported
- The take-home was supposed to take four to six hours.
- The recruiter said the candidate could use the platform's built-in AI assistant, and that Adobe would look at how they used it.
- According to the candidate, Claude completed the whole assessment in about 15 minutes. That left them asking others how Adobe actually evaluates it.
- The task itself wasn't described.
Patterns across the reports
This covers the two experienced reports.
- AI came last, and both candidates say that round went badly. Report 01 met AI in round 4, the director round; report 02 in round 5. Both had been through coding and design rounds first. Report 01 felt everything before the director round went very well; report 02 says round 4 went badly too. Report 01 was rejected the next day, and report 02 didn't share an outcome.
Keep practicing
- Mirror a Binary Tree: the tree question from report 01's director round.
- Why did you choose your project's architecture, and how would it scale? and Tell me about a production issue you faced: Adobe behavioral questions close to two prompts from report 01.
- Adobe behavioral questions: all of Adobe's behavioral practice questions (sign-in needed).
- Adobe low-level design questions: Adobe's object and service design exercises (sign-in needed).
- Adobe Experienced-Hire First Technical Round, Part 1 and Part 3: the first rounds of reports 01 and 02, inside a larger series of experienced-hire first rounds.
- Adobe Intern First Technical Round, Part 1: the intern cohort, covered separately, including a first round with one debugging task done with AI and one without.
- Adobe interview guide: an overview of how Adobe interviews.
- Adobe hiring insights: hiring data for Adobe.
- Interview experiences: the full feed of reports across companies.
AI coding rounds at other companies
- Meta: Meta AI coding interview: two onsite rounds where you finish a hard algorithm inside a mostly written codebase with an AI model, then face stress-test suites.
- Google: Google AI coding interview: an online assessment with HackerRank's built-in assistant, and a live round on a multi-file project where using AI was optional.
- Stripe: Stripe AI coding interview: experienced engineers kept getting the same transaction rule parser, built step by step with a built-in model.
- Stripe interns: Stripe intern AI coding round: ten intern accounts of the same AI-assisted round.
- Rippling: Rippling AI coding interview: HackerRank's built-in AI on Rippling's familiar problems, plus an HR codebase at the onsite.
- DoorDash: DoorDash AI coding interview: AI CodeCraft: build and run several small services live with your own AI tool.
- LinkedIn: LinkedIn AI coding interview: one long, multi-part task in an IDE whose agent edits files directly.
- Shopify: Shopify AI coding interview: pair programming with your own AI on Shopify's well-known question set.
- Datadog: Datadog AI coding interview: bring any AI tool and share your screen; the tasks are easy, and the follow-ups decide the round.
- Capital One: Capital One AI coding interview: new grad Power Day agentic round: fix a bug, then add a feature to a large full-stack app with Claude Code.
- Bloomberg: Bloomberg AI coding interview: intern rounds that start in a small file and move to a large codebase, debugging with AI help.
- xAI: xAI AI coding interview: new grad take-homes and onsites where you build with AI.
- Snowflake: Snowflake AI coding interview: design and build a rate limiter or a retrying task queue while the AI writes the code; one AI Engineer onsite was in person with your own laptop.
- Snap: Snap AI coding interview: a backend-only chat service from an empty Python project with Claude or Codex, or a feature in an existing codebase.
- Ramp: Ramp AI coding interview: build inside a repo Ramp provides; one repo logged every prompt for the interviewer to read.
- Anthropic: Anthropic AI coding interview: review four pull requests, then improve one with Claude Code.
- Apple: Apple AI coding interview: CoderPad with a sidebar agent, alongside Apple's other recent interviews.
More companies with AI rounds on FastPrep:
- Amazon: Amazon interview report: an AI-assisted debugging OA (1 experience).
- Atlassian: Atlassian interview report: project coding and AI tool use (11 experiences, two parts).
- Circle: Circle interview report: three AI rounds: building, debugging and PR review (1 experience).
- Volta: Volta interview report: a deliberately vague data task with a token budget (1 experience).
Across companies: 2026 AI Coding OAs at 15 Companies: 32 Reported Problems and 2025–2026 AI Coding Phone Screens and Onsites at 43 Companies: 76 Reported Problems.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.