← Interview experiences
Rejected

CS1 at Adobe

Difficulty
Process took
2-3 Weeks
Rounds
3
Format
Remote
Applied via
Company Website

How it went

Not selected, Adobe interview was an eye-opening experience, my advice to regular practice scenario-based DSA problem also

What they would tell you

Not selected, Adobe interview was an eye-opening experience, my advice to regular practice scenario-based DSA problem also

How to prepare

Practice query optimization, joins, ACID properties, and understand master-slave architectures Prepare to draw HLD/LLD diagrams, explain data flow

Their background

YOE: 3 years 10 months Interviewed for CS1 role at Adobe Unfortunately, I did not make it

Round by round

  1. 1

    Coding Round 160 min

    The interviewer started with a self-introduction, then presented a scenario-based problem involving sliding windows.Unlike a standard single-line problem, this one required interpreting requirements, generating edge cases, and designing an efficient approach.The round was strict, and the interviewer pushed hard on the efficiency and correctness of my approach.

  2. 2

    Coding Round 275 min

    This round tested both coding and core computer science concepts, roughly around 60–75 minutes Java Questions

    • How to handle multiple threads modifying the same data structure like a list, array, or map

    • Examples and differences between shallow vs deep copy of objects

    • How to ensure thread safety and avoid race conditions in real-world applications Database Questions

    • How to identify slow-running queries and optimize them for performance

    • Writing efficient SQL queries, explaining joins, aggregations, and indexing strategies

    • Detailed discussion on JDBC usage: how I have integrated it in past projects

    • Master-slave architecture and consistency considerations

    • ACID properties and transactional integrity in database design DSA Problem Minimum Moves to Get a Peaceful Board

  3. 3

    Design Round70 min

    The interviewer asked me to pick my most complex project, draw a high-level design (HLD), and explain the end-to-end architecture, grilled on decision-making, trade-offs, and reasoning behind every design choice. Scenario-based questions included:

    • Handling conflicts in design decisions with senior engineers.

    • What to prioritize when designing a complex system.

    • Justifying why I made certain technical or architectural choices.

    • Behavioral questions: Why Adobe? Why am I considering a change? Schema Design Challenge:

    • I was asked to design a detailed schema for IRCTC ticket booking.

    • Required to navigate the full flow of a ticket booking system: from searching trains, booking seats, payment processing, to ticket generation.

    • I had to explain step-by-step tables, relationships, and how data moves through each step

What came up

MediumRemote3 4 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources