Katkat

Company

Adobe interview questions

29 practice questions in the style of Adobe's interviews, covering System Design, Coding & Algorithms, Behavioral & Leadership, Analytics & Experimentation, ML System Design, Machine Learning, Data Manipulation (SQL/Python), Statistics & Math.

Questions29

2 easy20 medium7 hard

Your progress0/29

Adobe interview questions by the numbers

Last updated

Katkat has 29 Adobe interview questions. The largest topics are Coding & Algorithms (34%), Behavioral & Leadership (21%) and ML System Design (14%). By difficulty: 7% easy, 69% medium and 24% hard. The most common round is Onsite (52%). Frequent concepts include Algorithms, LLM, aggregation and Attention.

Difficulty

  • Easy7% · 2
  • Medium69% · 20
  • Hard24% · 7

Interview rounds

  • Onsite52% · 15
  • Technical Screen45% · 13
  • Online Assessment3% · 1

Roles

  • Software Engineer66% · 19
  • Machine Learning Engineer21% · 6
  • Data Scientist14% · 4

Frequent concepts

  • Algorithms10% · 3
  • LLM7% · 2
  • aggregation3% · 1
  • Attention3% · 1
  • Clustering3% · 1
  • Collaboration3% · 1

Showing 1–29 of 29 results

  • An Adobe software-engineer system-design screen on analyzing and optimizing end-to-end web request latency. The strong answer builds a client/network/server latency model, instruments both client (RUM) and server (OpenTelemetry, Server-Timing) with correlated traces, attributes frontend vs. backend time, investigates p95/p99 outliers, and ships layered optimizations behind SLO guardrails.

    AdobeSoftware EngineerSystem DesignTechnical Screen
  • This problem tests your ability to manage complex UI state in React, enforce business constraints (role limits) during data manipulation, and implement stable UI rendering based on sorted state.

    AdobeSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Give a concrete example of partnering with a product manager on a difficult decision involving scope, timing, quality, or measurement. Explain shared ownership, ambiguity, disagreement, alignment between product and engineering, and the measured result.

    AdobeSoftware EngineerBehavioral & LeadershipOnsite
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Describe Your Background and Alignment with This Role states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeData ScientistBehavioral & LeadershipOnsite
  • Explain how you want your capabilities, scope, and problem ownership to grow over the next two to three years. Ground the direction in prior evidence, connect it to the role, and show how you plan to learn while remaining adaptable.

    AdobeSoftware EngineerBehavioral & LeadershipOnsite
  • This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Design Metrics Framework for Adobe Express Performance Evaluation states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeData ScientistAnalytics & ExperimentationOnsite
  • Design a runtime localization system for dozens of countries with locale and regional resolution, variables, plural rules, safe fallback, and offline-capable bundles. Address live copy updates, approvals, rollbacks, formatting, missing translations, cache behavior, and longer-text layout failures.

    AdobeSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competency in ML system design for building scalable, multi‑tenant, privacy‑sensitive multimodal embedding pipelines, covering ingestion and idempotency, modality-specific preprocessing, model selection and fusion, throughput engineering, storage and versioning, data hygiene, and operational concerns.

    AdobeSoftware EngineerML System DesignTechnical Screen
  • This interview question evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer for Design a natural-language AEP Q&A assistant states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeMachine Learning EngineerML System DesignOnsite
  • This question evaluates the ability to implement an efficient iterator over nested lists, testing skills in iterator state management, lazy traversal, explicit stack usage, and algorithmic complexity reasoning.

    AdobeSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's competency in designing scalable distributed systems and large-scale data processing pipelines, focusing on ingestion, partitioning/sharding, partial aggregation and merging, global top‑K computation, fault tolerance, idempotency, and storage/serving concerns.

    AdobeSoftware EngineerSystem DesignTechnical Screen
  • This interview question evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer for Design file-embedding storage system states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeSoftware EngineerML System DesignTechnical Screen
  • This question evaluates knowledge of graph algorithms and dependency management, emphasizing concepts such as topological ordering and cycle detection and the ability to determine feasibility and produce a valid execution sequence.

    AdobeSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Determine if a multiple-sum subarray exists states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeMachine Learning EngineerCoding & AlgorithmsOnsite
  • This question evaluates a candidate's proficiency with graph-theoretic concepts like dependency modeling and cycle detection, and their ability to produce valid task orderings under constraints within the Coding & Algorithms domain.

    AdobeSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Discuss resume and behavioral scenarios states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeMachine Learning EngineerBehavioral & LeadershipOnsite
  • This question assesses a candidate's ability to foster psychological safety, maintain accountability, and handle interpersonal friction within a high-stakes engineering environment.

    AdobeSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question tests the candidate's deep conceptual knowledge of the Transformer architecture, focusing on the mathematical mechanics of scaled dot-product attention, memory optimization, and hardware-aware training techniques.

    AdobeMachine Learning EngineerMachine LearningOnsite
  • Tests the ability to write a multi-level SQL aggregation with window functions, exact date filtering, tie handling, and deterministic sorting.

    AdobeSoftware EngineerData Manipulation (SQL/Python)Online Assessment
  • Return the lowest common ancestor of two target values only when both are present in a potentially skewed binary tree. Handle absent targets, equal targets, empty input, and cases where one target is the ancestor.

    AdobeSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your understanding of the K-means clustering algorithm, specifically the iterative process of centroid initialization, assignment, and update steps.

    AdobeMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's skills in text processing, large-scale I/O, token normalization, memory-constrained computation and algorithmic trade-offs for frequency aggregation, and it falls under the Coding & Algorithms domain because it combines parsing, data structures and external processing concerns.

    AdobeSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of scalable word-count processing, including tokenization and normalization rules, streaming or external-memory techniques for inputs larger than RAM, and efficient top‑K frequency computation.

    AdobeSoftware EngineerData Manipulation (SQL/Python)Technical Screen
  • Describe a consequential professional setback that left you frustrated or disappointed. Focus on what was under your control, your response, the perspectives of others, and a lasting change in process or judgment.

    AdobeSoftware EngineerBehavioral & LeadershipOnsite
  • This question tests the ability to diagnose hardware utilization bottlenecks in LLM workloads and design architectural optimizations to improve throughput and latency under constrained GPU memory resources.

    AdobeMachine Learning EngineerML System DesignOnsite
  • Return a binary tree's values grouped by depth in level order while preserving left-to-right order within each level. Handle empty, repeated-value, skewed, and very large trees without changing the requested nested output shape.

    AdobeSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates proficiency in SQL event-log aggregation and basic Python data-structure transformations, assessing competencies such as counting distinct users, identifying frequent event types, and performing dictionary/list/string manipulations.

    AdobeData ScientistData Manipulation (SQL/Python)Onsite
  • This problem tests your ability to recursively traverse a directory structure and format the output into a human-readable, indented tree structure while handling potential I/O errors.

    AdobeSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This interview question evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation in a realistic interview setting. A strong answer for Understand P-Value's Role in Product Decision-Making states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    AdobeData ScientistStatistics & MathOnsite

