Tower Research Recruitment Process
Question Details
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other as...
Full Details
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other aspirants, and the portal where you can apply. About Company: Tower Research Capital, a trading and technology firm founded in 1998 by Mark Gorton, has created some of the world's quickest and most advanced electronic trading systems. Recruitment Process : Online Assessment Technical Interview 1 Technical Interview 2 HR Tower Research Eligibility Criteria : A bachelor’s degree in computer science or related field Strong communication skills
Online Assessment MCQ-based Quantitative, Verbal, Reasoning, and Coding. The aptitude section had medium-level questions, Computer Science Concepts. Technical Interview 1: Questions related to OS, OOPs, DBMS, and Computer Network and Data Structures and Algorithms Medium Hard Level and Discussion On Projects. Technical Interview 2: Questions on Design Low-Level Design and High-Level Design
HR Tell me About Yourself What are your Strengths and Weaknesses? Are you willing to relocate or travel? Hobbies Family- Background Interview Experience: It is always beneficial if you know what it is to be there at that moment. So, to give you an advantage, we provide you with Interview Experiences of candidates who have been in your situation earlier. Make the most of it. TowerResearch Interview Experience Questions Asked in TowerResearch : Binary Tree to DLL Reverse a sublist of a linked list Distinct palindromic substrings Median of 2 Sorted Arrays of Different Sizes Alien Dictionary Where to apply: TowerResearch LinkedIn
Topics
About Tower Research Interview Reports
This question was reported by a candidate who interviewed at Tower Research. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Tower Research are the higher-signal extractions to take from this report.
For broader preparation context, the Tower Research interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Tower Research reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Tower Research Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Tower Research reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.