Skip to content

Adobe Interview Experiences

How Adobe’s SDE/MTS loop actually plays out, based on aggregated candidate reports (GeeksforGeeks, 1point3acres, Blind, Glassdoor) across recent campus and off-campus cycles in Noida and Bangalore.

Reported total compensation for a fresher SDE/MTS role in India spans roughly ₹20-45 LPA (base plus stock/bonus) across public aggregators and candidate posts - the range is wide because it depends heavily on college tier, CGPA, and business unit, so treat any single number as one data point.

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

Experience 1: Software Engineer/MTS, on-campus (2025)

Section titled “Experience 1: Software Engineer/MTS, on-campus (2025)”

Profile: B.Tech CSE, ~8.5 CGPA, tier-1 college, two internships, active on competitive programming, applied through campus placement in Noida.

Online Assessment (90 min, HackerRank)

  • Longest palindromic substring - expand-around-center, all test cases passed in about 25 minutes.
  • Minimum window substring - sliding window with a hashmap, the harder of the two coding problems.
  • LRU cache implementation - hashmap plus doubly linked list, a familiar pattern that came together quickly.

Technical Interview 1 (60 min, video call)

  • Serialize and deserialize a binary tree, followed by trapping rain water with a two-pointer approach.
  • Follow-ups pushed on space-complexity optimization and how the solution would hold up with very large inputs.
  • Closed with 15 minutes on an internship project (an image-processing pipeline) - the interviewer wanted the actual algorithms used, not just the outcome.

Technical Interview 2 (60 min)

  • Word ladder solved with BFS, then a short discussion on designing a basic document-storage system: storage, indexing, and how caching would fit in.
  • A handful of CS-fundamentals questions - process vs thread, virtual memory, database indexing with B-trees.

Hiring Manager round (45 min)

  • “Why Adobe?”, “tell me about a challenging project,” and “how do you handle disagreements in a team?” - each answered with a short, specific story rather than a rehearsed pitch.

Result: Selected. Takeaway: Reasoning out loud through the two-pointer and sliding-window problems mattered more than reaching the answer quickly - the interviewer stopped several times to ask “why this approach” before letting the candidate move on.

Experience 2: Software Engineer, off-campus (2024)

Section titled “Experience 2: Software Engineer, off-campus (2024)”

Profile: B.Tech IT, ~8.0 CGPA, open-source contributor, applied off-campus after a referral, no prior Adobe internship.

What differed from the on-campus track

  • The Online Assessment problems ran harder: merge k sorted lists (min-heap), Word Break II with backtracking and memoization, and finding the median of a data stream. Two were solved optimally, one only partially - still enough to clear.
  • Off-campus added a third technical round: designing a URL shortener, plus a graph problem (course schedule II) and a behavioural segment on leadership examples.
  • The second technical round leaned harder into distributed-systems basics (a rate limiter design) than the on-campus track did at the same level.

Result: Selected after four rounds total. Takeaway: Off-campus loops for Adobe tend to run one round longer and test system-design basics more deliberately - candidates who only prepared DSA were caught off guard by the URL-shortener and rate-limiter questions.

  1. Longest palindromic substring - expand around center
  2. Minimum window substring - sliding window + hashmap
  3. LRU / LFU cache - hashmap + doubly linked list
  4. Serialize and deserialize a binary tree
  5. Trapping rain water - two-pointer
  6. Word ladder - BFS shortest transformation
  7. Course schedule I/II - topological sort
  8. Merge k sorted lists - min-heap
  9. Word Break II - backtracking with memoization

System design (lightweight, fresher-depth)

Section titled “System design (lightweight, fresher-depth)”
  1. Design a basic document-storage or file system
  2. Design a URL shortener
  3. Design a rate limiter
  4. Design a notification system
  1. Why Adobe?
  2. Tell me about a challenging project and what you learned
  3. How do you handle disagreements in a team?
  4. Walk me through a design decision you’d change today, and why
  5. Where do you see yourself in five years?
  • Clear the Online Assessment first - Adobe’s coding problems generally expect all visible test cases to pass, not partial credit.
  • Say your approach out loud before coding; several candidates reported interviewers stopping mid-problem to ask “why this approach” before letting them continue.
  • Know your resume project cold - the Hiring Manager/Director round goes deep on the reasoning behind specific design choices, not just the result.
  • Off-campus loops often run a round longer than on-campus ones and lean harder into basic system design - don’t skip it assuming Adobe is DSA-only.
  • Revise OS/DBMS/networking fundamentals; they show up as standalone questions, not just inside coding problems.

After the technical and Hiring Manager/Director rounds, Adobe closes with a short HR conversation covering fit, logistics, and the offer. Prepare those answers on the dedicated page rather than cramming them into this hub.

Google · Microsoft · Apple · Zoho · Freshworks · Salesforce