← Back to Directory

Booking

Large Enterprises

Booking (Booking.com), part of Booking Holdings, is a leading online travel agency that enables users to book accommodations, flights, car rentals, and other travel services worldwide. It is one of the largest travel technology companies globally, known for its extensive inventory of hotels and lodging options.

3 interview notes · updated Jul 2026

Booking·Software Engineer·Onsite - System Design / Architecture

Jul 2026
System design round at Booking for a software engineering role. The whole session was one big question about logging and telemetry infrastructure, and it went deep fast. Not a bad experience but they really pushed on the operational corners, not just the happy path.
  • Design a logging and telemetry system for a large application platform where many services emit log and metric events, writes are async, and users need real-time query access for debugging and dashboards.

“This one sprawled in every direction.”

View Post

Booking·Software Engineer·Online Assessment (OA)

Jun 2026
Booking's online assessment for the SWE role was 90 minutes, three questions, pretty standard algo stuff plus one problem that felt more domain-specific to what they actually do. Nothing too brutal but the third question had enough moving parts to eat up time if you weren't careful.
  • Given an array of strings, group all anagrams together.
  • Given a non-negative integer, return the maximum value you can get by swapping at most one pair of digits.
  • Given positive and negative keyword lists, a list of hotel reviews each tied to a hotel ID, and an integer k, return the top-k hotel IDs ranked by total sentiment score (ties broken by smaller ID first).

“Classic.”

View Post

Booking·Software Engineer·Technical Phone Screen

May 2026
Booking.com software engineer interview with a data-matching problem that sounds straightforward but has a few wrinkles worth thinking through ahead of time.
  • You have two unsorted lists, one of bookings and one of payments. Each payment record references a booking by ID. For each booking, figure out whether at least one payment exists for it. What does your output look like and how do you approach it?
  • How would your solution change if a single booking could have multiple payment records associated with it?

“The output format question tripped me up more than the logic itself.”

View Post