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.
The first thing I hit was an online assessment on HackerRank, and it was a pretty mixed bag: one LeetCode-style coding problem, one task where I had to make an OpenAPI call and filter the results, and then a fairly complicated SQL question. That set the tone for the rest of the process, because it felt like they were checking both general problem-solving and whether I could work comfortably with APIs and data. After that, I had a screening call with a sourcer that was scheduled for 30 minutes, but it wrapped up in about 7 minutes. She went straight into the usual questions about why Booking and what my day-to-day work looks like, then asked whether I currently work in an agile methodology. I explained that we have two meetings a week but not daily stand-ups, so I wasn’t sure I’d call it strictly agile. She then asked how many people work at my current company, and when I said fewer than 20, she told me Booking has around 6,000 people in the Amsterdam office and said she didn’t think I’d be able to adapt to that environment. She also said that even if I passed the technical rounds, I would very likely fail the culture-fit round, and suggested ending the conversation there. It was a pretty abrupt end to what was supposed to be a longer call.
Prep tip from this candidate
Be ready for a HackerRank OA that combines coding, OpenAPI filtering, and a fairly involved SQL problem. If you get past that, expect a recruiter screen that can move quickly and includes direct questions about agile experience and whether you’re used to a large-company environment.
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 | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Check Matching Parentheses | |
| Combinational Dice Rolls | |
| Targeted sum | |
| Why Do You Want to Work With Us | |
| Relational Migration | |
| Duplicate Product Names | |
| LRU Cache 1 | |
| Hotel Occupancy Prediction | |
| Facebook Autocomplete | |
| Bootstrapping Samples | |
| Flight Modeling | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Delivery Estimate Model | |
| Random SQL Sample | |
| Raining in Seattle | |
| Employee Salaries | |
| Weighted Keys | |
| User Experience Percentage | |
| P-value to a Layman | |
| Nearest Common Ancestor | |
| Maximum Profit | |
| Permutation Palindrome | |
| Rectangle Overlap | |
| Download Facts | |
| Google Maps Improvement |
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.