Nov 2024–Nov 2026 Adobe Experienced-Hire First Technical Round: 69 Experiences (Part 1 :)
- Company
- Adobe
- Reports
- 6 interview reports
- Level
- Full-time
- Stages
- Phone screen
In this series
- Part 1 (current): 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: 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
The first technical round at Adobe is usually a coding round, but machine learning hires got ML design work instead.
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 01–06 of 69, three machine learning engineers and three software engineers (MTS-2, Computer Scientist 1), India where a place was given, Nov 2026 back to Aug 2026 for the engineers and back to 2025 for ML.
Other Adobe first-round roundups: interns · hiring level not reported
This part has two role sections: machine learning engineers first, then the newest general software engineering reports. That section continues through Part 8.
Machine learning engineers: what came up
All three ML reports put machine learning at the center of round 1. Two were design tasks: a fraud-detection system, and a model that predicts a document's aspect ratio from its image and text.
| Topic | Reports | Most recent report |
|---|---|---|
| Machine learning | 3 of 3 | Nov 7, 2026 (report date) |
| Resume and project deep dive | 1 of 3 | about Aug 2025 |
Machine learning engineers: questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Unnamed easy-to-medium DSA problem (topic only) | 1 report | about Aug 2025 |
Machine Learning
| Question | Frequency | All last seen dates |
|---|---|---|
| Flag Fraudulent Subscription Accounts From Event Logs: design a fraud-detection ML system | 1 report | Nov 7, 2026 (report date) |
| Define a network and write its training loop for multi-label prediction (PyTorch or TensorFlow) | 1 report | Nov 7, 2026 (report date) |
| Predict a Document's Aspect Ratio From Its Images and Text | 1 report | 2025 |
Language and CS Fundamentals
| Question | Frequency | All last seen dates |
|---|---|---|
| Computer vision and AI questions (topic only) | 1 report | about Aug 2025 |
Machine learning engineers: 3 detailed candidate timelines
01: MLE 3 on the Genuine team, fraud-detection design plus PyTorch
Report date: Nov 7, 2026 · Role: Machine Learning Engineer 3 (Adobe Genuine team) · Experience: 2.5 years, plus a PhD in ML · Result: No reply after follow-ups; the application still showed as under review
Round 1: ML system design and PyTorch coding (first technical round)
An outside recruiter reached out, and both technical interviews were set for the next day.
- Design a fraud-detection ML system. The talk covered data collection, feature engineering, outlier detection, class imbalance, model choice, deployment, and online vs offline metrics. No scale, input schema or required algorithm was given.
- Define a neural network and write its training loop for multi-label prediction. The candidate could pick PyTorch or TensorFlow. No dataset was given, so the code wasn't run. The exact labels, loss and layer sizes weren't shared.
After round 1: Round 2 was hands-on ML on an event-level CSV with about 15 features and a fraud label. The interviewer nudged the candidate to build user or account level aggregates. The candidate wanted to drop the account ID because of encoding worries and got stuck. The last 15 minutes covered model choice and metrics.
02: AI/ML engineer, projects first, then a quick coding problem
Interview date: about Aug 2025 (about three months before the Nov 16, 2025 report) · Role: AI/ML Engineer · Location: India · Result: Cleared round 1; rejected after round 2
Before the first technical round: An HR call asked about total experience, current role, notice period and expected pay.
First technical round (about 1 hour)
- A long, detailed talk about the candidate's projects and what they built.
- An easy-to-medium DSA problem. The candidate solved it in about 10 minutes while explaining the logic. The problem itself wasn't named.
- Computer vision and AI questions; the exact questions weren't shared.
HR confirmed the same day that the candidate had cleared the round.
After round 1: The second, more advanced round had a scenario-based problem where the candidate needed hints, plus one simple DSA question. They didn't clear it and were told about a six-month wait before reapplying.
03: MLE II, predicting a document's aspect ratio
Interview date: 2025 (report date Oct 12, 2025) · Role: Machine Learning Engineer II · Experience: 3+ years as a data scientist and MLE · Result: Offer, accepted
Round 1 (first technical round)
- End-to-end ML design for documents that have both image and text data: propose a full pipeline that predicts a document's aspect ratio.
This was the only question reported for the round.
After round 1: Round 2 had one Python coding question and a deep dive on LLMs, transformers and attention. Round 3 was managerial (projects, teamwork, behavioral). The hiring manager round asked for a design of a color suggestion system. The candidate was selected and accepted.
Software engineers: what came up
Cache work came up in two of these three rounds: an LFU cache with running code, and an open-ended cache design. Two rounds also spent real time on the resume.
| Topic | Reports | Most recent report |
|---|---|---|
| Trees | 1 of 3 | Sep 5, 2026 (report date) |
| Dynamic programming | 1 of 3 | Sep 5, 2026 (report date) |
| Arrays and strings | 1 of 3 | Sep 5, 2026 (report date) |
| LRU/LFU cache design | 2 of 3 | Aug 26, 2026 (report date) |
| Resume and project deep dive | 2 of 3 | Aug 26, 2026 (report date) |
| Intervals | 1 of 3 | Aug 26, 2026 (report date) |
| OS, DBMS and networking basics | 1 of 3 | Aug 26, 2026 (report date) |
| SQL and databases | 1 of 3 | Aug 26, 2026 (report date) |
| Java | 1 of 3 | Aug 26, 2026 (report date) |
Software engineers: questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Unnamed hard tree dynamic programming problem (topic only) | 1 report | Sep 5, 2026 (report date) |
| Unnamed hard matrix problem (topic only) | 1 report | Sep 5, 2026 (report date) |
| Merge Overlapping Intervals (LC 56) | 1 report | Reports: Aug 26, 2026 (report date); Additional FastPrep history: Jul 14, 2025 |
| Least Frequently Used Cache Simulator (LC 460) | 1 report | Reports: Aug 26, 2026 (report date); Additional FastPrep history: Jul 18, 2025 |
Low-Level Design (LLD/OOD)
| Question | Frequency | All last seen dates |
|---|---|---|
| Design a cache (no other requirements given) | 1 report | Aug 13, 2026 |
Language and CS Fundamentals
| Question | Frequency | All last seen dates |
|---|---|---|
| OOP pillars, one SQL query, caching and database basics | 1 report | Aug 26, 2026 (report date) |
Software engineers: 3 detailed candidate timelines
04: MTS-2 in Noida: two hard problems in one round
Report date: Sep 5, 2026 · Role: MTS-2 · Experience: 2+ years · Location: Noida, India · Result: Passed round 1, rejected after round 2
Round 1: DSA (first technical round)
- Two questions, both described by the candidate as hard. The exact prompts weren't shared.
- The first was a dynamic programming problem on a tree. Their code passed about 60–70% of the test cases.
- The second was a matrix problem. Only 10 minutes were left for it. The interviewer accepted the approach the candidate explained, but the code didn't compile and time ran out before a fix.
- The recruiter still moved them to the next round.
After round 1: Round 2 came two days later and was a low-level design of a food-court system, with extra constraints added during the interview. It was the candidate's first LLD interview. The interviewer was helpful, but the candidate felt nervous, made weak design choices, and was rejected.
05: MTS-2 Java backend: merge intervals and LFU cache on HackerRank
Report date: Aug 26, 2026 · Role: MTS-2, backend (Java) · Experience: 3 years · Result: Rejected after the director round
Round 1: DSA + Java (first technical round)
- The round ran on HackerRank. Code had to run against 6–8 custom test cases.
- Merge overlapping intervals (LC 56).
- Implement an LFU cache (LC 460), again with working code on custom tests.
- A deep dive into one point on the resume.
- Short discussion questions: OOP and its main pillars, one SQL query, caching, and databases.
The candidate felt this round went well and moved on.
After round 1: Round 2 asked for a sliding-window rate limiter, all subsequences of a string in sorted order, and Java locking. Round 3 (hiring manager) covered projects, the HLD of the current project and a URL shortener. In the director round, the candidate reversed the sentences in a file word by word with running code, then fed it to an AI tool to optimize; the interviewer wanted a stack-based version. A mirror-a-BST question followed. They were rejected the next day.
06: CS-1 hiring drive in Bangalore: resume talk and an open cache design
Interview date: Aug 13, 2026 · Role: Computer Scientist 1 · Location: Bangalore, India · Result: Positive feedback on three rounds, then put on hold by a hiring freeze
Round 1 (first technical round, at a hiring drive)
- A discussion based on the resume.
- Design a cache. No further requirements were reported.
The recruiter said the feedback from this round was positive.
After round 1: Round 2 had Asteroid Collision (LC 735), one SQL question, and system design ideas including idempotency. Round 3 was resume and behavioral. A director round asked a sales-related system design, which the candidate answered about halfway. The process then paused for a hiring freeze.
Keep practicing
- Flag Fraudulent Subscription Accounts From Event Logs: ML modeling question from report 01.
- Predict a Document's Aspect Ratio From Its Images and Text: ML modeling question from report 03.
- Least Frequently Used Cache Simulator: practice problem from report 05.
- Merge Overlapping Intervals: practice problem from report 05.
- Mirror a Binary Tree: practice problem from report 05.
- Asteroid Collision: practice problem from report 06.
- Adobe coding questions: the company-filtered question bank (sign-in needed).
- Adobe low-level design questions: the company-filtered question bank (sign-in needed).
- Adobe ML modeling 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.