Adobe India — with its massive Noida campus (4,000+ engineers) and growing Bangalore presence — is one of the best product companies for engineers who want to work on globally used software at scale. Photoshop, Illustrator, Acrobat, and Adobe Experience Cloud are used by hundreds of millions of people. For Delhi-NCR engineers especially, Adobe Noida is often the dream first product company switch.
What makes Adobe India interviews unique: they place significantly more emphasis on Object-Oriented Design (OOD) than most companies. You won't just solve a LeetCode problem — you'll be asked to design a class hierarchy, justify your design patterns, and extend your design to new requirements. This guide covers everything: rounds, OOD prep, DSA by frequency, system design scenarios, and salary.
4
Interview rounds (SDE/MTS)
OOD
Heavy emphasis on object-oriented design
₹25–52L
Total CTC range MTS1–MTS2
6–8 wk
Recommended prep time
1. Adobe India Campuses — Noida vs Bangalore
🏢 Noida (Sector 25 — Adobe India HQ)
- Largest Adobe India campus — 4,000+ engineers
- Teams: Photoshop, Illustrator, InDesign, Acrobat, Adobe Fonts
- Deep ownership of flagship creative products
- Most connected to Adobe's core creative DNA
- Well-established culture, excellent campus facilities
- Salary slightly below Bangalore market rate
🏢 Bangalore (Kalyani Tech Park)
- Smaller campus — 1,500+ engineers, growing fast
- Teams: Adobe Experience Cloud, Analytics, Campaign, Marketo, Magento Commerce
- More cloud/SaaS and B2B marketing tech focus
- Higher salaries (Bangalore market premium)
- Better access to other Bangalore product company talent networks
- More recent campus, newer teams with ownership opportunities
2. Adobe India Interview Process — All 4 Rounds Explained
Round 1
Online Assessment (OA)
- 3 DSA problems: 1 Easy (warmup), 1 Medium, 1 Medium-Hard
- No behavioral section — pure coding
- Adobe OA is generally considered similar to Flipkart's — Medium difficulty, occasional Hard
- Common topics: arrays, trees, dynamic programming, string manipulation
- Cutoff: need to fully solve at least 2 problems
- Tip: Adobe tags on LeetCode show frequently tested patterns — solve top 60 Adobe-tagged problems
Round 2
Technical Round 1 — DSA + OOD
- 1–2 DSA problems: Medium difficulty, discussion of complexity and edge cases
- OOD component: Design a class hierarchy for a real-world problem — this is Adobe's signature addition
- Common OOD asks: Design a logging framework, design a plugin system for Photoshop, design a document editor's undo/redo
- Expected: class diagram in words/pseudocode, identify design patterns, discuss extensibility
- SOLID principles are explicitly tested — interviewers may ask "does this follow the Open/Closed principle?"
- Tip: Adobe builds complex GUI software — they value engineers who think about extensibility and plugin architectures
Round 3
Technical Round 2 — System Design + Project Deep-Dive
- System design (SDE2+): Full HLD for a cloud or creative-software system
- SDE1: Lighter LLD problem or OOD extension of Round 2
- Project deep-dive: One of your past projects, probed for technical depth (data model, scale challenges, trade-offs made)
- Adobe-specific design questions: design a document collaboration system, design a media asset management system, design a SaaS analytics pipeline
- Adobe Experience Cloud engineers often get cloud/SaaS system design; Noida creative product engineers may get architecture questions about plugin systems or rendering pipelines
Round 4
Hiring Manager / Director Round
- Conducted by the hiring manager or a Director — the person you'd directly report to
- Behavioral questions based on Adobe's Work Smart values (see Section 4)
- Career discussion: "What kind of problems do you want to solve in the next 3 years?"
- Adobe asks: "Why creative software / digital experience?" — show you understand their products as a user, not just a developer
- Compensation discussion often starts here
- This round has lighter technical questions — focus is 80% behavioral, 20% technical clarifications
3. Object-Oriented Design (OOD) — Adobe's Signature Focus
Adobe builds complex, extensible software (Photoshop plugins, Acrobat document processing, Experience Cloud modules). Their engineers must think in clean class hierarchies and design patterns. This is why OOD appears in almost every Adobe technical round — it's not an add-on, it's core to how Adobe engineers think.
⚠️ Most Common OOD Mistake at Adobe
Writing one God Class that does everything. Adobe interviewers will explicitly ask "does this follow Single Responsibility?" If your entire solution is in one class, they'll guide you to break it down. Practice creating multiple small, well-named classes with clear responsibilities before your interview. The best Adobe OOD solutions feel like they could actually be shipped as part of Photoshop or Acrobat.
Top Adobe OOD Problems to Practice
1. Design Photoshop's Undo/Redo System
Support multiple operations (draw, fill, delete layer). Undo/redo with history. Merge consecutive strokes into one undoable action.
Key classes: Command (interface), DrawCommand, FillCommand, CommandHistory, OperationExecutor. Pattern: Command Pattern + Memento for state.
2. Design a Plugin System (like Photoshop extensions)
Third-party developers can write plugins. Plugins can add new menu items, filters, and tools. System should work without modifying core code.
Key classes: PluginRegistry, PluginInterface, PluginLoader, MenuItem, ToolRegistry. Pattern: Plugin/Extension pattern, Factory, Strategy.
3. Design a Document Collaboration System (like Google Docs)
Multiple users edit the same document simultaneously. Track changes, comments, revision history. Conflict resolution for concurrent edits.
Key classes: Document, Revision, Change, Comment, CollaborationSession, ChangeTracker, ConflictResolver. Pattern: Observer for live updates, OT for conflict resolution.
4. Design a Logging Framework (like Log4j)
Support multiple log levels (DEBUG, INFO, WARN, ERROR). Multiple appenders (file, console, remote). Configurable log formatting. Thread-safe.
Key classes: Logger, LogLevel, LogRecord, Appender (FileAppender, ConsoleAppender), Formatter, LogManager. Pattern: Chain of Responsibility, Observer, Singleton for LogManager.
5. Design a Media Asset Management System
Store and organize images, videos, PDFs. Support tagging, search, permissions, previews. Version control for assets.
Key classes: Asset, AssetVersion, Tag, Folder, Permission, AssetRepository, PreviewGenerator. Pattern: Strategy for preview generation per asset type, RBAC for permissions.
6. Design Adobe Sign (e-Signature Workflow)
Create signature requests, multiple signers in order, reminder system, audit trail, status tracking.
Key classes: SignatureRequest, Signer, SignatureField, AuditLog, ReminderService, DocumentTemplate. State machine for request lifecycle. Observer for notifications.
4. DSA Patterns Adobe India Tests Most Frequently
| Topic | Frequency | Key Patterns | Must-Solve Problems |
|---|---|---|---|
| Arrays & Strings | Very High | Sliding window, two-pointer, prefix sum, matrix | Minimum Window Substring, Longest Repeating Character Replacement, Image Rotation, Spiral Matrix |
| Trees & Graphs | High | BFS/DFS, binary search, LCA, traversals | Flatten Binary Tree, Lowest Common Ancestor, Path Sum III, Course Schedule |
| Dynamic Programming | High | 1D DP, 2D DP, DP on strings | Longest Common Subsequence, Palindrome Partitioning II, Decode Ways, Maximal Square |
| OOD/Design Patterns | High (Adobe-specific) | SOLID, Command, Strategy, Observer, Factory | See OOD problems section above — these are the "must-solve" for Adobe |
| Stacks & Queues | Medium | Monotonic stack, expression parsing, design | Basic Calculator, Evaluate Reverse Polish Notation, Maximum Rectangle |
| Heaps | Medium | K-way, custom comparators | Merge K Sorted Lists, Task Scheduler, Find Median from Data Stream |
5. Adobe's Work Smart Values — Behavioral Interview Prep
Genuine
"Tell me about a time you gave honest feedback that was difficult to deliver."
Authentic communication, transparency, saying hard truths respectfully
Exceptional
"Tell me about the highest quality work you've ever shipped. What made it exceptional?"
High standards, craftsmanship, going beyond "done" to "excellent"
Innovative
"Tell me about a time you found a novel solution to a problem everyone else was solving conventionally."
Creative problem-solving, challenging assumptions, new approaches
Involved
"Tell me about something you built or contributed to outside your direct responsibilities."
Community engagement, cross-team contribution, caring beyond your scope
💡 Adobe Behavioral Interview Tip
Adobe engineers work on software used by creative professionals — designers, photographers, filmmakers. The best behavioral stories at Adobe show that you think like a product person, not just a developer. "I refactored the code" is fine — but "I redesigned the API to be more intuitive for plugin developers, which reduced their integration time by 60%" is what Adobe interviewers remember. Connect your technical work to user impact.
6. Adobe System Design — Creative & Cloud Scale
Adobe system design questions split between creative software architecture (Noida) and cloud SaaS design (Bangalore). Know which team you're interviewing for and prepare accordingly.
Common Adobe System Design Scenarios
- Design Adobe Experience Manager (AEM): CMS with templating, asset management, multi-site, multi-language. Key concepts: content versioning, role-based access, CDN for asset delivery, OSGi-based plugin architecture.
- Design a SaaS Analytics Platform (Adobe Analytics): Collect user events (100B events/day), real-time dashboards, historical reports, customer segmentation. Key concepts: Kafka ingestion, lambda architecture (batch + stream), columnar storage (Apache Parquet), query engine.
- Design Adobe Sign e-Signature Service: Send documents for signature, track status, audit trail, multi-signer workflows. Key concepts: state machine for signature workflow, encrypted document storage, exactly-once processing, compliance audit log.
- Design a Distributed Rendering Pipeline: Process large Photoshop/After Effects files in the cloud. Distribute rendering tasks across nodes. Key concepts: task queue, node health monitoring, work stealing, result aggregation.
- Design a Digital Asset Management (DAM) System: Store, organize, search 100M+ creative assets (images, videos, PDFs). Key concepts: metadata indexing (Elasticsearch), CDN for fast preview, format transcoding pipeline, access control.
7. Adobe India Salary Breakdown 2026 (MTS1–Principal)
Adobe India uses the title MTS (Member of Technical Staff) — equivalent to SDE. Compensation includes base + performance bonus (10–20%) + RSUs in ADBE stock (vesting quarterly over 4 years after 1-year cliff).
MTS1
Member of Technical Staff 1 (SDE1 equivalent, 0–3 yrs)
Base: ₹18–25 LPA | Bonus: 10–12% | RSUs: ₹6–12L/yr | Total: ₹26–36 LPA
MTS2
Member of Technical Staff 2 (SDE2 equivalent, 3–6 yrs)
Base: ₹28–38 LPA | Bonus: 12–15% | RSUs: ₹12–22L/yr | Total: ₹38–52 LPA
Sr MTS
Senior MTS (SDE3 equivalent, 6–9 yrs)
Base: ₹40–55 LPA | Bonus: 15–18% | RSUs: ₹22–40L/yr | Total: ₹55–76 LPA
PMTS
Principal MTS (10+ yrs)
Base: ₹60–80 LPA | Bonus: 18–22% | RSUs: ₹40–80L/yr | Total: ₹80–1.2 Cr
8. 6-Week Adobe India Preparation Plan
Week 1–2
OOD + Design Patterns Foundation
- Study SOLID principles with concrete code examples — apply each to a scenario
- Learn and implement: Command Pattern, Strategy, Observer, Factory, Singleton, Builder
- Implement 4 OOD problems from scratch under 60-minute timers (undo/redo, plugin system, logging, media asset)
- Practice explaining your class design out loud: "I chose Strategy here because..."
Week 3–4
DSA: Arrays, Trees, DP + More OOD
- Arrays and strings: sliding window, two-pointer, matrix manipulation — 30 Medium problems
- Trees and graphs: BFS, DFS, common tree patterns — 25 problems
- DP: grid DP, string DP, 1D DP — 20 Medium problems
- 2 more OOD problems: document collaboration system, Adobe Sign workflow
- Filter LeetCode by "Adobe" company tag — solve top 50 by frequency
Week 5–6
System Design + Work Smart Stories + Apply
- Design: DAM system, analytics platform, e-signature service, collaborative document editor
- Write 4 Work Smart STAR stories: Genuine (honest feedback), Exceptional (high quality), Innovative (novel solution), Involved (beyond scope)
- Research Adobe's latest products: read tech.adobe.com and recent announcements
- Practice using Adobe products as a user — understanding user pain points strengthens your behavioral stories
- Apply: Adobe careers portal + referral from Adobe engineers (LinkedIn, alumni networks)
9. Frequently Asked Questions
How many rounds are in the Adobe India SDE interview process?
Adobe India runs 4 rounds: (1) Online Assessment — 3 DSA problems on HackerEarth; (2) Technical Round 1 — 1–2 DSA problems + OOD class design; (3) Technical Round 2 — System design (SDE2+) or LLD + project deep-dive; (4) Hiring Manager/Director Round — Work Smart behavioral questions + career goals. The total process takes 3–5 weeks. Adobe's interview is generally considered moderate difficulty — easier than Google/Amazon but harder than Walmart Global Tech or SAP Labs.
What is the Adobe India MTS salary in 2026?
Adobe uses the MTS (Member of Technical Staff) title. MTS1 (SDE1 equivalent) earns ₹26–36 LPA total CTC in 2026. MTS2 (SDE2) earns ₹38–52 LPA total. Senior MTS earns ₹55–76 LPA. Adobe pays below FAANG but above most Indian product companies. ADBE stock has performed consistently well, making RSUs particularly valuable. Bangalore campus salaries run 10–15% higher than Noida for the same level.
Which is better — Adobe Noida or Adobe Bangalore?
Both are strong choices with different profiles. Noida: larger campus (4000+ engineers), deeper ownership of Photoshop/Illustrator/Acrobat, strong creative product culture, slightly lower salary. Bangalore: growing campus, Adobe Experience Cloud teams (cloud/SaaS focus), higher salaries, better access to Bangalore's tech ecosystem. If you want to work on iconic creative software, choose Noida. If you want cloud/SaaS engineering at scale, choose Bangalore. Career growth is strong at both.
How important is OOD/object-oriented design for Adobe interviews?
Very important — more so than at most other companies. Almost every Adobe technical round includes an OOD component: design a class hierarchy, justify your design patterns, and demonstrate SOLID principles. This reflects Adobe's actual engineering culture — they build complex, extensible software that must work as plugin platforms. Practice implementing Command Pattern, Strategy, Observer, and Factory from scratch. For Adobe, the ability to design extensible, maintainable systems is as important as solving DSA problems.
What are Adobe India's Work Smart values and how do I prepare for them in interviews?
Adobe's Work Smart values are: Genuine (authentic, honest), Exceptional (high quality standards), Innovative (creative problem-solving), Involved (engaged beyond your scope). Prepare 4 STAR stories, one per value. The best approach: connect your technical work to user impact. "I innovated by redesigning the API to be simpler for plugin developers" resonates more than "I wrote an innovative algorithm." Show that you think about the people using what you build — Adobe's users are creative professionals who depend on their tools daily.
🎨 Prep for Adobe India with PrepFlix
DSA tracks, OOD patterns, and system design guides designed for Adobe India SDE/MTS interviews. Build the skills that get you hired at India's premier creative tech company.
Start Your Prep →