Adobe Software Engineer Onsite Coding Questions
24+ questions from real Adobe Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the Adobe Onsite Coding round test?
The Adobe onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
Adobe Software Engineer Onsite Coding Questions
Adobe Frontend Engineering Fulltime Onsite Interview Experience
Firefly Front-End Interview Experience In-Store Interview The HR will tell you what aspects they'll test when they contact you. It mainly focuses on concepts; just memorize those concepts before the i
Adobe Interview Experience | Set 26 (On-Campus for MTS-1)
Adobe visited our campus for full-time Member of Technical Staff-I (MTS-1)First round consisted of an aptitude test and a coding test.The aptitude test had 45 minutes and ...
Permutation sequence of N repeating numbers
Given an array of 2N positive numbers where every number from 1 to N appears exactly twice in the array, find if there is a permutation possible such that for...
#49 Group Anagrams
LeetCode #49: Group Anagrams. Difficulty: Medium. Topics: Array, Hash Table, String, Sorting. Asked at Adobe in the last 6 months.
#146 LRU Cache
LeetCode #146: LRU Cache. Difficulty: Medium. Topics: Hash Table, Linked List, Design, Doubly-Linked List. Asked at Adobe in the last 6 months.
LeetCode #1636: Sort Array by Increasing Frequency. Difficulty: Easy. Topics: Array, Hash Table, Sorting. Asked at Adobe in the last 6 months.
#56 Merge Intervals
LeetCode #56: Merge Intervals. Difficulty: Medium. Topics: Array, Sorting. Asked at Adobe in the last 6 months.
#468 Validate IP Address
LeetCode #468: Validate IP Address. Difficulty: Medium. Topics: String. Asked at Adobe in the last 6 months.
#5 Longest Palindromic Substring
LeetCode #5: Longest Palindromic Substring. Difficulty: Medium. Topics: Two Pointers, String, Dynamic Programming. Asked at Adobe in the last 6 months.
#1 Two Sum
LeetCode #1: Two Sum. Difficulty: Easy. Topics: Array, Hash Table. Asked at Adobe in the last 6 months.
#392 Is Subsequence
LeetCode #392: Is Subsequence. Difficulty: Easy. Topics: Two Pointers, String, Dynamic Programming. Asked at Adobe in the last 6 months.
#475 Heaters
LeetCode #475: Heaters. Difficulty: Medium. Topics: Array, Two Pointers, Binary Search, Sorting. Asked at Adobe in the last 6 months.
#20 Valid Parentheses
LeetCode #20: Valid Parentheses. Difficulty: Easy. Topics: String, Stack. Asked at Adobe in the last 6 months.
#124 Binary Tree Maximum Path Sum
LeetCode #124: Binary Tree Maximum Path Sum. Difficulty: Hard. Topics: Dynamic Programming, Tree, Depth-First Search, Binary Tree. Asked at Adobe in the last 6 months.
#1482 Minimum Number of Days to Make m Bouquets
LeetCode #1482: Minimum Number of Days to Make m Bouquets. Difficulty: Medium. Topics: Array, Binary Search. Asked at Adobe in the last 6 months.
#983 Minimum Cost For Tickets
LeetCode #983: Minimum Cost For Tickets. Difficulty: Medium. Topics: Array, Dynamic Programming. Asked at Adobe in the last 6 months.
LeetCode #1293: Shortest Path in a Grid with Obstacles Elimination. Difficulty: Hard. Topics: Array, Breadth-First Search, Matrix. Asked at Adobe in the last 6 months.
Stream/Collector: Subject average, filter above average, top-K by subject, and median per subject
## Problem: Student grade processing with Java Streams (Collector/Predicate) You are given a list of `Student` objects, each with: - `name` (String) - `grade` (double) - `subject` (String) Implemen
## Binary Tree Maximum Path Sum (Tree Kadane) Given a binary tree `root` (node values may be negative), a **path** is defined as: - It can start and end at any nodes; - No node appears more than onc
## Problem: Print directory tree given a file path (Node.js) Given a filesystem path `path` (possibly a directory), use Node.js to read and print all files and folders under that path as a tree. ###
What to Expect in the Adobe Onsite Coding Round
The Adobe Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 24+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at Adobe show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at Adobe typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Adobe Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 24 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access