Adobe Round 1 Interviews, Level Not Reported: 11 Experiences

Shared by janebeingjane ·
Company
Adobe
Reports
11 interview reports
Level
Unknown
Stages
Phone screen

Adobe round 1 reports from 11 candidates who didn't give a hiring level (2024–2026): test engineers on Selenium, SDEs with two or three problems, and more.

At a glance

  • Process: a test or call often came first: a HackerRank test (01, 10), a written test (02), a recruiter or hiring-manager call (03, 05, 06). The first live round then ran about an hour where stated (03, 04, 08, 10).
  • Asked recently: Selenium and test automation in both test-engineer rounds (02, 03); two or three coding problems in both SDE rounds (04, 05); named problems were Third-Highest Known Salary (02), All Rearrangements of a String (03), Timed Message Batches (06) and Fewest Jumps to the End or Stuck (09).
  • Difficulty: candidate 04 had an easy, a medium and a hard problem; 05 felt short of time; 08 was asked for the optimal answer straight away. Two reported offers (01, 02), and 02 declined.
  • Practise first: the four linked problems above.

Coverage: 11 reports from Nov 2024 to Jul 2026 whose hiring level wasn't stated, so they stay out of the intern, new-grad and experienced roundups: a technical product consultant (01), test engineers (02, 03), software engineers (04–06), an ML engineer (07), two with no role given (08, 09), a junior frontend developer (10) and a Python developer (11), in India, the U.S. and Romania. First live technical round only. Other Adobe roundups: experienced hires, round 1 · interns, round 1 · level not reported before Nov 2024, every round.

Each role has its own section, ordered by its newest report.

Technical product consultant: what came up

The one consultant report had four short coding tasks, named only by area (strings, dictionaries, a diamond star pattern and OOP), plus resume questions.

Technical product consultant: questions we found

Algorithms / Data Structures

Question Reports Last seen
Print a diamond star pattern (size and format not shared) 1: 01 Jul 2026 (report date)

Technical product consultant: 1 detailed candidate timeline

01: Campus technical product consultant: four short coding tasks

Report date: Jul 17, 2026 · Role: Technical Product Consultant (campus hiring) · Location: Noida, India · Result: Selected

Before the first technical round: A HackerRank test with three coding questions, plus aptitude, reasoning and some SQL.

Technical interview 1 (first technical round)

  1. Four coding items, described only by area: strings, dictionaries, printing a diamond star pattern, and object-oriented programming. The exact prompts weren't shared.
  2. Questions about the resume.

After round 1: A technical-cum-managerial round asked technical and basic logic questions about the resume. The candidate was selected and was weighing the offer.


Test engineers: what came up

Both test-engineering rounds were mostly test automation with Selenium. The newer one added a SQL query; the older one added a string-permutations task.

Topic Reports Last seen
Test automation 2 of 2 Sep 2025
SQL and databases 1 of 2 Sep 2025
Build, CI/CD and cloud tools 1 of 2 Sep 2025
OS, DBMS and networking basics 1 of 2 Sep 2025
Java 1 of 2 Nov 2024 (report date)
Backtracking and recursion 1 of 2 Nov 2024 (report date)
Puzzles and probability 1 of 2 Nov 2024 (report date)

Test engineers: questions we found

Algorithms / Data Structures

Question Reports Last seen
All Rearrangements of a String 1: 03 Nov 2024 (report date)

SQL

Question Reports Last seen
Third-Highest Known Salary 1: 02 Sep 2025

Language and CS Fundamentals

Question Reports Last seen
HTTP status codes 1: 02 Sep 2025
Java functional interfaces and threading 1: 03 Nov 2024 (report date)

Test Automation

Question Reports Last seen
Selenium implicit vs explicit vs fluent waits 1: 02 Sep 2025
XPath using both id and class 1: 02 Sep 2025
Test annotations (@Suite, @Group, @Test, @Class) 1: 02 Sep 2025
Selenium window handles and frames 1: 02 Sep 2025
XPath using siblings 1: 02 Sep 2025
Running tests in parallel 1: 02 Sep 2025
XPath matching "abc" or "ABC" with translate() 1: 02 Sep 2025
Selenium framework: attach to an open browser, multiple windows, dynamic dropdowns, shadow DOM 1: 03 Nov 2024 (report date)
Extract every salary value from a chart on a page 1: 03 Nov 2024 (report date)

DevOps and Cloud

Question Reports Last seen
Git fetch vs pull; Jenkins 1: 02 Sep 2025
Fixing Git merge problems with reset 1: 02 Sep 2025

