← Back to Directory

Adobe

Large Enterprises

Most of these Adobe write-ups come from Software Engineers (14), then Machine Learning Engineers (11). The most reported rounds are the technical phone screen (18), the behavioral / leadership round (3), the system design round (2) and the hiring manager screen (1).

25 interview notes · updated Jun 2026

Adobe·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Adobe MLE interview that went deep into transformer internals and GPU performance. Felt like they wanted someone who actually understands why things are slow, not just someone who can use a library.
  • Why are transformer models considered memory-bound rather than compute-bound, and what does that mean in practice?
  • What is the cost of materializing the full attention matrix, and how does that affect system design decisions?
  • Can you explain HFU and MFU and how you'd use them to evaluate GPU efficiency?
  • How would you identify and address GPU underutilization in a training or inference workload?
  • What is kernel fusion and when would you use it? How do CUDA graphs fit into that picture?

“This is where I felt most confident.”

View Post

Adobe·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Adobe system design round for a software engineer role. One question, but it kept branching into harder territory every time I thought I had a handle on it. Not a bad experience, just dense.
  • Design an API that returns a unique random integer from a range of 1 to 33 trillion, guaranteed never to repeat, at 300,000 requests per second. Walk through your data structure choices, how you'd partition the keyspace across nodes, how you'd ensure durability and exactly-once issuance, how you'd handle coordination and leader election, and how you'd extend the design if the keyspace doubled to 66 trillion.

“I started with a bitmap and immediately realized I was describing something that would need terabytes of RAM to hold in memory.”

View Post

Adobe·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Adobe SWE interview that leaned heavily on operational depth. Three big questions, all behavioral but with real technical teeth. The kind of round where you can't just recite a story without actually knowing what you're talking about.
  • Walk me through the most complex project you've worked on. What made it complex, what problems came up, and how did you get through them?
  • Describe the most urgent on-call incident you've personally handled. How did you triage, limit the damage, communicate with stakeholders, and follow up after?
  • Share an experience that shows you're a good fit for a role focused on operational excellence.

“I spent too long on the setup and not enough on what I actually did.”

View Post

Adobe·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Adobe SWE behavioral round that's basically a deep dive through your resume. They don't just skim it, they pick a project and start drilling, so you'd better know every decision you made inside and out.
  • Walk me through a significant project on your resume. What was the problem, what did you specifically contribute, and what technical decisions did you make?
  • What would you do differently on that project if you could go back?
  • For a role or project on your resume, what was the outcome and how did you measure success?

“This is the core of the whole round.”

View Post

Adobe·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Adobe ML engineer interview that went deep into transformer internals, specifically Multi-Head Attention. The whole session felt like a graduate seminar on attention mechanics, which I was not fully prepared for.
  • Walk through the full operation order inside Multi-Head Attention, from input to output.
  • What are the Q, K, and V projections doing, and how does tensor reshaping fit into that process?
  • How is the attention score computed and what role does softmax play?
  • Why does Multi-Head Attention use 4 linear projections rather than fewer?
  • Can you estimate the FLOPs involved in self-attention?
  • Why is the computational complexity of self-attention O(S^2) with respect to sequence length?

“I got the broad strokes right but fumbled the exact sequencing of the reshape steps relative to the projection.”

View Post

Adobe·Software Engineer·Technical Phone Screen

Jun 2026
Adobe system design phone screen that went deep on Linux internals. One question, but it had a lot of moving parts and I definitely underestimated how much they'd want on the inode side of things.
  • A process in one terminal is continuously writing to log.txt. Another terminal is running `tail -f log.txt`. You delete the file from a third terminal with `rm log.txt`. Walk through what happens to: the writer's file descriptor and ongoing writes, what the tailer sees, the directory entry and inode lifecycle, and when the disk space actually gets reclaimed. Also cover how `lsof | grep deleted` exposes the situation, and explain the discrepancy you'd see between `df` and `du` after this kind of delete.

“I knew the broad strokes: rm unlinks the directory entry but the inode stays alive while open file descriptors hold a reference.”

View Post

Adobe·Machine Learning Engineer·Technical Phone Screen

May 2026
Adobe ML Engineer interview that was basically one long coding exercise around K-Means from scratch. No sklearn allowed, and they wanted the full discussion on complexity and edge cases too. Felt more like a whiteboard lecture than a back-and-forth.
  • Implement K-Means clustering from scratch using only NumPy or plain lists. Your solution should accept a set of 2D points, the number of clusters k, a max iteration count, and a convergence tolerance. Walk through centroid initialization, point assignment, centroid updates, and the stopping condition. Return both the cluster labels and final centroids.
  • What is the time complexity of your K-Means implementation, and what edge cases should it handle?
  • How would you choose the right value of k for a given dataset?

“This was the whole interview basically.”

View Post

Adobe·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Adobe leadership rounds for a software engineer role, and I walked out pretty sure I'd bombed it. Two separate interviewers said upfront they weren't touching technical stuff and just wanted to know if they could trust me. Vague brief, vague feedback, and then a rejection.
  • How would you go about earning the trust of your manager and your team?

“I fumbled this pretty badly.”

View Post

Adobe·Software Engineer·Technical Phone Screen

May 2026
Adobe SWE interview with a classic array intersection problem. The question had a few layers to it and the follow-up caught me a bit flat-footed.
  • Given two sorted integer arrays, find their intersection. Walk through a two-pointer approach, explain how you'd handle duplicates (set vs multiset semantics), and compare it to a hash-set solution in terms of complexity.
  • Follow-up: if one array is much smaller than the other, how would you change your approach? Think about binary search.

“I jumped straight to two pointers which felt right, and the linear time part clicked pretty naturally.”

View Post

Adobe·Software Engineer·Technical Phone Screen

May 2026
Adobe SWE interview where the resume walkthrough was basically a trap door into a deep dive on everything you've ever touched. If it's on your resume, they will find the edge of what you know.
  • Walk me through your resume, and be ready to go deep on any technology, framework, or system you mention.

“This sounds like a warmup but it really isn't.”

View Post

Adobe interview FAQ

What rounds are in the Adobe interview?

Candidates most often report a technical phone screen (18 write-ups), a behavioral / leadership round (3), a system design round (2) and a hiring manager screen (1).

What does the Adobe technical phone screen cover?

Across 18 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (52 questions), System Design (31) and Algorithms & Data Structures (23).

Adobe interview guides by role

14 notes

Adobe Software Engineer interview questions

11 notes

Adobe Machine Learning Engineer interview questions