GTS Interview Questions
& Process

The process included a coding assessment and several discussions with team members. It covered topics ranging from math to trading or coding. The team was pleasant to interact with. The entire process spanned two to three months.

The online assessment was really tough, covering a lot of computer science concepts and multiple hard LeetCode problems. The math part wasn't that difficult. Honestly, I thought it was a bit over the top for a trading role, even with the focus on systematic trading. Some of the questions felt like they were only answerable by someone with a CS major background.

First, there was an initial interview to check my experience and see if I met the basic requirements. After that, I had a take-home lab where I had to configure a network with some basic functionalities, including a routing protocol and multicast. Finally, I had a meeting with seniors to go over my networking knowledge.

I applied through a third-party recruiter. First, there was a phone call with an internal recruiter at GTS where they asked why I was looking for a new job, why GTS, and explained the process. The first round was a 4-hour take-home test, not a typical Leetcode challenge, but more of a systems programming and C++ skills test relevant for HFT. I passed and heard back within a day. GTS is quick with feedback. The second round was a video interview with two interviewers. They discussed my C++ experience and asked some C++ questions. Then, each interviewer gave me either a Leetcode-style problem or a design problem to solve in C++, requiring compiled and passing code. I passed this and was scheduled for the onsite. The onsite was split into two parts. Onsite Part-I had three rounds via Microsoft Teams. Round 1 was with a senior engineer discussing the firm, its teams, and basic algorithmic theory, like sorting algorithms. Round 2 involved implementing an API based on a graph model, with the interviewer running simulations to check for bugs and seeing if I could fix them. Round 3 focused on C++ and Leetcode problems, where the interviewer probed my understanding of C++ STL features and performance implications. All solutions were compiled and tested. I passed this part and scheduled the final two rounds. Onsite Part-2 Round 1 was an algorithms screen with a hard Leetcode problem, requiring significant hints and time to reach an optimal, working solution with passing tests, plus C++ follow-ups. Round 2 was a discussion with an engineering team lead about market access teams, roles, my interests, and programming/design philosophies, along with personality and behavioral questions. I was informed the next day that I didn't get an offer because I wasn't technically strong enough, which I felt was a valid decision due to my performance in the design/bug fixing round and the algorithms round where I needed many hints and went over time. Overall, interviewing with GTS was fun, with good interviewers and fast feedback, better than most trading firms.