Susquehanna International Group Interview Questions
& Process

The interview process started with a Capital Markets Skills Assessment that covered EV/Finance/Market Q's and Math. Then there was a 45-minute Recruiter Call where they asked behavioral questions, about a stock pitch, and a probability question. After that, I had to submit a video stock pitch. Finally, there was a 90-minute video interview focusing on market scenarios and quantitative reasoning.

The interview process was very aggressive on both behavioral and technical fronts. I was asked an options trading question involving different probabilities. The technical part was particularly aggressive with many follow-ups. In total, there were three technical questions, with further follow-ups if they deemed it necessary. They also followed up on behavioral questions, so it's crucial to be truthful and prepared.

5 rounds over 2-3 months, very slow process. First an OA with 17 Math and probability Qs in about an hour. Then a 45 min call with HR for a vibe check and 3 probability/ expected value Qs. After that, an interview with a Trader, 1 hour long, with harder probability Qs and a vibe check at the end. Then a take home project, 48 hours to analyze a sequence of trades made and come up with a strategy in any language. Final round was an on site interview with a trader and HR member, good cop bad cop style. Lots of expected value Questions and market making games based on estimated fair value of a game.

I went for a C# SWE role, I have 4 years of experience. A recruiter hit me up on LinkedIn. First, I talked to the recruiter, then had a 90-minute technical interview over Zoom, followed by a 3-hour technical interview also on Zoom. The recruiter called me back after the technical rounds. All the coding was done on CodeSignal. It was a bit unusual; instead of staying on the call, they let you leave for 30 minutes after explaining the problem to implement the solution, and then they'd come back to review it. They always ask a lot of follow-up questions about optimizing and adapting the solution to different scenarios. The first technical round involved a movie catalog search problem. They provided objects and started with a list, and the task was to improve it using hash map indexing. There were some follow-up questions about caching, and this round was relatively easy. The second round was tougher and split into two parts. Part 1 was a trie problem, which is quite challenging to solve in 30 minutes unless you're well-practiced; you need to implement building and searching a trie. The interviewer attempted to assist, but the code snippets they provided didn't work, making recovery impossible. It was ironic that the interviewer couldn't solve their own question. I think failing this part is why I was rejected. Part 2 was more of a pseudocode design session with a different interviewer who stayed on the call the entire time. They wanted me to create an order book for stock asks and bids. We spent the whole time discussing different data structures for high-speed searching, focusing on optimization for various factors like binary search, tries, min heaps, and hash maps, along with pointers. We discussed the Big O notation for each data structure. Out of the three engineers I spoke with, only one was actually on the team I applied for, which made it difficult to get accurate information since the teams operate independently. Additionally, taking three hours out of a workday is always inconvenient.