Adobe Web, QA, DevOps, ML Roles: 13 Experiences (Part 3 of 3)

Shared by janebeingjane ·
Company
Adobe
Level
Unknown
Stages
Phone screen

Nine 2023-24 Adobe frontend, quality, DevOps and ML reports with no level given: frontend rounds leaned on theory, quality first rounds on coding.

At a glance

  • Process: six reports describe one technical interview (FE 01 to FE 05, OPS 01): FE 04's came after an online coding challenge and was followed by a soft-skills interview, and OPS 01's came after a 15-minute call. ML 01 gave a research talk, then had a coding round. QA 01 had three rounds and QA 02 seven.
  • Asked in these reports: web or React theory in four of five frontend reports (FE 01, FE 02, FE 04, FE 05); several string and array tasks for both quality engineers (QA 01, QA 02); one architecture question for DevOps (OPS 01).
  • Difficulty: QA 01 called its palindrome task easy, and ML 01's problem was LeetCode medium; the frontend reports gave no rating.
  • Practise first: Is the String a Palindrome, Move the Ones Before the Zeros and Design a Web App With Password Login.

Coverage: 13 candidates with no hiring level given: six frontend, web or JavaScript, three quality, two DevOps and two machine learning, in India, Romania, France and the United States. Nine are current (Nov 2023 to Oct 2024); four from 2022 sit in History.

In this series

Roles in this part: frontend and web (FE 01–05, FE H01) · quality engineers (QA 01–02, QA H01) · DevOps (OPS 01, OPS H01) · machine learning (ML 01, ML H01).

Frontend and web developers

What came up

Four of the five current reports centred on web or React theory (FE 01, FE 02, FE 04, FE 05), and FE 03 on projects and data structure types. Two named a coding task in the interview, a queue from stacks (FE 02) and a palindrome with a stack (FE 05), and FE 04 had an online coding challenge first.

5 detailed candidate timelines, loops, and screens

FE 01: front-end basics, then a no

Interview date: Oct 2024 · Role: Front End Developer · Location: Bucharest · Result: No offer

  1. Lazy loading, JavaScript performance, the CSS box model, semantic HTML and JavaScript primitives. The feedback said core concepts were missing.

FE 02: React APIs and a queue

Interview date: May 2024 · Role: Front End Developer · Location: India · Result: Offer accepted

  1. Deep questions on calling APIs from React, and one coding task: Build a Queue From Two Stacks.

FE 03: improve your project

Interview date: Jan 2024 · Role: Frontend Engineer · Location: Noida · Result: No offer

  1. Resume projects and how to make them better, then linear versus non-linear data structures.

FE 04: an HTTP method question

Interview date: Dec 2023 · Role: JavaScript Developer · Location: Bucharest · Result: No offer

  1. After an online challenge, a technical interview asked which HTTP method fits posting a comment on social media. A soft-skills interview followed.

FE 05: a palindrome with a stack

Interview date: Nov 2023 · Role: Web Developer · Location: Bengaluru · Result: No offer

  1. Logic and basic coding first: check a palindrome using a stack (Is the String a Palindrome). Then React, frameworks and design principles.

History (before Nov 2023)

FE H01: picking from an array

Interview date: Mar 2022 · Role: JavaScript developer · Location: Romania · Result: No offer

  1. An online test (two coding problems and multiple-choice questions), then a technical round on HTTP, databases and data structures, such as the cost of reading one item from an array.

Quality engineers

What came up

Both current quality engineers opened with two string or array problems (QA 01, QA 02). QA 02 then moved to test plans, a microservice test strategy, more coding with language questions, and manager and director rounds; QA 01 stayed on coding for all three rounds, with one Selenium snippet at the end.

2 detailed candidate timelines, loops, and screens

QA 01: ones before zeros, then a surprise manager

Interview date: Mar 2024 (report date Apr 2024) · Role: Software Quality Engineer, automation · Location: India · Result: Rejected after round 3

  1. Round 1: rearrange [1,0,0,1,1,1,0] so the ones come first. The candidate struggled for about 15 minutes, then used a list and discussed cost and tests (Move the Ones Before the Zeros). Next, an easy string palindrome check with tests (Is the String a Palindrome).
  2. Round 2: an array's minimum and maximum, and its most repeated value with a hash map.
  3. Round 3, billed as HR but run by the hiring manager: weave arrays A and B into a third (done in five minutes), some Selenium code and debugging habits. The recruiter later said the skills did not fit.

QA 02: seven rounds for a quality engineer

Interview date: Nov 2023 · Role: Software Quality Engineer · Result: Offer accepted

  1. Round 1: the most and least frequent characters in a string (Most and Least Frequent Characters) and every pair that sums to x (Every Index Pair That Sums to a Target).
  2. Round 2: test plans for creating a group chat and for a big sale day. Round 3: how to test a microservice newly added to a product that already exists, down to the code.
  3. Round 4: moving negative numbers to the left, plus many language and test-framework questions. Round 5: removing vowels and sketching a printer with SOLID classes.
  4. Rounds 6 and 7: a manager asked test-strategy scenarios as if the candidate led a project's testing, and a director asked much the same, plus past experience.

History (before Nov 2023)

QA H01: strings and lists, then cut

Interview date: Aug 2022 · Role: SDET · Location: India · Result: No offer

  1. First technical round: string and linked-list questions. The candidate was cut, and round two never happened.

DevOps engineers

What came up

The one current DevOps report was a single architecture question (OPS 01).

1 detailed candidate timeline

OPS 01: a login web app architecture

Interview date: Sep 2024 · Role: DevOps Engineer · Location: Clermont-Ferrand · Result: No offer

  1. A 15-minute call on the company and pay, then a 40-minute technical interview: propose an architecture for a team building a TypeScript front end and a back end with a database and password login (Design a Web App With Password Login).

History (before Nov 2023)

OPS H01: pairs with a target sum

Interview date: Apr 2022 · Role: DevOps Engineer · Location: France · Result: No offer

  1. Under ten minutes on the job and the CV, then 30 minutes of technical questions that had little to do with the job: in any language, find the pairs among signed whole numbers in a list that add up to a target (Every Index Pair That Sums to a Target).

Machine learning engineers

What came up

The one current ML report was a research talk followed by an unnamed LeetCode-medium coding problem (ML 01).

1 detailed candidate timeline

ML 01: research first, then a medium problem

Interview date: Apr 2024 · Role: Machine Learning Engineer · Location: San Jose · Result: No offer

  1. A detailed research presentation with questions on the model, the problem and the papers, then a medium coding problem (not named).

History (before Nov 2023)

ML H01: an image classifier in PyTorch

Interview date: Sep 2022 · Role: Machine Learning Engineer · Location: Remote · Result: Offer accepted

  1. Design an image classifier, write it in PyTorch and defend each choice (the closest Adobe case is Design an On-Device Classifier for Imported Image Types), plus Multiply Two Matrices. A manager interview followed; the candidate found both very easy.

Keep practicing

In this series

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.