Booking Holdings | SDE-II | BLR | Reject

Hi Folks,

YOE : 6.5

Recently gave the OA of Booking Holdings for Marketplace team.
Applied through multiple methods: Referral, Instahyre, Cold email.

Platform: Hackerrank
No. of questions : 3
Time Limit : 90 min


Screenshot 2025-11-01 at 6.08.20 PM.png

Screenshot 2025-11-01 at 6.08.12 PM.png
Screenshot 2025-11-01 at 6.08.41 PM.png
Screenshot 2025-11-01 at 6.08.48 PM.png


R-1: Coding Round

Interviewer was from Fintech Platform team.
Time: 60 min
(I have faced this question before, hence, was very happy 😁 )

An abstract problem statement about credit card limit and authorize & capture transactions was shared and based on the question, there were certain business rules given.
The idea was to write code to support the validations and see if the type of transaction could be processed or not.
Status: Cleared.


R-2: System Design

2 Interviewers (both SE-2) from Fintech team. Time: 60 min

Q: You have 1B customers on Booking.com and 1% of them are "genius". A "Genius" customer is someone who makes atleast 2 bookings and completes it in last 2 yrs.
Scope of this design is to compute the flag, store it, and serve it to frontend so that it is available throughout the logged in context.
The flag needs to be made available near real-time.
We'll need to re-evaluate his "genius" offer after 2 years again.

Constraints:

  1. We're not bothered about how the reservation/booking is done. Reservation system is a black-box to you.

Additional Scope:

  1. Later on, we would move from a genius boolean flag based system to a tier based system: BRONZE (2 stays in 2 yrs), SILVER (5 stays in 2 yrs), GOLD (10 stays in 2 yrs). Both upgradation and downgradation of tiers are in scope.
    ^ This can be done using Sliding Window.

This was the design that I proposed:
image.png

Received feedback that this was over-engineered along with a rejection mail.


#booking.com #bookingholdings #oa #sde2

Comments (13)