CV Screening with recruiter. Asked about experience and what I know about trading. The recruiter provided useful information.

Home assessment. Medium assignment (code a simple game) to display your abilities to understand requirements, provide a solution, test your own code, and document decisions. They asked to spend 4 hours, but I did more than that.

1 hour, 1:1 with an Engineer asking general Java / Technical questions to test your understanding of the platform or see how well you explain yourself, e.g., what is a thread? or what happens when you enter a URL in your browser.

2.5 hours - 3 hours Code exercise with 2 higher-level engineers. All the previous steps are important, but this is the real test in my opinion. You get a problem and 30 minutes to read it by yourself alone. Then 1 hour to discuss your understanding and a solution focusing on performance, alternatives, etc. This is similar to what you would have in a day-to-day meeting with your colleagues to discuss how to implement something. The last part of this 3-hour interview is another 1-hour session to actually implement your solution. You are given access to a laptop that already has the tests, and you implement the solution, making them pass.

1 hour Another high-level Engineer, this would be behavioral.

1 hour Another high-level executive who would make the final decision.

I didn't pass the 3-hour session. It was doable, but at this point, I'd been interviewing with multiple companies and doing home assessments and design interviews for over a month, taking weekends to study, etc. So, by the time I got to this interview, I was really tired. Also, because I was interviewing from abroad, it was 7 am my time, and caffeine hadn't kicked in, so I was slow at understanding the problem and providing a solution. I'm also used to coding on a big screen, and having a remote session on a laptop screen wasn't very helpful; there was too much scrolling, and it was easy to get lost. They tell you what environment you're going to use (IDEA), and you can ask to set up your keybindings (e.g., OSX, WIN, or IDEA Classic), so if you practice on a laptop screen, that would be very helpful.

I accept the result. The problem wasn't difficult at all; it's basically implementing 1 method following the rules described and discussed previously. It is NOT LeetCode but something that could be real, e.g., "Let's implement this method in one of our systems; these are the 20 test cases it has to pass." So, again, I could have totally done it if I was more rested and/or focused on just interviewing for IMC instead of applying everywhere.

Unlike everywhere else, they give you a very thorough explanation of where you failed: "Candidate asked this question but failed to understand the answer" or "Candidate tried to implement XYZ, but XYZ was already defined earlier," so I really appreciate the complete feedback.

I don't know what the rest of the other two interviews would've been, but I can tell the more tests you have in green for this one, the better.

I would definitely apply again.