← Back to Directory

Expedia

Large Enterprises

Screna has 19 Expedia interview write-ups. The most reported round is the technical phone screen (11).

19 interview notes · updated Jun 2026

Expedia·Software Engineer·Technical Phone Screen

Jun 2026
Expedia coding screen, one algorithmic problem about rearranging an array so no two adjacent elements are the same. Pretty standard for this type of role but the constraint makes it trickier than it looks at first glance.
  • Given an integer array, rearrange it so that no two adjacent elements are equal. A valid arrangement is guaranteed to exist. Return any valid result.

“My first instinct was to just sort and interleave, which works but I fumbled explaining why it works.”

View Post

Expedia·Software Engineer·Hiring Manager Screen

Jun 2026
Hiring manager behavioral round for a software engineering role at Expedia. Three questions, all pretty standard on the surface, but the accountability one has a specific angle that'll trip you up if you're not ready for it.
  • Why do you want to work at Expedia, and why this team specifically?
  • Tell me about a project you're most proud of. What was your specific contribution?
  • How do you hold yourself accountable on a team? Specifically, how do you keep projects on schedule and what do you do when someone else is blocking your progress?

“Prepared something for this but it felt a bit thin in the moment.”

View Post

Expedia·Software Engineer·Technical Phone Screen

Jun 2026
Expedia software engineer interview that looked deceptively simple on the surface. They paste a JSON blob into the editor and suddenly you're not just parsing it, you're defending every design decision you make along the way.
  • Given a large JSON string pasted into the editor, write code to parse it and extract specific fields. You can use any language or library you want.
  • Once you've parsed the JSON, how would you model the data? Walk through the tradeoffs between typed DTO classes and raw maps.
  • How do you handle missing or optional fields, type mismatches, and malformed JSON in your parsing logic?
  • Can you discuss streaming parsers versus full deserialization for very large JSON payloads, and when you'd choose one over the other?
  • How would you implement a JSON parser from scratch using recursive descent, and what are the time and space complexity bounds?
  • How would you write tests for the JSON extraction logic?

“I went straight for the one-liner deserialization and it felt like a trap the moment I finished typing.”

View Post

Expedia·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Expedia for a software engineering role. The main problem was designing a synchronous order cancellation and refund processor, which sounds contained but ends up touching a lot of moving parts fast.
  • Design a synchronous order cancellation and refund processor. The API must return a definitive success or failure only after the cancellation and refund are fully resolved, not fire-and-forget. Walk through validating order state, issuing the refund via a payment gateway, updating order/payment/inventory atomically, and staying within acceptable latency.
  • How would you handle partial failure in this system, specifically when the refund succeeds at the payment gateway but the database update then fails?
  • How do idempotency keys make retries safe in this refund flow, and where exactly do you enforce them?
  • Compare using a distributed transaction versus a saga with compensation for coordinating the refund, order update, and inventory update. Which would you choose and why?
  • How would you apply timeouts and circuit breakers around the payment gateway calls in this synchronous flow?
  • Why would a team choose a synchronous cancellation flow over an asynchronous one, and what are the trade-offs?

“This one sprawled in ways I didn't anticipate.”

View Post

Expedia·Machine Learning Engineer·Technical Phone Screen

Jun 2026
One round at Expedia for an ML Engineer role, basically just a project walkthrough where they had me talk through my own work. Pretty low pressure but also hard to gauge how well you're doing when there's no clear right answer.
  • Walk me through one of your recent projects in detail.

“I talked through a model I'd built and it went fine until they started asking follow-up questions I hadn't prepared for.”

View Post

Expedia·Software Engineer·Technical Phone Screen

May 2026
Expedia software engineer interview with a sliding window / prefix sum problem. Pretty standard coding round, nothing too wild, but the two-approach angle made it more interesting than I expected.
  • Given an integer array and an integer k, count the number of contiguous subarrays that contain exactly k odd numbers.

“I went straight for the prefix sum approach, which worked, but I fumbled explaining why it was correct.”

View Post

Expedia·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
System design round at Expedia for an MLE role, focused almost entirely on building a large-scale event ingestion and transformation pipeline. It went deep fast and covered a lot of ground, more like a data engineering interview than anything ML-specific.
  • Design a data pipeline that ingests events from many upstream producers, transforms them, and delivers them to analytics-ready storage. Walk through the full system end to end.
  • How would you handle exactly-once delivery semantics across the pipeline, and where would you relax that to at-least-once and why?
  • How do you approach schema evolution in a high-throughput event pipeline without breaking downstream consumers?
  • Walk me through your storage layer choices, specifically around table formats and the tradeoffs between options like Iceberg, Delta, and Hudi on top of object storage.
  • How would you design the observability and data quality layer for this pipeline, including SLA monitoring and handling bad data?
  • How do you think about cost optimization and scaling for a pipeline processing millions of events per second?

“This was the main question and it basically ate the whole session.”

View Post

Expedia·Software Engineer·Technical Phone Screen

May 2026
Expedia coding round, one problem the whole session. It was a backtracking question dressed up with a quirky digit constraint and I spent more time second-guessing the range than actually coding.
  • Given a string of digits and '?' wildcards (e.g. '08??840') and a target digit sum, replace each '?' with any digit from 0 to 8 and return all resulting strings whose digits sum to the target.

“The 0-8 range tripped me up.”

View Post

Expedia·Software Engineer·Onsite - System Design / Architecture

May 2026
Expedia system design round for a software engineer role, focused entirely on building a middleware-style 'Connectivity' service that sits between external listing providers and an internal validation domain. Pretty involved question with multiple deliverables expected in one session.
  • Design a 'Connectivity' service for an OTA platform that accepts listing-creation requests from external providers, forwards them to an internal validation domain, and returns results back to the provider. Deliverables include a full REST API spec with endpoints, payloads, status codes, and required headers; a request lifecycle flowchart; and a discussion of how to scale the service.

“This is a meaty one.”

View Post

Expedia·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Expedia focused entirely on building a disaster notification system for a vacation rental platform. Pretty deep dive, lots of back-and-forth on geospatial indexing and how to handle scale.
  • Design a natural disaster notification system for a vacation rental platform. Given a disaster event with affected geographic regions, how do you efficiently identify all impacted properties, orders, hosts, and guests, and notify them within an acceptable time window?
  • How would you model and index property location data to support fast geospatial queries at scale, and what are the tradeoffs between approaches like R-tree, S2, and geohash?
  • How do you design the system to handle many concurrent disaster events without degrading notification latency or overwhelming downstream services?

“I jumped straight into the notification pipeline and the interviewer had to pull me back to talk about how I'd even find the affected properties in the first place.”

View Post

Expedia interview guides by role

16 notes

Expedia Software Engineer interview questions