Test engineers: 2 detailed candidate timelines

02: Software test engineer: Selenium waits, XPath and a SQL query

Interview date: Sep 21, 2025 · Role: Software Test Engineer · Location: Noida, India · Result: Offer, declined

Before the first technical round: A written test.

1st round (first technical round)

  1. Selenium: implicit, explicit and fluent waits, and how to handle window handles and frames.
  2. XPath: one using both id and class, one using siblings, and one that matches "abc" or "ABC" with translate().
  3. Test annotations such as @Suite, @Group, @Test and @Class, and running tests in parallel.
  4. Git fetch versus pull, fixing merge problems with reset, and Jenkins.
  5. A SQL query for the third-highest salary.
  6. HTTP status codes.

After round 1: Two more technical rounds followed, one face to face in the office, with technical, behavioral and reasoning questions. The candidate also listed coding tasks without a round, such as reversing an array in groups of three and checking whether an integer is a palindrome. An HR round came fifth. They got an offer and declined it.


03: Selenium and Java tester: framework, shadow DOM and string permutations

Report date: Nov 30, 2024 · Role: Test automation (Selenium and Java); formal title not given · Location: Noida, India

Before the first technical round: A recruiter call asked about SQL DDL and DML commands and some queries.

R1: Technical, one hour (first technical round)

  1. The candidate's Selenium and object-oriented test framework.
  2. How to attach to a browser that is already open, and how to handle multiple windows, dynamic dropdowns and the shadow DOM.
  3. Pull every salary value out of a chart on a page.
  4. Java functional interfaces and threading.
  5. Write all permutations of a string.
  6. A puzzle with five minutes to answer. It wasn't described; the candidate felt about 70% convincing.

After round 1: Two more one-hour technical rounds followed. They covered the bug lifecycle, TestNG parallel runs and retry code, Singleton, Git, the kth largest and smallest values, Linux, sorting a 0/1/2 array in O(n), palindromic substrings and more puzzles. The result wasn't reported.


Software engineers: what came up

These three rounds had little in common. Two candidates gave their coding problems only as topics; the third, on a prototyping team, got a message-batching task.

Topic Reports Last seen
Linked lists 1 of 3 Aug 2025
Arrays and strings 1 of 3 Aug 2025
Dynamic programming 1 of 3 Aug 2025
OS, DBMS and networking basics 1 of 3 Aug 2025
Streaming data 1 of 3 Nov 2024

Software engineers: questions we found

Algorithms / Data Structures

Question Reports Last seen
Mock an API call that returns paginated results 1: 05 Feb 2025
Timed Message Batches 1: 06 Nov 2024

Language and CS Fundamentals

Question Reports Last seen
What is a random variable; common probability distributions 1: 04 Aug 2025

Software engineers: 3 detailed candidate timelines

04: SDE in Bengaluru: three coding problems and some probability

Interview date: Aug 2025 · Role: Software Development Engineer · Location: Bengaluru, India · Result: No offer

Interview, one hour (first technical round)

  1. Three coding problems, shared only by type: a medium linked-list problem, an easy array problem and a hard dynamic-programming problem.
  2. Probability: what a random variable is, and several common distributions.
  3. General CS fundamentals.
  4. The interviewer was supportive and helped along the way.

05: SDE in San Jose: two medium problems and a paginated API mock

Interview date: Feb 2025 · Role: Software Development Engineer · Location: San Jose, California · Result: No offer

Before the first technical round: A 30-minute call with the hiring manager.

Round 2: Live coding (first technical round)

  1. Two medium-level coding problems. They weren't named.
  2. A last task: mock an API call that returns results page by page.
  3. The candidate felt there wasn't enough time to finish everything.

06: Software engineer on a prototyping team: timed message batches

Interview date: Nov 3, 2024 · Role: Software Engineer (prototyping team) · Location: New York, New York · Result: No offer

Before the first technical round: A recruiter call clarified the position and salary expectations.

Round 2: Technical with the hiring manager (first technical round)

  1. One fairly simple coding problem: build a messaging service that gathers incoming messages for a set time, then logs them and clears the batch.

After round 1: The second technical round asked for a small full-stack app, in any stack, that fetches data over HTTP and shows it with filtering and sorting. Final behavioral rounds were with team members in pairs. The candidate did not get an offer.


Machine learning engineer: what came up

The one ML engineer report was an hour of programming built around a modified BFS problem.

Machine learning engineer: questions we found

Algorithms / Data Structures

