Skip to content

Adobe Interview Questions

Adobe runs real campus and off-campus drives out of Noida and Bangalore, pairing DSA-heavy technical rounds with a values-driven Hiring Manager or Director conversation.

Round Duration What it tests
Online Assessment 60-90 min Aptitude/logical reasoning + 2-4 DSA coding problems + CS-fundamentals MCQs
Technical Interview 1 45-60 min Live DSA coding on a shared editor, complexity trade-offs
Technical Interview 2 45-60 min DSA + CS fundamentals (OS/DBMS/networking) + project deep-dive
Hiring Manager / Director round 45-60 min Project ownership, technical judgment, values-driven behavioural questions
HR round 20-30 min Fit, logistics, offer discussion

A HackerRank-hosted test that runs 60-90 minutes: an aptitude/logical-reasoning section (seating arrangements, data interpretation, quantitative aptitude) followed by 2-4 DSA coding problems and a batch of C/C++/Java or CS-fundamentals MCQs. Most drives expect all visible test cases to pass on the coding problems, not just partial credit.

Common questions

  • Longest palindromic substring / minimum window substring
  • LRU or LFU cache implementation
  • Maximum height of a tower buildable between two given towers (greedy/math)
  • OOP, OS, and DBMS MCQs alongside the coding problems

Full round-by-round breakdowns are on the Adobe interview experience page.

A 45-60 minute live coding round, usually over video call with a shared editor. Expect 1-2 DSA problems with follow-up questions on optimizing space/time complexity and handling edge cases - Adobe interviewers generally want to hear your reasoning as you go, not just a final answer.

Common questions

  • Serialize and deserialize a binary tree
  • Trapping rain water (two-pointer)
  • Word ladder / shortest transformation sequence (BFS)
  • Course schedule I/II (topological sort)

See how real candidates handled this stage on the Adobe interview experience page.

Another 45-60 minute round, but weighted more toward CS fundamentals and your resume project alongside a DSA problem. Some loops add a lightweight system-design discussion here - designing a document-storage or notification system in plain language, not a full distributed-systems deep-dive.

Common questions

  • Process vs thread, virtual memory, paging
  • Database indexing and B-trees
  • Design basics for a document-storage or notification system
  • Deep dive into your internship/major project: design choices and trade-offs

Adobe’s most distinctive technical-adjacent round: a 45-60 minute conversation, often with a Director or senior engineering manager, that mixes a project deep-dive with behavioural questions tied to Adobe’s culture. Interviewers probe the “why” behind your technical decisions - not just what you built - and look for ownership of outcomes, including ones that didn’t go as planned.

Common questions

  • Walk me through a design decision you’d change today, and why
  • Tell me about a time you had to defend a technical choice to someone senior
  • How do you handle disagreements within a team?
  • Where do you see yourself in five years?

Sample answer frameworks for each of these are on the Adobe HR interview questions page.

A short 20-30 minute closing conversation covering fit, location/relocation, notice period, and offer logistics. On some campus drives this gets folded directly into the Hiring Manager/Director round rather than run separately.

Common questions

  • Tell me about yourself
  • Why Adobe?
  • Are you willing to relocate to Noida/Bangalore?
  • Do you have any questions for us?

Adobe runs genuine large-scale on-campus and off-campus drives out of Noida and Bangalore, typically gated by a 7.0+ CGPA cutoff for CSE/IT/ECE branches - a real placement-season pipeline, not a referral-only trickle. Because its business units (Creative Cloud, Document Cloud, Experience Cloud) each run their own variant of the loop, round count and exact question mix can differ even within the same overall drive.

Adobe is well known in HR circles for scrapping annual performance reviews in 2012 in favor of frequent, informal “Check-in” conversations between managers and employees - no forced stack ranking, no once-a-year scramble. This isn’t a formal interview round, but it’s a genuine piece of Adobe’s culture that experienced interviewers sometimes reference when asking how you like to receive feedback - candidates who frame their answer around continuous, informal feedback (rather than annual review cycles) tend to land better than those who don’t know the reference.

Frequently asked questions about Adobe interviews

Section titled “Frequently asked questions about Adobe interviews”
What is the Adobe interview process for SDE/MTS roles?

Adobe’s loop usually runs 4-6 stages: 1. An Online Assessment (60-90 min) - aptitude/logical reasoning plus 2-4 DSA coding problems and CS-fundamentals MCQs (OOP, OS, DBMS, networking), run on HackerRank. 2. Two technical interviews (45-60 min each) - live DSA coding on a shared editor, then a second round mixing DSA with project deep-dive and sometimes basic system design. 3. A Hiring Manager or Director round (45-60 min) - project ownership, technical trade-offs, and values-driven behavioural questions. 4. A short HR round (20-30 min) for fit and offer logistics. Campus timelines run 2-4 weeks; off-campus/lateral loops often take 3-6 weeks and add a round.

What questions are asked in Adobe interviews?

Coding rounds lean LeetCode medium-to-hard: arrays/strings (sliding window, two-pointer), trees and graphs (BFS/DFS, topological sort), dynamic programming, and caching structures like LRU/LFU. CS-fundamentals questions cover OOP concepts, OS topics (virtual memory, paging, process vs thread), DBMS (indexing, normalization), and networking (HTTP/HTTPS, DNS, load balancers). The Hiring Manager/Director round probes your resume project in depth - the “why” behind design choices, not just the what - alongside basic system-design questions like designing a document-storage or notification system.

How many rounds are there in the Adobe interview?

Typically 4-6 touchpoints: an Online Assessment, two technical/coding interviews, a Hiring Manager or Director round, and a closing HR round. Some campus drives compress this to 4 rounds by folding HR questions into the Director round; off-campus and experienced-hire loops sometimes add an extra technical round.

How should I prepare for Adobe interviews?

Drill medium-to-hard DSA (arrays, trees, graphs, DP, caching structures) until you can explain complexity trade-offs out loud, revise OS/DBMS/networking fundamentals since Adobe’s fundamentals questions carry real weight, be ready to walk through your major project’s design decisions in depth, and prepare 2-3 STAR stories around ownership and impact for the Hiring Manager/Director round.

Does Adobe hire through campus placements in India?

Yes. Unlike some FAANG peers that hire India engineers mostly off-campus, Adobe runs genuine large-scale on-campus and off-campus drives out of its Noida and Bangalore offices, typically with a 7.0+ CGPA cutoff for CSE/IT/ECE branches. Business units (Creative Cloud, Document Cloud, Experience Cloud) hire in parallel, so exact round count and question style can vary by team even within the same drive.

What is Adobe’s “Check-in” culture, and does it come up in interviews?

Adobe famously replaced annual performance reviews with frequent, informal “Check-in” conversations between managers and employees back in 2012 - no forced rankings, no once-a-year scramble. It’s not a formal interview topic, but interviewers (especially in the Hiring Manager/Director round) sometimes ask how you prefer to receive feedback or handle ongoing coaching, and framing your answer around continuous feedback rather than annual reviews signals you’ve done real homework on Adobe specifically.

What compensation does Adobe offer freshers/SDE-1 in India?

Reported packages for fresher SDE/MTS roles cluster in the roughly Rs.20-45 LPA range (base plus stock/bonus), varying widely by college tier, CGPA, and business unit - treat any single number from a forum post as one data point, not a guarantee.

Looking for placement papers, OA practice, or coding questions?

Section titled “Looking for placement papers, OA practice, or coding questions?”