Booking.Com software engineer candidates commonly report an assessment or recruiter screen, then coding, system design, and behavioral evaluation. Prepare for reservation-themed algorithms, practical Java coding, and product-aware design trade-offs.
$113K
Avg. Base Comp
$171K
Avg. Total Comp
3 rounds
Typical Rounds
2-4 weeks
Process Length
Booking.Com Software Engineer candidates describe a process that often moves from an online assessment or recruiter conversation into coding, system design, and behavioral evaluation. Treat the exact sequence as variable rather than fixed. One candidate reported three interviews, while another completed an assessment followed by a combined coding and system-design round.
Coding is sometimes framed around Booking.com-style reservation data. Reported tasks include a sliding-window challenge, finding a maximum discount in reservation JSON, and implementing an insertion-based cache in an online IDE. One candidate was required to code in Java even though the earlier assessment had allowed another language, so confirm the permitted language and be ready to implement and explain a clean solution under time pressure. Another assessment combined a coding problem with OpenAPI filtering and SQL.
For system design, candidates reported a live hotel-viewer popup, a near-real-time transaction and reporting system, and a cab-sharing application. Be ready to clarify requirements and discuss relevant trade-offs such as scale, retries, duplicate handling, bottlenecks, and data-store choices. Behavioral discussions included background and past projects, motivation for Booking.com, agile experience, and handling a difficult project. The supplied reports do not establish one universal timeline or round count.
Synthesized from 9 candidate 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.
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 | |
| Ride-Sharing App Schema | |
| Check Matching Parentheses | |
| Combinational Dice Rolls | |
| Targeted sum | |
| Scalable Data Pipelines | |
| Duplicate Product Names | |
| Relational Migration | |
| Why Do You Want to Work With Us | |
| LRU Cache 1 | |
| Stories Success | |
| Hotel Occupancy Prediction | |
| Using APIs for Downstream Tasks | |
| Facebook Autocomplete | |
| Bootstrapping Samples | |
| Flight Modeling | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Bagging vs Boosting | |
| Random SQL Sample | |
| Rolling Bank Transactions | |
| Raining in Seattle | |
| Over-Budget Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either an initial HackerRank or LeetCode-style assessment, or a recruiter-led conversation about the role, resume, motivation, daily work, agile experience, and company environment. One assessment combined coding, OpenAPI-result filtering, and SQL; another candidate described three standard assessment questions.
Candidates commonly report practical coding around booking or reservation data, including a rolling seven-day average or a sliding-window variation. Other reported tasks include implementing an insertion-based cache and working with a JSON list of reservations. One live session lasted about 90 minutes, while another lasted one hour.
Candidates report system-design prompts such as a hotel-booking system, a feature showing how many people are viewing a hotel, a near-real-time transaction and reporting system, and a cab-sharing application. Discussion may cover requirements, scaling, bottlenecks, retries, duplicate handling, queues or APIs, and data-store trade-offs.
Candidates report behavioral or manager conversations covering background, past projects, conflict with a disagreeing peer, a difficult project, product-mindedness, and measuring user behavior for a feature. Some accounts place this alongside coding and system design, while one candidate did not continue to it.
