Overall, a difficult-ish experience. Someone with more coding style interview experience may have found this easier than I did. Be prepared to interview in front of more than one interviewer.

Just because a certain question comes up for one person doesn’t mean it will definitely come up for you. Having said that, I still think it’s important to put them on here so it can give people a rough idea of the types of questions and the difficulty being asked.

Round 1: Balanced Arrays (Leetcode 724 - but the Hackerrank version). Round 2: OOP Question - Design a hotel class with search function. System Design: Design Hotel Booking Web Application. Behavioural: Current experience, difference in Java versions, difference between unit testing, integration testing, acceptance testing. How to handle conflicts. Biggest technical challenge faced.

If you put something on your CV, be prepared to REALLY talk about it. Knowing how to calculate Time/Space complexity of a function is extremely important.

Practice questions on both Hackerrank and Leetcode.

There were a couple of books that really helped me:

• System Design Interview - Alex Xu
• CTCI - Don’t be overwhelmed by the size of the book. Just look at it for a few key points or some algorithms you might need a bit more explanation on if you’re stuck.

Don’t sit panicking in the interview. Always be talking; never be silent. Keep talking and discussing; they will appreciate this.

Also, for software engineers, have the IDE and the problem starter kit on your machine ready; they will appreciate you getting this sorted beforehand.

I hope this helps.

See above in the description.