← Expedia Interview InsightsSoftware Engineer

Expedia·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
May 2026

Summary

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.

Questions Asked (1)

Q1

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.

System DesignAPI & IntegrationsTechnical Trade-offs
Author's notes

This is a meaty one.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then outline the high-level architecture and request lifecycle before diving into API details. Structure your answer around the three deliverables: API spec, lifecycle flowchart, and scaling strategy, ensuring you cover both functional and non-functional aspects. Use a whiteboard-friendly approach to sketch the flow and justify design decisions with trade-offs.

Pro tip: Emphasize idempotency and asynchronous processing for long-running validations, and discuss how you'd handle partial failures and retries to ensure reliability. This shows you understand real-world integration challenges beyond just the happy path.

1. Clarify Requirements and Scope

Ask questions to understand expected request volume, latency requirements, validation complexity, and provider authentication needs. Confirm whether validation is synchronous or can be asynchronous, and identify any compliance or data residency constraints.

2. Design High-Level Architecture

Propose a layered architecture: API gateway for auth/rate limiting, connectivity service for orchestration, and integration with internal validation domain via REST or messaging. Consider using a queue for decoupling and resilience.

3. Define REST API Specification

Specify endpoints (e.g., POST /listings, GET /listings/{id}/status), request/response payloads (JSON schema), required headers (Authorization, Content-Type, Idempotency-Key), and status codes (202 for accepted, 400 for bad request, 401/403 for auth, 409 for conflict, 429 for rate limit, 500 for server error).

4. Map Request Lifecycle

Describe the flow: provider sends request -> API gateway authenticates and rate limits -> connectivity service validates payload and persists request -> forwards to validation domain (sync or async) -> receives result -> updates status and notifies provider via callback or polling. Include error handling and retry logic.

5. Discuss Scaling and Trade-offs

Explain horizontal scaling of stateless services, database sharding, caching, and use of message queues for load leveling. Discuss trade-offs between sync vs async validation, consistency vs availability, and cost implications.

Key Points to Mention

  • Idempotency: Use Idempotency-Key header to prevent duplicate listing creation on retries.
  • Asynchronous processing: Return 202 Accepted with a status URL for long-running validations to avoid blocking provider.
  • Error handling: Define clear error response format with error codes and messages, and implement retries with exponential backoff.
  • Security: OAuth 2.0 for provider authentication, TLS, and input validation to prevent injection attacks.
  • Scalability: Stateless services, horizontal scaling, database read replicas, and queue-based load leveling.
  • Monitoring and observability: Logging, metrics, tracing, and alerting for request latency, error rates, and queue depths.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.