First stage was a bunch of hackerranks which Im 100% sure people cheat on, was grinding them recently so I passed without cheating.
Second stage was the technical interview with a person that speaks poor english, wants you to implement caching, and will ask one of those "what if" questions that never occur in real life. Also, you will need to know random syntax from the top of your head.
One mistake, even small = you are out.
Even if the recruiter is wrong. Good luck lmao.
Very kind. The questions weren’t easy, but with knowledge of database configurations, concurrency, locks, and some practical experience, you are able to answer them clearly, confidently, and effectively overall. It was good time.
Recruiter round, they’re basically looking for buzz words. They asked for my experiences in handling different scenarios, then other db and concurrent related questions . Overall it was straightforward, just go through other’s experiences here and you should be covered
Interview questions [1]
Question 1
Concurrency
Optimistic vs pessimistic locking
Db isolation levels
HR interview, coding interview, then system design interview. No specific feedback from them. I really thought I went well and answered everything at least reasonably, but didn't get an offer.
Interview questions [1]
Question 1
Design Revolut Stays. Hotel info comes from an external partner. Bookings must be done through the external partner as well.