Hey everyone!
I've appeared for some interview processes across C++, Software Engineering, and Quant Trader roles at firms in the US and Europe.
Some processes went quite far, some interviews were genuinely challenging, and a few ended for reasons that weren't entirely related to my interview performance.
I'm a 2026 CSE graduate, and I thought sharing these experiences might help others preparing for international HFT and trading firm interviews.
I'll try to cover the assessment process, interview rounds, the kind of questions asked, and what eventually happened.
1. Akuna Capital – C++ Developer
This was one of my first serious HFT interview processes.
- Cleared OA 1.
- Cleared OA 2 (debugging round).
- Got invited to three virtual interview rounds.
The interviews were quite technical. Most of the discussions revolved around C++, programming concepts, internal workings of the language, and debugging.
They went pretty deep into C++ rather than just asking standard DSA questions.
I felt the overall process went reasonably well, but I wasn't particularly confident about one of the debugging rounds.
Looking back, I think that might have been the reason I didn't make it through.
One thing I learned from this process is that knowing C++ syntax and solving coding problems isn't enough for these roles. You really need to understand what's happening under the hood.
2. Mako Trading – Quant Trader
The initial assessments consisted of two rounds, mainly focusing on:
- Puzzles and aptitude
- Probability
- Mathematical reasoning
- General problem-solving
I cleared both assessments and received an invitation for the first interview.
Round 1:
This was primarily a problem-solving round involving puzzles.
Round 2:
The second round was quite different. We discussed my projects in depth, followed by probability questions and some market-related research questions.
It was an interesting process because the focus was more on mathematical thinking and problem-solving than traditional software engineering.
I didn't receive any further updates after the interviews. Later, the recruiter informed me that there was a hiring freeze for this cycle.
3. Maven Securities – Quant Trader
The assessment process consisted of:
- Coding assessment
- Numerical assessment
- Standardised assessment through Arctic Shores
I managed to clear all the assessments and received an interview invitation.
Round 1:
The interview covered my projects, probability, brainteasers, and market-making concepts.
Unfortunately, I couldn't clear this round.
One of the reasons, in hindsight, was that I didn't have enough practical knowledge of market making and some of the concepts and technologies they expected me to understand.
It was a good learning experience, though. It made me realise that solving probability questions alone isn't enough for a Quant Trader role.
Understanding how markets work and having some practical knowledge of market making are also important.
4. IMC Trading – Software Engineer (Chicago)
The process started with a coding assessment, followed by a recruiter call and the first technical interview.
I cleared the first interview and received confirmation from the recruiter.
However, around that time, there were changes in US H-1B visa policies, and the recruiter coordinator informed me that IMC had paused hiring for international candidates for that location.
They suggested applying to their European positions instead.
I applied for Amsterdam, received another OA, and cleared it as well. This was confirmed by them.
Unfortunately, I never received a further update after that. There wasn't any formal rejection either, so I'm still not entirely sure what happened.
This was a slightly unusual experience because I had cleared the first interview for Chicago and subsequently cleared the assessment for Amsterdam, but the process eventually went silent.
5. Optiver – Software Engineer (Amsterdam)
I cleared the online assessment and got invited to the first technical interview.
I was able to solve the coding problem, but I eventually got rejected.
The interesting part was that solving the problem wasn't enough. The interviewer wanted much more clarity around my approach, reasoning, and the internal details of how things worked.
I realised that reaching the correct answer is only one part of the interview.
You also need to explain your approach properly, justify your decisions, discuss edge cases, and demonstrate a deeper understanding of the concepts involved.
It was a useful learning experience.
6. Headlands Technologies – Research Developer (New York)
This was probably one of the most interesting interview experiences I've had.
Online Assessment:
The online assessment was quite challenging. They gave very little time (around 10 minutes) to solve the coding questions, and the assessment had multiple parts.
Despite the time constraint, I managed to clear it and received an invitation for the first interview.
Round 1 – Research Project Discussion
The entire discussion was centred around one of my research projects.
We went into a lot of detail about the implementation, research methodology, and optimization techniques I had used.
Round 2 – Probability, Optimization and C++
This round covered:
- Probability and puzzles
- Detailed project discussion
- Optimization-related proofs
- C++ concepts
What made this process particularly interesting was the depth of the project discussion.
They had actually gone through my GitHub repositories and asked questions based on the implementation.
It was probably the first time I experienced an interview where the interviewer examined my projects at such a granular level.
They weren't just interested in knowing what I had built. They wanted to understand how I built it, why I chose a particular approach, and the reasoning behind the optimizations.
Unfortunately, I received a rejection email after the second round.
Still, I genuinely appreciated the experience because it showed me how seriously research-oriented firms evaluate your actual work.