Adobe is a global software company known for its creative, marketing, and document management solutions - Photoshop, Illustrator, Acrobat, Creative Cloud, Document Cloud, and Experience Cloud. In India, engineering hubs in Bangalore and Noida hire for product development, AI/ML, and cloud services through campus and off-campus MTS / Software Engineer loops.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Adobe is a product-engineering bar. Clearing the printed CGPA floor only gets you into the funnel - the HackerRank-style OA and interview depth decide offers.
Academic requirements
Marks: Typically 7.5+ CGPA or 75% throughout when the JD lists all levels
Degree: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields
Year of Study: Final-year students and recent graduates
Backlogs: No active backlogs (offer-stage verification is common)
Branch & skills
Eligible Branches: CS, IT, ECE, EE, or related streams
Programming: Strong C++, Java, or Python under time pressure
Design preference: Fresher system-design intuition helps Round 2
Minimum CGPA required (candidate-reported): 7.5+ CGPA or 75% throughout when the JD lists 10th, 12th, and graduation. Treat this as a shortlisting floor - Adobe still filters heavily on assessment and interview performance. Always verify the exact requirement on your drive notice or careers portal. Criteria chatter for 2025 and 2026 is the same band, so you do not need a separate year-tagged eligibility FAQ.
| Academic Level | Typical floor (candidate-reported) | Notes |
|---|---|---|
| Graduation | 7.5+ CGPA or 75% throughout | Confirm on campus JD / careers post |
| 10th / 12th | Often aligned when the JD lists all three | Consistency across years matters |
| Backlogs | Usually none active at joining | Offer-stage verification |
What that means day to day: a 8.2 CGPA who cannot finish two medium-hard problems in 90 minutes loses to a 7.6 who ships correct solutions with edge cases. Adobe’s brand looks “creative,” but the fresher SWE loop is still a coding + design grind - Photoshop interest helps HR answers, not OA scoring.
Good fit: You already solve LeetCode mediums under a timer, you can narrate trade-offs on a simple distributed design, and you have 1-2 projects with real metrics (latency, users, storage). Internships on product teams help, but a clean personal project with architecture notes beats a vague internship bullet.
Harder path: You only practiced untimed problems; you freeze when asked “why this data structure?”; your “system design prep” is buzzwords without bottlenecks. Adobe Round 2 rewards concrete constraints (file size, concurrent editors, CDN) more than namedropping Kafka.
Branch myth: ECE/EE students clear Adobe when DSA is real. Branch does not replace coding ability; it also does not auto-reject you if the JD lists related fields and your OA is strong.
Locations: Bangalore and Noida dominate India engineering chatter. Be honest early if you cannot relocate - better than accepting and freezing later.
Backlogs and gaps: active backlogs are the usual hard stop on fresher JDs. Historical cleared backlogs rarely matter if the transcript is clean at offer time - still, do not surprise HR. Gap years are less discussed than at some Indian product companies, but unexplained multi-year gaps invite questions; prepare a one-sentence ownership answer.
Intern convert path: Adobe internship performance can convert to full-time when headcount exists. Conversion is not automatic - treat the internship like a long interview with real code review standards. If you are targeting convert, ask your mentor early what “hire bar” looks like on that team.
Off-campus reality check: Careers applications without a referral can sit longer in resume review. A tight resume with 2-3 defensible projects and a GitHub that matches bullets helps more than a generic “Adobe Creative Cloud enthusiast” summary. Referrals improve visibility; they do not lower the OA bar.
Download 2026 Adobe placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Adobe does not publish one permanent “official paper.” Previous-year style packs on this site train the timed DSA OA and early technical rounds - medium-hard arrays/strings/trees/graphs/DP - plus enough design flavor for Round 2. Think of papers as simulators for 90-minute stamina, not a question bank to memorize. Adobe reuses themes more than exact clones.
| Round (typical) | What to practice |
|---|---|
| Online coding OA | Timed DSA correctness under HackerRank-style constraints |
| Technical 1 | Live coding + complexity + edge cases |
| Technical 2 | Light system design + project depth |
| HR | Why Adobe, motivation, location |
Across recent drives and candidate write-ups, the same families show up:
How to use a paper: time a full 90-minute block; mark every problem you guessed; rewrite any solution that would fail hidden tests; spend 20 minutes listing which pattern you missed. Three reviewed papers beat ten skimmed ones.
Year-page cheat sheet (what to open when):
| Year pack | Use it for | Skip if… |
|---|---|---|
| 2024 | Baseline OA themes, classic medium DSA sets | You only have 3 days - jump to timed PDF |
| 2025 | Newer window/tree/DP mixes, pattern notes | You have not finished one full timed mock yet |
| 2026 | Expected pattern + study plan framing | You are still weak on arrays/hashing basics |
2024 vibe (from student reports): coding OA → DSA tech → design tech → HR; clear rates often cited ~20-30% after coding; packages in the same fresher ₹35-45 LPA chatter band. 2025 vibe: same skeleton with more microservices/cloud vocabulary in Round 2. 2026 prep implication: do not chase a mythical “AI-only paper” - keep DSA sharp and add one AI-feature design talking point (recommendation, generative assist, document intelligence) for HR/design chat.
Hackathon previous-year questions (and Adobe India hiring challenges) typically look like timed DSA sets - often 2-3 coding problems in 90 minutes - plus later design or product discussion for shortlisted teams. Students report overlap between hackathon prompts and the standard Adobe OA bank. Practice Adobe-style prompts on coding questions and year pages; treat hackathon and OA prep as the same DSA core unless your invite specifies a build-a-feature brief.
Adobe runs campus drives at selected colleges and off-campus / careers applications year-round. Hackathons and India hiring challenges sometimes feed the same OA-style bank. Technical bar stays product-SWE either way - campus may feel smoother because of PPT context; off-campus pools are denser.
Campus recruitment
Placement cell PPT → resume shortlist → OA → interviews (virtual or onsite). Season-aligned for many colleges.
Adobe careers / off-campus
Apply on Adobe Careers for MTS / Software Engineer. Resume screen → OA invite → same interview ladder.
Hackathons & referrals
Adobe India challenges / hackathons and employee referrals improve visibility; the coding bar stays the same.
Campus vs off-campus in practice: On-campus = reserved slots, college support, peer energy. Off-campus = more attempts, merit-heavy pool. Many students try both. Content does not soften because the venue is familiar.
Resume / campus shortlist (days to ~2 weeks)
They scan CGPA floors, projects, and internship signals. Put measurable product work on the resume - “built collaborative editor prototype with OT notes” beats “interested in Adobe products.” Roughly half of applicants never see the OA on competitive drives; honesty matters because interviews reopen every bullet.
Online Coding Round (~90 minutes)
Typical: 2-3 coding questions · Format: online proctored (HackerRank commonly reported) · Negative marking: usually none for coding · Languages: C++, Java, Python.
| Focus | Example themes from candidate reports |
|---|---|
| Arrays / hashing | Subarray sums, frequency maps, two pointers |
| Strings | Anagrams, windows, parsing |
| Trees / graphs | Traversals, shortest path on unweighted graphs |
| DP | Climbing stairs / knapsack-style medium DP |
| Design-flavored code | LRU, task scheduler with cooldown, bounded buffer |
Some MTS-1 write-ups describe a split OA: aptitude block + input-output programs + two programming questions in timed slices (for example 15 + 15 + 45 minutes). Read your invite. Clear rates after coding-first OAs are often cited around ~20-30%.
Time boxing that works: 3-4 minute skim → solve the bankable medium → attempt the harder item → reserve time for custom tests. Passing hidden cases beats a brilliant half-solution.
Technical Interview Round 1 (~60 minutes)
Live DSA on shared doc or whiteboard: arrays, strings, trees, graphs, DP. Interviewers watch approach, edge cases, and complexity narration. Success rates among OA survivors are often cited around ~40-50%.
Restate → brute force → optimize → code → test. Silent typing without explaining is a common fail mode.
Technical Interview Round 2 (~60 minutes)
System design + project deep-dive + advanced concepts. Topics: scalability, caching, microservices, APIs, consistency trade-offs - often tied to Creative Cloud, Document Cloud, or media pipelines. About ~50-60% of Round-1 survivors advance in many student reports.
Fresher design bar: identify actors, data model, bottlenecks, and one scaling lever (cache, queue, CDN, shard). You do not need to invent Adobe’s entire cloud.
HR Interview (~30 minutes)
Motivation, Why Adobe?, teamwork, location (Bangalore/Noida), career goals. Communication and integrity checks. Around ~80-90% of tech-clear candidates get offers when location/commitment concerns are sorted.
Prepare a specific Why Adobe (product craft, creative tech, Experience Cloud - pick what is true for you). Vague “I like Photoshop” without engineering curiosity underperforms.
| Phase | Duration | Key activities |
|---|---|---|
| Application / shortlist | 1-14 days | Campus cell or Adobe Careers |
| Online Coding Round | ~1 week window | Invite + 90-minute assessment |
| Technical Interviews | ~1 week | Round 1 + Round 2 (60 min each) |
| HR Interview | 2-3 days | Fit, location, logistics |
| Result / offer | 3-5 days | Offer letter and onboarding details |
Total: usually 2-3 weeks end to end (faster for strong candidates; off-campus can stretch). Extended MTS loops with director/manager rounds can pack multiple hours into fewer calendar days.
If you only remember three numbers: ~90-minute OA, two technical hours, fresher CTC band ₹35-45 LPA (candidate-reported). Everything else is execution detail.
You will not get Adobe’s internal architecture diagram. You will get fresher prompts that reward clear thinking. Practice aloud with a timer (25-35 minutes):
For each: list requirements, draw 4-6 boxes, name the first bottleneck, pick one scaling lever, mention one failure mode. That beats memorizing “CAP theorem” slides.
Most rejection stories after a green OA sound the same: “I could code, but design felt vague.” Adobe Round 2 is not asking you to invent Photoshop. It is asking whether you can reason about users, data, and scale for twenty minutes without collapsing into buzzwords. Practice with a friend who interrupts you every time you say “we’ll use microservices” without naming the pain those services solve. If you cannot explain a cache invalidation problem in plain English, you are not ready - and that is fixable with eight deliberate design sketches, not another fifty easy array problems.
Another under-prep area: OS concurrency vocabulary for MTS loops that touch producer-consumer or scheduler-style coding. You do not need to implement a kernel. You do need to explain locks, races, and why a bounded buffer matters. Spend two evenings on that if your invite hints at applied systems coding.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Adobe invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Adobe sits around ₹35-45 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Adobe eligibility for freshers 2026 (candidate-reported): typically 7.5+ CGPA or 75% across 10th, 12th, and graduation when the JD lists all three; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; no active backlogs. Strong timed DSA and clean project stories matter as much as the academic floor. Always verify your campus JD or Adobe Careers posting.
What you are training for: Adobe placement process typically runs: Online Coding Round (about 90 minutes, 2-3 DSA problems) → Technical Interview 1 (about 60 minutes, live DSA) → Technical Interview 2 (about 60 minutes, system design + projects) → HR Interview (about 30 minutes). Some MTS loops add aptitude/IO blocks or extra managerial rounds. End-to-end is usually 2-3 weeks.
Short version of the prep split: Split prep roughly: DSA/algorithms ~45%, system design ~25%, timed coding mocks ~20%, CS fundamentals ~5%, interview/HR ~5%. Aim for 250-300+ medium-hard problems, weekly 90-minute OA mocks, and one Creative Cloud / Document Cloud flavored design prompt. Full plan: preparation guide on this site.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Adobe previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Adobe drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Adobe usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Adobe?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Adobe-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Adobe story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Adobe papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Adobe papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Adobe-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Adobe paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Adobe. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Adobe, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Adobe mistakes, you are collecting content, not preparing.
Sit one more mixed Adobe set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported as of August 2026 (total annual package bands). Treat them as ranges, not offer letters.
| Level | Experience | Base (approx.) | Total Package | Typical background |
|---|---|---|---|---|
| Software Engineer / MTS | Fresher | ₹35-40 LPA | ₹35-45 LPA | Engineering graduates |
| Senior Software Engineer | 2-3 years | ₹45-60 LPA | ₹50-70 LPA | Relevant experience |
Health coverage, stock purchase / equity components, professional development, flexible arrangements (team-dependent), global collaboration, and Creative Cloud access as a perk students often mention. Bangalore vs Noida living costs differ - HR will still discuss location explicitly.
How to read the fresher band: ₹35-45 LPA is the Software Engineer / MTS range students most often cite for Adobe India. Exact CTC splits (base vs bonus vs RSU) vary by offer letter and year - use the band for expectation-setting, not negotiation theater before you have an offer.
Growth students ask about: MTS / SWE → Senior → staff-level tracks vary by org. Product breadth (Creative, Document, Experience) is a real talking point - if you care about creative tech vs enterprise marketing platforms, say that in your own words.
Location & offer logistics students forget to ask: joining timeline, hybrid expectations for the specific team, equity vesting schedule, and whether the role is Creative Cloud vs Experience Cloud vs Document Cloud adjacent. Those details affect day-to-day more than a 1 LPA band debate before the offer exists.
How Adobe pay compares in student chatter (fresher India): often near Microsoft-like product bands, usually below top-of-market Google chatter, typically above mid-tier SaaS and well above classic service-company packages. Still - pick the product and team, then read the letter.
Hiring trends 2026
System design stays a real Round-2 filter. Cloud-native and AI-feature vocabulary shows up more in Why Adobe / design chat - OA remains DSA-first.
Process shape
Virtual interviews remain common. Some MTS loops still use split OA blocks (aptitude + IO + coding). Project deep-dives got pickier.
Access paths
Campus + Careers + hackathon/challenge funnels. Internship-to-full-time conversion remains a strong path when available.
Company context
India engineering footprint in Bangalore and Noida; Creative Cloud, Document Cloud, Experience Cloud, and AI features across the suite.
Net for 2026 prep: do not wait for a “new pattern” rumor. Double down on timed medium-hard DSA, one polished Adobe-flavored design, and project stories with trade-offs. Process length and virtual formats matter for calendar planning; they do not replace fundamentals.
Also expect more AI vocabulary in Why Adobe answers - Einstein-style features across Document/Experience products show up in student prep notes. You do not need a research paper; you do need one concrete sentence on how AI assists creators or marketers without breaking trust/latency budgets.
Calendar planning tip: if your campus Adobe PPT lands mid-semester with two weeks notice, freeze new topics and run OA mocks + error-log repair only. If you have three months, follow the 8-12 week plans above. Panic-adding system-design courses three days out usually hurts sleep more than it helps Round 2.
Yes. Free Adobe placement papers PDF download and previous-year style coding/DSA/interview practice (2024-2026) are on this site - no registration. Start with the 2026 PDF and the archive. Papers train patterns and timing; they are not leaked live exams.
Typical fresher ladder: Online Coding Round (~90 min, 2-3 DSA) → Technical Interview 1 (~60 min) → Technical Interview 2 (~60 min, design + projects) → HR (~30 min). End-to-end often 2-3 weeks. Some MTS loops add aptitude/IO OA blocks or extra managerial rounds - follow your invite.
Most students report four core stages (OA + two technical + HR). Extended MTS-1 journeys can include five hour-long conversations (multiple technical + director/manager). Count the rounds on your schedule.
Common report: ~90 minutes, 2-3 medium-hard DSA on a proctored platform (HackerRank frequently mentioned), languages C++/Java/Python, usually no negative marking on coding. Alternate MTS papers split time across aptitude, input-output, and programming. Clearing OA only shortlists you for interviews.
Adobe India hiring challenges and campus hackathon-style rounds show up in student chatter. Expect timed DSA sets similar to the OA bank, then design/product discussion for shortlisted teams. Treat hackathon and OA prep as the same DSA core unless your brief is explicitly “build a feature.”
Medium-hard DSA (arrays, strings, trees, graphs, DP), live coding with complexity talk, project architecture, fresher system design (caching, APIs, scale), CS fundamentals (OOP/DBMS/OS), and behavioral/HR (Why Adobe, teamwork, location).
Often yes in Technical Interview 2. Keep it fresher-depth: requirements, data model, bottleneck, one scaling lever. Creative Cloud / Document Cloud flavored prompts beat generic “design Twitter” answers.
Specific Why Adobe tied to products you actually know; STAR stories for ownership/conflict/failure; honest relocation answer for Bangalore/Noida; questions about team mentoring and success metrics. Full bank: HR interview questions.
Candidate-reported: typically 7.5+ CGPA or 75% when listed across 10th/12th/graduation; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; no active backlogs. Same band students cite for recent cycles - verify your JD. Strong OA performance still decides advancement.
C++, Java, and Python are the common trio. Pick one language you can debug live. Do not switch stacks the week of the drive.
Yes when the JD lists ECE/related fields - many do. You still need the same DSA + design bar as CS peers. Branch is not a free pass past the OA.
Candidate-reported as of August 2026: Software Engineer / MTS roughly ₹35-45 LPA CTC (base, bonus, equity vary by Bangalore/Noida team). Offer letter wins over blogs.
Member of Technical Staff - Adobe’s common fresher/early-career engineering title in India. Selected via OA + technical + HR. Day-one focus is product coding; compensation sits in the fresher band above.
Split ~45% DSA, ~25% design, ~20% timed mocks, ~5% CS, ~5% interview/HR. Target 250-300+ medium-hard problems, weekly 90-minute OA mocks, and one Adobe-flavored design prompt. Details: preparation guide.
Adobe: creative/Experience/Document Cloud craft, design-heavy Round 2, fresher CTC often ₹35-45 LPA. Google: algorithms + large-scale systems, often higher fresher bands in student chatter. Microsoft: enterprise/cloud productivity, fresher bands often similar to Adobe in reports. Choose by product interest and written offer.
Correctness-first OA under 90 minutes, then rehearse one Adobe-flavored design with explicit bottlenecks. Brute-force-only answers without complexity talk get filtered hard.
Aim for roughly 250-300+ reviewed medium-hard problems with an error log - not raw attempts. A workable split: ~80-100 arrays/strings, ~60-80 trees/graphs, ~50-70 DP, plus greedy/backtracking. Weekly timed mocks matter more than crossing a vanity count.
The OA is the steepest drop for many campuses (~20-30% clear rates students cite). Technical rounds are medium-hard if you can narrate and defend code. Overall harder than aptitude-heavy service drives, but very beatable with deliberate timed DSA + one design habit - not random easy-problem grinding.
Adobe: creative/document/experience product craft, generally better WLB chatter than the most intense FAANG loops, fresher CTC often ₹35-45 LPA. Amazon: customer-obsession leadership principles, large-scale systems, intense loop culture in many reports. Meta: social/AI/infra product focus, often higher fresher bands in student chatter, fast pace. Choose by product interest, location, and the written offer - not meme prestige.
When the placement cell drops an Adobe PPT with a short window, compress ruthlessly:
Students who “wait to see if they clear OA before preparing interviews” waste the only buffer they have. Adobe loops move in days, not months, once you are shortlisted.
You do not need Adobe Certified Professional for MTS SWE. You do need enough product awareness to sound specific:
Pick one line that matches your interests and prepare a 30-second engineering angle (sync conflict, large asset delivery, permission models, inference latency). That is enough for HR and many Round 2 openers.
In a June 2025 Adobe SDE-3 journey shared on LinkedIn, Round 1 was an Online Assessment on HackerRank with two applied problems (task scheduler with cooldown; bounded buffer / producer-consumer simulation) before live DSA coding (LinkedIn). Even for senior loops, Adobe still opens with a timed coding filter rather than jumping straight to design. Takeaway for juniors: applied systems-flavored coding shows up - practice scheduler/concurrency-style prompts, not only pure array toys.
An Adobe MTS-1 select (page updated July 2025) broke the HackerRank OA into timed blocks on GeeksforGeeks: “15 aptitude questions (15 mins),” five input-output programs (15 mins), and two programming questions (45 mins). Clearing that led to five one-hour onsites - three technical, a director round, and a manager round - covering DSA, OS concurrency, image/line geometry coding, and project detailed questions before selection. Takeaway: some Adobe India loops are longer than the four-round campus summary - budget stamina and OS/concurrency refreshers.
What to steal from these stories: expect HackerRank-style timing; do not assume every OA is “only two coding”; keep design/OS ready for later rounds; and treat one GfG/LinkedIn post as a vibe check, not a fixed template - return to your own timed mocks.
A common campus MTS pattern: 90-minute OAs with medium-hard string/window/DP items, then live rounds that reopen trees and project trade-offs. Candidates who failed often admit the same two mistakes - over-investing in the hardest OA problem first, and listing frameworks they could not defend. Candidates who cleared usually sound almost boring in retrospect: triage early, tests before submit, and one project story with a metric.
If you interview this month: print your invite sections, map them to the practice map above, and schedule two full mocks before the real OA. Do not collect five more PDFs. Execution beats archive hoarding.
Offer-stage checklist: reread the role title (MTS vs SWE), base vs variable vs equity, joining location, background-verification docs, and any internship convert clauses. Celebrate after the letter is signed - not after the HR smile.
Google · Microsoft · Apple · Zoho · Freshworks · Salesforce