Question Reports Last seen
Modified BFS problem (change not shared) 1: 07 Jul 2025

Machine learning engineer: 1 detailed candidate timeline

07: ML engineer in Bucharest: an hour built around a modified BFS

Interview date: Jul 9, 2025 · Role: Machine Learning Engineer · Location: Bucharest, Romania · Result: No offer

Programming and algorithms hour (first technical round)

  1. An hour of standard coding-interview problems. The one named was a modified BFS problem; the change wasn't described.
  2. The candidate listed this hour first, so it's treated as the first round.

After round 1: A second hour was on machine learning: theory questions, then building and training a small neural network on dummy data with the screen shared and internet use allowed. No offer followed.


Role not stated: what came up

Neither candidate named the role. One round ended with a rushed medium problem; the other was a variant of Jump Game II.

Topic Reports Last seen
Resume and project deep dive 1 of 2 Jul 2025
Greedy 1 of 2 Jun 2025

Role not stated: questions we found

Algorithms / Data Structures

Question Reports Last seen
Fewest Jumps to the End or Stuck (variation of LC 45) 1: 09 Jun 2025

Role not stated: 2 detailed candidate timelines

08: Role not stated: a distracted interviewer and a race against time

Interview date: Jul 2025 (shortly before the Jul 23, 2025 report) · Result: Rejected the next day

Interview, one hour (probably the first round)

  1. It ran on a shared coding platform that needed a candidate login. Setup ate about 5 minutes.
  2. About 20 to 25 minutes went to the candidate's project, theory questions and some coding around them.
  3. Then a DSA problem where the interviewer wanted the optimal solution straight away. The interviewer said the candidate came very close.
  4. In the last 10 minutes came a medium problem that was hard to implement. The candidate first had to work out what it was asking, coded it, and ran out of time.
  5. The candidate felt the interviewer was unprepared and distracted, and was told simply to code.

09: Role not stated: a Jump Game II variant and disputed test inputs

Interview date: Jun 2025 (a few days before the Jun 18, 2025 report)

Interview (round number not given; treated as the first)

  1. A variation of Jump Game II, the fewest jumps to reach the end (LC 45). The exact twist wasn't described.
  2. The candidate gave an O(n²) brute force first, then an O(n) solution.
  3. The interviewer kept trying inputs that the candidate felt broke the stated constraints. The candidate offered a version that would handle them anyway, and felt the interviewer didn't know how to solve the problem.
  4. No result was reported.

Junior frontend developer: what came up

The one junior frontend round had an unnamed medium problem and a question on promises, async/await and fetch.

Junior frontend developer: questions we found

Language and CS Fundamentals

Question Reports Last seen
Promise vs async/await vs fetch().then 1: 10 Feb 2025

Junior frontend developer: 1 detailed candidate timeline

10: Junior frontend developer in Bucharest: promises and fetch

Interview date: Feb 2025 · Role: Junior Frontend Developer · Location: Bucharest, Romania · Result: No offer

Before the first technical round: A screening problem on HackerRank.

Interview, about one hour (first technical round)

  1. One medium-level coding problem. It wasn't named.
  2. JavaScript and frontend questions, including how a Promise, async/await and fetch().then differ.

Python developer: what came up

The one Python developer round was OOP questions in Python, then a short coding section.

Python developer: questions we found

Language and CS Fundamentals

Question Reports Last seen
Object-oriented programming in Python 1: 11 Jan 2025

Python developer: 1 detailed candidate timeline

11: Python developer in Bucharest: OOP talk, then 20 minutes of code

Interview date: Jan 2025 · Role: Python Developer · Location: Bucharest, Romania · Result: No offer

Interview (first technical round)

  1. The topics were sent ahead by email.
  2. About 10 minutes of introductions, then 30 to 40 minutes on object-oriented programming in Python.
  3. The last 20 minutes were coding. The task wasn't described.

Patterns across the reports

  1. Selenium window handling. Both test-engineering rounds asked how Selenium deals with more than one window (02: window handles and frames; 03: multiple windows, dropdowns and the shadow DOM).

Common questions

What does Adobe ask test automation engineers?

Both test-engineer rounds were mostly Selenium: waits, window handles and frames, XPath and annotations (02), and the candidate's own framework, open browsers, dropdowns and the shadow DOM (03). Each also had one coding or SQL task (02's third-highest salary, 03's string permutations).

How many coding problems are in the Adobe SDE first round?

The two SDE reports had three problems in an hour (04) and two medium problems plus a paginated API mock (05).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.