Tower Research Capital Software Engineer interview typically runs 5 rounds: online assessment, virtual coding interviews, and onsite technical interviews. Timeline is about 1-2 weeks, with a calm but coding-heavy process.
$118K
Avg. Base Comp
$225K
Avg. Total Comp
4-6
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Tower Research Capital is less interested in polished theory than in whether you can reason cleanly through real engineering trade-offs under time pressure. A recurring theme is the mix of language fundamentals and practical design judgment: Python edge cases, C++ implementation details, OOP, data storage, and schema thinking all show up alongside puzzle-style coding. One candidate specifically noted that the interviewers were friendly and willing to let mistakes slide if they were corrected thoughtfully, which suggests they are watching for composure and recovery as much as correctness.
We’ve also seen that Tower tends to reward engineers who can move beyond isolated algorithm drills and talk through how a system would actually work. Candidates described prompts like designing a service and database schema, building a file system, and discussing smart pointers and design patterns in C++. That combination points to a company that values hands-on implementation depth over abstract architecture talk. The non-obvious part is that even when the conversation feels calm, the bar is still quite specific: they seem to probe whether your choices are grounded in production reality, not just whether you can arrive at an answer.
Another pattern worth noting is the mismatch some candidates felt between expectations and what actually happened in later conversations. One experienced engineer expected more senior-level system design and scalability discussion, but instead encountered more basic, tricky coding questions. That tells us Tower may calibrate heavily on fundamentals even for experienced hires, so candidates who assume the process will automatically become high-level can get caught off guard. The strongest signal here is simple: they want engineers who can explain their thinking clearly, defend implementation choices, and stay precise when the questions get deceptively small.
Synthetized from 2 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tower Research Capital process.
I wanted to share my interview experience with Tower Research Capital in Montreal because the process caught me off guard in a few ways. A recruiter reached out to me on LinkedIn, and even though I was not actively job hunting, the role sounded strong enough that I decided to explore it. I already work at a major bank in the U.S., so the main reason I kept going was personal: I have family near Montreal, and the possibility of being closer to them made the move worth considering.
The process started with two virtual coding interviews, and I passed both. After that, I was invited to Montreal for what I understood would be five in-person interviews, each about an hour long. Based on that, I expected the onsite to shift toward more senior-level topics like system design, architecture, scalability, or production experience. Instead, after waiting in a conference room, I was told the first interview would actually be virtual. That was already a little confusing since I had traveled for an onsite. The first interviewer opened with a very basic but tricky Python question, which made me think the rest of the round would stay in that style. The second interviewer was much better from my perspective and gave me a more realistic engineering problem, closer to what senior engineers deal with in practice. I solved that one and felt much more comfortable there.
What stood out most was that after the second interview, the remaining three interviewers never came out to speak with me. By then I had the feeling the first round had already set the tone, and that the rest of the process had effectively stopped. I left feeling like the interview was more about isolated tricky coding questions than about evaluating the broader experience I would bring as a senior engineer. I had already made real trade-offs to be there, including travel and salary expectations, so the mismatch was disappointing. In the end, I did not get an offer. My main takeaway is to clarify the exact onsite structure before traveling, especially if you have already passed earlier coding rounds. I would specifically ask whether the later rounds are still coding-heavy or whether they will cover system design, architecture, and real production trade-offs.
Prep tip from this candidate
Before an onsite, ask the recruiter to confirm whether the later rounds after initial coding screens are still basic Python-style questions or whether they move into system design and production engineering. If you’re interviewing for a senior role, be ready for a tricky first-round coding question even after passing earlier technical screens.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tower Research Capital
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Prime to N | |
| String Shift | |
| Comments Histogram | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Google Maps Improvement | |
| Monthly Customer Report | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Over-Budget Projects | |
| Top 3 Users | |
| Sum to N | |
| Size of Joins | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
A recruiter reaches out, often via LinkedIn, to gauge interest in the role and discuss basic fit and location preferences. In one experience, the candidate was contacted while not actively job hunting and continued because of the Montreal opportunity.
Candidates may complete an online assessment followed by one or more virtual coding interviews. These early rounds focus on problem solving, coding fundamentals, and language-specific knowledge, with Python, C++, and DSA-style questions appearing in the interviews.
The main interview loop is conducted over video and can include multiple technical rounds. Interviewers ask about CV experience, practical engineering judgment, data processing, data storage, OOP, bash basics, and design problems such as building a file system or designing a service and database schema.
Some candidates are invited onsite for a larger final loop, though parts of it may still be virtual. This stage can remain coding-heavy, including tricky Python questions and live problem solving, and may not always shift into the system design or senior-level discussion candidates expect.