Adobe interview experiences

All 7 →
  • No response

    The process lasted about four rounds and felt more demanding than a standard recruiter-to-manager path. It began with a discovery-style conversation and a peer interview. I was also asked to prospect for a meeting with the hiring manager. That task was awkward because the hiring manager did not answer calls and had a private LinkedIn profile, so outreach was not straightforward even though the pr…

  • The process felt normal and contained, with about three rounds. It began with a recruiter conversation, then a task, and finally a meeting with the hiring manager. Communication ran smoothly at first, and the recruiter was especially supportive. I received helpful, actionable feedback instead of vague notes. After the first round, the experience did not continue that way. I got nothing back. Ther…

  • Adobe Research Analyst Interview Experience: One-hour research conversationAdobe · Research Analyst · Intern · Technical Screen · Jul 2026
    Offer

    After a recruiter touchpoint, I had one technical conversation with a team member. It lasted an hour and stayed mainly focused on the research I had already done and where I wanted to take it during the internship. The process moved quickly. I had the interview and received a decision about two weeks later. There was not much jumping between steps. It was essentially a discussion about my work an…

  • Five Relaxed Rounds Built Around OOP and API DesignAdobe · Software Engineer · Onsite · Apr 2026

    This one felt pretty comfortable to interview with — slow pace, none of that being-chased-the-whole-time feeling. Each round was an hour, and in some rounds close to half the time was just chatting. The problems were medium-to-easy, but they really like steering things toward object-oriented design and code design — the questions here are different from what other companies ask. A quick note: I'm…

  • This was for the AEP team — a pit that a friend referred me into. Four rounds total, overall not too hard. Round 1 was billed as tech/coding, but after we finished going over my resume, the interviewer just started asking about request latency analysis, plus some front-end/back-end fundamentals-style questions. I initially expected coding or system design, but it ended up basically being a conver…

More companies