The interview started with a basic technical phone screen by a team member. This involved basic, FizzBuzz-esque questions about Unix/Linux (covering basic commands, reading files, troubleshooting, and seeking help via man pages), discussions about your experience, and time for you to ask questions.

Next was a coding screen conducted by a team member through Coderpad. You don't need OCaml for this; you can use any language you're comfortable with. This interview also began with a FizzBuzz-esque question. However, after solving the initial problem, the interviewer introduced new layers to increase the difficulty. The primary focus of this interview is likely writing clean code, discussing your plan with the interviewer beforehand, and then implementing that plan. Asking for help or hints is not a major issue, as the ability to talk through the problem to a solution is more important. Optimize only if you have extra time and have demonstrated that the original solution works.

Then came the on-site interviews. There were three interviews with the Trading Systems team and several developers, typically with two team members present for each. These included a coding interview, a command-line question, and an interview where you were introduced to a new module or expression parser (?) and tasked with solving a problem using it.

Again, none of the individual interviews were inherently difficult. For the coding interview, it was more important to outline a clear plan before writing code. For the other two interviews (CLI and parser), try out different commands to understand the system and communicate your thought process effectively with the interviewers.

There's no need to cram LeetCode problems; it's better to practice walking through problems with a friend. Everyone seemed nice and very smart.

(Screening question) How do you kill a process?