I applied through a recruiter. The process took 5 weeks. I interviewed at Susquehanna International Group (Philadelphia, PA) in Apr 2017
Interview
Initially got a call from their recruiter and followed by Hiring team manager. It was a nice discussion about my experience and some technical questions like binary search and how it is better than linear search. Then in the onsite interview, you get programming assignment for which you are given 1 hour time to code and then technical managers come talk you through the problem. Later another round is about a design problem. They took a lot of time to make a decision like 3 weeks later and decided to pass. Maybe interviewing some other candidates.
Interview questions [1]
Question 1
Which data structure you would choose in place of something which you have used already to make the code efficient?
I applied through a recruiter. I interviewed at Susquehanna International Group (Dublin, Dublin)
Interview
Was pretty easy, 1 round of phone screen interview + 2 - 4 hours of onsite final round. Onsite is scheduled to take place in person in the office.
Interviews were pleasant to talk good and experience was quite good.
I interviewed at Susquehanna International Group in May 2026
Interview
recruiter call - first tech interview, codesignal programming, let u program for 30mins and the interviewer will come back - second tech virtual onsite, OOD + another live coding round, interviewer stays for the duration of OOD and values interaction, live coding is a similar version of prev round - final round onsite team fit, back to back resume deep dive + bq with different engineers / managers. I enjoyed talking to all the engineers and they were genuine and helpful
Interview questions [3]
Question 1
movie sorting problem, different genres search by year
I applied online. I interviewed at Susquehanna International Group
Interview
The OA consists of four LeetCode questions, needed to be done within 70 min. Highly recommend revising how to do the int-string conversion in the language you will use. The problems themselves are not hard, but better to have a clear high-level view before you code.