Expedia Machine Learning Engineer interview questions

5 Machine Learning Engineers have shared notes from their Expedia interviews, with the questions they were asked in each round. That is 14% of the 36 Expedia interview notes on Screna AI.

5 Machine Learning Engineer interview notes

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

Jun 2026
System design round at Expedia for an MLE role, focused entirely on building a text-to-image generation service from scratch. It was a long 45-ish minutes and the scope kept expanding every time I thought I'd covered enough ground.
  • Design a text-to-image generation service similar to DALL-E or Midjourney. Walk through the full system from user prompt submission to returned images.
  • How would you design the async API for image generation, including how clients know when their job is done?
  • How would you manage and scale a GPU inference fleet to handle diffusion model workloads efficiently?
  • How would you handle model versioning and run A/B tests across different versions of a diffusion model?
  • What does a safety pipeline look like for a system like this, covering both prompt filtering and output moderation?
  • How would you optimize costs in this system, especially given the expense of GPU inference at scale?
  • How would you handle abuse prevention and rate limiting for a public-facing image generation API?

“I started with the API layer and worked outward, which in retrospect was fine but I spent too long on the happy path.”

View Post

Expedia·Machine Learning Engineer·Technical Phone Screen

May 2026
First round for an MLE role at Expedia, basically a notebook-based case study centered on LLMs. The skeleton was already there so you're not starting from scratch, but you still have to implement the real pieces yourself.
  • Given a pre-built LLM training framework in a notebook, implement a tokenizer along with word-to-token and token-to-word conversion functions.
  • Write an optimizer and a loss function for the training loop, then verify the loss decreases over iterations.

“Having the framework handed to you sounds like a relief until you realize the tokenizer is actually the part that needs to work correctly for everything downstream.”

View Post

Expedia·Machine Learning Engineer·Technical Phone Screen

Apr 2026
ML system design round at Expedia where you pick a product, find the ML-worthy problems in it, and then basically walk through the entire lifecycle from problem framing to deployment. Pretty open-ended, which I was not fully prepared for.
  • Given a specific product at Expedia, how would you identify which problems within it are actually good candidates for an ML solution?
  • How would you define the ML task for this product, including inputs, outputs, and how you'd source or construct labels?
  • What model class and feature signals would you choose, and why?
  • Walk me through how you'd design the training and evaluation pipeline for this system.
  • How would you decide on online versus offline metrics, and how would you set up an A/B test to validate the model in production?
  • What deployment trade-offs would you consider when taking this model to production?

“I jumped straight into listing ML techniques before really justifying why ML was even needed, which felt backwards in hindsight.”

View Post

Expedia·Machine Learning Engineer·Technical Phone Screen

Apr 2026
One round at Expedia for an ML Engineer role, basically just a walkthrough of my own projects. Pretty low-key as far as technical screens go.
  • Walk me through a project you've worked on recently. What was your role and what technical decisions did you make?

“They just wanted me to talk through my own work, which sounds easy until you're actually doing it live and second-guessing every detail you mention.”

View Post

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

Apr 2026
System design round at Expedia for an ML Engineer role, focused almost entirely on building a large-scale event pipeline end to end. It went deep fast and covered a lot of ground.
  • Design a data pipeline that ingests events from multiple upstream producers, transforms them, and delivers them to analytics-ready storage. Walk through your full architecture.
  • How would you handle schema evolution in a high-throughput streaming pipeline without breaking downstream consumers?
  • Walk me through the tradeoffs between stream processing (e.g. Flink) and micro-batch approaches (e.g. Spark Streaming) for this kind of pipeline.
  • How would you design for backfills when your pipeline has already been running in production for months?
  • How do you ensure data quality and handle bad or malformed events at scale?
  • How would you approach observability and lineage for a pipeline like this, and what does a meaningful SLA look like?
  • What's your strategy for managing cost and scaling as event volume grows by an order of magnitude?

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

View Post