Real, anonymous reports from people who interviewed for Software Engineer at Tower Research Capital, newest first and distilled into what to expect across the loop.
I got contacted by a recruiter on LinkedIn and ended up exploring Tower Research Capital even though I hadn’t been actively looking. I wasn’t very familiar with the company going in, but the role sounded technically strong and it also made sense because my family was near Montreal. The process started with two virtual coding interviews, and I passed both.
My first interaction was almost entirely coding-focused, with very little framing around the role. There wasn’t a proper introduction or a resume walkthrough—just a coding challenge where I was asked two questions and given about thirty minutes to complete. The emphasis was on how I think using C++.
The interview process typically begins with an online coding assessment, followed by multiple technical phone screens, and culminates in an onsite interview day with several back-to-back interviews. Candidates noted that the scheduling can feel intense and fast-paced, with varying communication about next steps.
Candidates experienced a strong emphasis on coding skills, particularly in languages like Python and C++, with a focus on data structures, algorithms, and system design. Many reported that the coding challenges were challenging and required a deep understanding of technical fundamentals.
Several candidates expressed surprise at the focus on finance-related questions and domain knowledge during the interviews, which were not clearly outlined in the job description. This led to a perception that familiarity with the trading environment was a significant factor in evaluation.
While the technical rounds were predominant, some candidates noted that there were behavioral interviews that assessed cultural fit and soft skills, often framed around past experiences and motivations. The tone of these interviews was generally described as friendly and low-pressure.
Candidates reported a high level of difficulty across the interview process, with many feeling that the expectations for technical depth and breadth were significant. Some experienced pressure during the coding segments, while others appreciated a more conversational approach that alleviated stress.
Many candidates highlighted issues with communication throughout the process, including delays in feedback and a lack of clarity regarding next steps. This contributed to a feeling of uncertainty and frustration for some candidates, impacting their overall experience.