Booking.com Software Engineer interviews typically run 4–5 rounds: HackerRank OA, recruiter screen, hiring manager chat, technical coding, and culture/behavioral. The process moves quickly, often within weeks, and is notable for mixing algorithmic coding with SQL or REST API tasks.
$119K
Avg. Base Comp
$200K
Avg. Total Comp
4-6
Typical Rounds
2-4 weeks
Process Length
Booking.com's software engineering process has a few non-obvious wrinkles that consistently catch candidates off guard. The online assessment is the first real filter, and it's broader than most expect — we've seen candidates encounter sliding window and greedy algorithm problems alongside REST API calls and SQL queries in the same 90-minute window. Passing all test cases isn't enough either; multiple candidates reported clearing the visible tests and still receiving no callback, which tells us the evaluation weights solution efficiency heavily. If your solution works but runs slow, treat it as a failing submission.
The language flexibility advertised in job postings is, in practice, more constrained than it appears. One candidate prepared entirely in TypeScript after the take-home explicitly allowed it, only to be told mid-process that the live coding session required Java. This isn't an isolated complaint — it's worth treating Java as the de facto expected language regardless of what the description says. The live coding prompt we've seen most frequently is an insertion-based cache implementation, with boilerplate already provided. The challenge is getting the logic clean and correct under time pressure, not architecting from scratch.
Perhaps the most striking pattern is how much weight the culture-fit assessment carries — and how early that judgment can be made. One candidate was effectively screened out during a sourcer call when their company size raised concerns about adaptability to a 6,000-person office. The behavioral bar here isn't just about collaboration stories; it's about demonstrating comfort operating at scale. The interviewers are generally described as pleasant, but the process can feel abrupt when things aren't going well, including interruptions during technical explanations and being told to skip edge cases mid-solution.
Synthetized from 3 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Booking.Com process.
I sat down for the technical interview, one hour, one problem. And it wasn't the LeetCode-style grind I'd been preparing for — no dynamic programming, no trick to spot, no clever algorithm hiding under the surface. It was more about actually using a data structure correctly. Knowing its properties, understanding when to reach for it and why, and then working with it properly in code.
Questions asked: The problem gave me a JSON with a discount rate and a list of reservations. I had to find the maximum discount across that list and return the index where it occurred. To do it efficiently, I used a sliding window with pointers — moving through the reservations, maintaining the window, and tracking the best value as I went.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Booking.Com
This problem involves finding the first non-repeating character in a given string. The solution involves iterating over the string and keeping track of the frequency of each character. The first character that has a frequency of 1 is the first non-repeating character.
| Question | |
|---|---|
| The Brackets Problem | |
| Real-Time Transaction Streaming | |
| Resumable Fact Table Load | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Check Matching Parentheses | |
| Combinational Dice Rolls | |
| Targeted sum | |
| Scalable Data Pipelines | |
| Duplicate Product Names | |
| Why Do You Want to Work With Us | |
| Relational Migration | |
| LRU Cache 1 | |
| Hotel Occupancy Prediction | |
| Using APIs for Downstream Tasks | |
| Facebook Autocomplete | |
| Bootstrapping Samples | |
| Flight Modeling | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Delivery Estimate Model | |
| Random SQL Sample | |
| Over-Budget Projects | |
| Raining in Seattle | |
| Employee Salaries | |
| Rectangle Overlap | |
| Weighted Keys | |
| Google Maps Improvement | |
| Nearest Common Ancestor |
Synthesized from candidate reports. Individual experiences may vary.
A HackerRank-based assessment mixing LeetCode-style coding problems (easy to hard), REST API/OpenAPI tasks, SQL questions, and multiple choice questions. Optimization matters — passing test cases alone may not be sufficient for a callback.
A brief call covering motivation for joining Booking.com, current role and responsibilities, and basic culture-fit questions such as team size and familiarity with agile methodologies. Can end early if the recruiter identifies a perceived fit mismatch.
A conversational get-to-know-you round with the hiring manager that serves more as an introduction than a hard technical filter, covering background, experience, and general working style.
A live coding session conducted in Booking.com's online IDE with two engineers, focused on implementing practical data structures (e.g., an insertion-based cache) or medium-difficulty algorithm problems framed in business scenarios covering topics like sliding window, greedy, top-k, two pointers, and DFS. Be prepared to code in Java regardless of what the job posting states.
A round asking candidates to design or extend an existing service, with discussion around architectural decisions such as caching strategies and scalability considerations.
A structured round with general personality and situational questions, including how you handle difficult projects, how you collaborate with others, and a resume review. This round is treated as a distinct filter in the process.