Adobe Software Engineer interview questions

30 Software Engineers have shared notes from their Adobe interviews, with the questions they were asked in each round. That is 52% of the 58 Adobe interview notes on Screna AI.

30 Software Engineer interview notes

Adobe·Software Engineer·Onsite - Multi Round

Sep 2026
This is a pre-interview crowdsourcing post from someone trying to gather intel on Adobe's Software Engineer Intern interview before candidates go in. No personal experience shared yet, just a breakdown of what they're hoping to learn across the three rounds: code review, bug solving, and a final technical discussion.
  • In the code review round, is the candidate given a single file or a full repository to navigate through?
  • How much context or prompting is provided before the code review begins?
  • In the code review round, is the expectation a high-level summary of the code or specific line-by-line feedback?
  • In the bug solving round, is the candidate working with a single file or navigating a larger repository?
  • Are the bugs in the bug solving round algorithmic in nature or more system and syntax related?
  • During the bug solving round, are candidates expected or allowed to use AI tools, and do they need to run existing test cases?
  • In the final round, does the interviewer focus on past assessment submissions, your resume, or general technical questions?

View Post

Adobe·Software Engineer·Onsite - Multi Round

Aug 2026
Interviewed at Adobe Noida for an MTS-2 role and got knocked out in the LLD round after barely surviving a brutal DSA round. Two rounds total, both harder than expected in different ways, ended in rejection.
  • Solve a dynamic programming problem on a tree structure.
  • Solve a matrix-based algorithmic problem under strict time pressure.
  • Design a food court system, then extend it with additional constraints provided by the interviewer.

“Got maybe 60-70% of test cases passing and ran out of time before fixing the rest.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jul 2026
Adobe SWE interview that leaned heavily on systems thinking. The main question was a deep dive into word frequency counting at scale, and it covered a lot of ground fast.
  • Write a function to compute word frequencies from a very large text file. Cover how you'd tokenize and normalize the input, handle files bigger than available RAM, and efficiently find the top-K most frequent words. Walk through time and space complexity.

“This one sprawled in a way I didn't expect.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jul 2026
Adobe SWE interview with a dynamic programming problem that looks straightforward until you start thinking about the bonus condition. The question had enough moving parts to trip you up if you're not careful with your state transitions.
  • You're given a binary string representing a work schedule, where '1' is a workday and '0' is a rest day. You also have a base daily pay, a bonus earned whenever two consecutive days are both workdays, and a budget of k flips to turn rest days into workdays. What's the maximum total pay you can achieve, and what's the time and space complexity of your approach?

“I went straight to greedy and immediately realized that was wrong because flipping a single zero can affect two potential bonuses depending on its neighbors.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jun 2026
Adobe full-stack round, one coding question the whole time. They gave me a Node.js filesystem problem and just let me run with it, which I wasn't expecting to be as tricky as it turned out.
  • Using Node.js, write a function that takes a file path and recursively reads all files and subdirectories under it, then prints the directory structure as an indented tree.

“I went straight for the sync version with readdirSync and statSync because I didn't want to fumble async error handling under pressure.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jun 2026
Adobe SWE interview that went deep on a file processing problem. The question started simple but kept expanding into memory constraints and data structure trade-offs, which I wasn't fully ready for.
  • Write a function to read a large text file and return the frequency count of each word. You'll need to define your tokenization and normalization strategy, handle memory constraints through streaming or chunking, and return the top-k most frequent words. Also analyze time and space complexity and compare hash maps, tries, and external sorting when the file barely fits in memory.

“This one kept growing legs.”

View Post

Adobe·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Adobe SWE interview with a single system design question about building type-ahead search for a large e-commerce site. Pretty focused session, no fluff.
  • How would you design a type-ahead (autocomplete) search feature for a large e-commerce platform like walmart.com?

“Spent probably too long on the trie data structure angle before they nudged me toward scale considerations.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jun 2026
Adobe software engineer interview where the whole thing basically revolves around your resume. They pick something you listed and just start pulling threads until you run out of answers.
  • Walk me through your resume, and be ready to go deep on anything you mention.

“This is deceptively stressful.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jun 2026
Adobe technical screen for a software engineer role, basically one big Java Streams question broken into four parts. The whole thing felt like a functional programming deep-dive and I was not fully prepared for the Collector API stuff.
  • Given a Student class with name, grade, and subject fields, implement a method that returns a Collector grouping students by subject and computing the average grade per subject using Java Streams.
  • Implement a method that returns a Predicate<Student> filtering students in a given subject whose grade exceeds a specified threshold.
  • Implement a method that returns a Stream<Student> of the top N students in a given subject, sorted by grade in descending order.
  • Implement a method that returns a Collector computing the median grade per subject, using idiomatic Stream and Collector pipelines without any imperative loops.

“This one I got through okay.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jun 2026
Adobe coding round focused entirely on task scheduling with dependency graphs. Pretty classic topological sort territory but they pushed hard on complexity analysis and edge case behavior, which is where things got interesting.
  • Given n tasks labeled 0 to n-1 and a list of dependency pairs where (a, b) means task a depends on task b, write a function to determine if all tasks can be completed, and if so, return a valid execution order.

“I knew this was topological sort pretty much immediately, but I fumbled the cycle detection explanation for a bit.”

View Post