← Interview experiences
Got the offer

SDE 2 at Expedia

Difficulty
Process took
2-3 Weeks
Rounds
5
Format
Remote
Applied via
Referral

How it went

Each round had a clear purpose, the interviewers were respectful and engaged If you are preparing for Expedia, I'd recommend focusing heavily on DSA fundamentals, being comfortable with system design patterns, and having clear stories from your past experience ready to share

What they would tell you

Each round had a clear purpose, the interviewers were respectful and engaged If you are preparing for Expedia, I'd recommend focusing heavily on DSA fundamentals, being comfortable with system design patterns, and having clear stories from your past experience ready to share

How to prepare

For OA, What I realized timing really matters, you're constantly racing against the clock, beyond just getting the right logic, they also care about how clean your code is.

Round by round

  1. 1

    Online Assessment60 min

    I had to solve two DSA-based coding problems within time limit

  2. 2

    Coding Round One60 min

    This round entirely on problem-solving skills, basic introductions and then two dsa problem

  3. 3

    Coding Round Two60 min

    This round continued with DSA but with slightly different problem patterns

  4. 4

    Low Level Design60 min

    The problem was to design an API that determines whether a product can be delivered within 2 days given a pincode or not Core Logic Design I proposed maintaining a mapping of pincodes to serviceable warehouses. For each pincode query, the system would:

    • Identify the nearest warehouse(s) that stock the product

    • Calculate estimated delivery time based on distance, available logistics partners, and historical delivery data

    • Return whether it qualifies for 2-day delivery Data Modeling: I designed several entities:

    • Warehouse (id, location, pincode, inventory)

    • Product (id, name, warehouseIds)

    • PincodeServiceability (pincode, serviceableWarehouseIds, averageDeliveryDays)

    • LogisticsPartner (id, name, serviceableRoutes, avgDeliveryTime) I suggested using PostgreSQL for transactional data and Redis for caching frequently accessed pincode-delivery time mappings to reduce latency

  5. 5

    Behavioural Round60 min

    The final round was all about cultural fit & understanding how I work in team environment, there was not any technical coding here, conversation revolved around my previous work experiences, challenges I'd faced, and how I handled them.

What came up

MediumRemote4 5 years

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

Sources