Candidates report three to four rounds for Squarepoint Software Engineers: often a HackerRank assessment, then live coding with Python fundamentals, practical build tasks, and in-depth questions about your own projects.
$110K
Avg. Base Comp
$150K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Squarepoint's Software Engineer interviews lean toward practical coding and language fundamentals rather than pure puzzle-solving, though the mix depends on the team. Several candidates started with a HackerRank assessment. One described two questions, hashing URL strings and generating unique usernames. Another said it covered data structures, algorithms and Python fundamentals, with the format appearing to depend on the division.
Live rounds usually open with your background and projects, and interviewers expected a detailed walkthrough rather than a high-level summary. Candidates on the Python path report questions on tuples versus lists and context managers, along with Bash and SQL familiarity. Another candidate was asked the difference between a list and a map and to explain OOP principles. The coding that followed ranged from LeetCode easy to medium, including recursively unpacking arbitrarily nested lists and querying JSON.
Others were asked to build something concrete: a todo app with TypeScript questions and a reimplemented JavaScript function, an in-memory key-value store with SQL-like transactions built on a hashmap, or a calculator that parses numbers and operators written as digits or words. In the key-value store round, the hard part was turning the transaction design into complete working code, so practice finishing implementations, not just describing them. One candidate noted the interviewer gave no feedback while they coded, so be ready to narrate your approach unprompted.
Candidates describe three to four rounds in total, and most shared outcomes were rejections.
Synthesized from 13 candidate 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 Squarepoint capital process.
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 Squarepoint capital
Determine whether there exists a permutation of an input string that is a palindrome.
| Question | |
|---|---|
| Stranded Miner | |
| Find Square Root | |
| Pathfinder in Maze | |
| Shortest Path Algorithms | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Size of Joins | |
| Total Spent on Products | |
| Get Top N Frequent Words | |
| Top 3 Users | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Duplicate Rows | |
| String Shift | |
| Google Maps Improvement | |
| Scrambled Tickets | |
| Comments Histogram | |
| Prime to N | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a HackerRank assessment. One described two questions on hashing URL strings and generating unique usernames after the CV screen. Another said it covered data structures, algorithms and Python fundamentals, with the format seeming to depend on the division.
Candidates describe a conversation of roughly an hour to 90 minutes with one or two engineers. It typically starts with past projects, which interviewers expected to be explained in detail. Python questions followed, such as tuples versus lists and context managers, with Bash and SQL in one report. Live coding ranged from LeetCode easy to medium.
Reported tasks include a todo app with TypeScript questions and a reimplemented JavaScript function, an in-memory key-value store with SQL-like transactions, and a calculator that parses numbers and operators written as digits or words. Another candidate had a second technical round with easy-to-medium problems such as unpacking nested lists.
One candidate had an HR conversation after two technical rounds. Others were told an HR round, or a system design and hiring manager stage, would follow, though they did not reach it.
