Interview started with a basic technical phone screen by a team member. Basic, fizzubzz-esque, questions about Unix/Linux (know basic commands, reading files, how to troubleshoot and seek help like man pages), talk about your experience, ask questions. Then there was a coding screen by a team member done through Coderpad. You don't need OCaml for coding, just pick the language you are comfortable in. Once again, the interview starts with a fizzbuzz-esque question. However, this time after solving the first problem, the team member provides new layers to the problem to increase the difficulty. The main point of this interview is probably just writing clean code, talking first with the team member about your plan, and implementing that plan. Asking for help/hints isn't a huge issue since it's more important that you can talking through the problem into a solution - worry about optimizing if you have extra time and showed that the original solution actually works. Then came the on-site. It was 3 interviews with the Trading Systems team and a few devs - typically 2 team members for each interview. There's a coding interview, a command line question, and an interview where you are introduced to a new module/expression parser (?) and need to solve a problem using it. Again, none of the interviews were hard in themselves, more important to outline a clear plan before coding for the coding interview. For the other two interviews (cli and parser), make sure to try out different commands to figure out the system and communicate with the interviewers well about your thought process. Don't need to cram leetcodes, better to just practice walking through a problem with a friend or something. Everyone seemed nice and very smart.