Susquehanna International Group, Llp (Sig) Software Engineer Interview Guide

The most memorable part of the process was the final system design interview, mostly because one of the interviewers came across as pretty condescending. The questions themselves were reasonable, though, and the overall process was not designed to trick me.

I started with a HackerRank online assessment containing four coding questions that increased in difficulty. The first couple were extremely basic, almost FizzBuzz-level, while the later problems required more substantial algorithmic thinking. The areas that could come up included graphs, dynamic programming, greedy approaches, and breadth-first search. The assessment was roughly 70 minutes, so the main challenge was managing time well enough to reach the harder questions. Nothing about it was specific to quantitative finance.

After passing the assessment, I had a recruiter phone screen. This stage could be fairly detailed about my resume, including my background, interest in SIG, and what motivates me. I also had to be comfortable explaining my experience directly rather than forcing every answer into a STAR story. The screen was around 30 minutes and included four mental math questions that had to be solved without a calculator while talking through my reasoning aloud.

I then moved on to SIG’s Discovery Day. It included a basic behavioral conversation and a technical coding interview. Both felt straightforward, with no unexpected twists or sense that the interviewers were intentionally making things harder. The final stage covered system design and conversations about potential team matches. Aside from the attitude of one system design interviewer, the process was predictable and technically fair. I ultimately did not receive an offer. My biggest takeaway is to prepare for a four-question assessment with a sharp difficulty jump, know every part of your resume well, and practice narrating mental math clearly under pressure.