I was interviewed a couple of weeks after completing the OA. As others mentioned, submitting the first two questions was sufficient to pass the OA. I also completed part of the fourth question.

The actual interview was scheduled two weeks later and was broken down into four parts:

1. System Design: This was my first time tackling system design, and I was very unprepared. I could barely answer the questions, and I felt my chances were over after this section. The question was to design a banking app capable of handling transactions. I recommend understanding High-Level Design (HLD) and then selecting a specific technology, explaining your reasoning. Don't just guess. For starters, I suggest reviewing the "credit card" discussions on LeetCode.

2. Coding Interview: I was prepared for a LeetCode-style interview, but instead, it was an object-oriented programming (OOP) question divided into three interconnected parts. The task was to design an implementation for creating user accounts, storing all their transactions, facilitating transfers between accounts, and calculating the sum of all transactions for specific accounts (these requirements were presented in stages). A key tip is to ensure you store all transactions. I managed to answer two out of three parts and ran out of time on the last one, which wasn't overly difficult. I recommend looking up "create-a-banking-system" on Exponent.

3. Case Study: I didn't study much for this. It involved some data and code analysis, as others have noted. It wasn't too bad; just think critically.

4. Behavioral: These were standard questions, such as:

   • A time you disagreed with a coworker or manager.
   • A time priorities shifted.
   • A time you had to learn something new for a task.

Good luck!

Time you disagreed with a coworker or manager. Time priorities shifted. Time you had to learn something new for a task. Good luck.