Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · Adobe

Adobe Technical Interview Questions India 2026

Adobe's coding rounds in India often use graphics- and document-flavoured data-structures and algorithms: flood-fill on an image matrix, an LRU cache for rendered thumbnails, efficient undo/redo over a stream of edit operations.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds3
Intense3 of 12
FrameworkIn-Domain DSA
Try it · Adobe question 1 of 10
Standard

Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect medium-to-hard problems where the interviewer wants correct code, sensible data-structure choices, and a follow-up on memory when the canvas or document is huge. The in-domain framing is deliberate; Adobe values engineers who connect the algorithm to how a real editor would use it.

Practice questions

  1. 01

    Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

    Standard
    Practise
  2. 02

    What is the difference between a class and an object? Give an example.

    Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.
    Practise
  3. 03

    Write a SQL query to find the second-highest salary in a department.

    Warm-up
    Practise
  4. 04

    What is normalisation in databases? When would you de-normalise?

    Warm-up
    Practise
  5. 05

    What's the difference between a stack and a queue? Give a real-world use case for each.

    Warm-up
    Practise
  6. 06

    Given a stream of integers, design a data structure that returns the median in O(log n).

    Intense
    Practise
  7. 07

    You have a service that's slow only on Tuesdays. Walk me through how you'd debug.

    StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first.
    Practise
  8. 08

    Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.

    IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.
    Practise
  9. 09

    Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.

    StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas.
    Practise
  10. 10

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    Practise
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes

How to walk in ready.

The typical Adobe recruitment process has 4 stages: Online coding assessment or campus test → Technical coding round one on DSA → Technical coding round two plus low-level design → Hiring-manager round, then offer.

Adobe typically conducts 3 interview rounds: Round 1 (60-90 min): online assessment with DSA problems; Round 2 (60 min): live coding on flood-fill, caching, or stack-based problems; Round 3 (60 min): harder coding plus low-level design with memory and scale discussion.

HireStepX recommends the In-Domain DSA framework for this type of interview: Solve the algorithm cleanly with a stated complexity, then answer the memory or scale follow-up in terms of a real editor or document workload.

TCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.

Googleyness: structured debugging, hypothesis-driven, instrumentation-first.

Stripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.

BFS/DFS (flood-fill), caching and LRU, stacks for undo/redo, arrays and matrices, and trees, at medium-to-hard difficulty, usually framed around graphics or document editing.

Medium to hard. Correctness, a sensible data-structure choice, and an honest complexity and memory discussion matter most.

Practice

Rehearse the room before you enter it.

Run a mock Adobe interview and get scored feedback on every answer.