Squarepoint Software Engineer interview questions

12 Software Engineers have shared notes from their Squarepoint interviews, with the questions they were asked in each round. That is 71% of the 17 Squarepoint interview notes on Screna AI.

12 Software Engineer interview notes

Squarepoint·Software Engineer·Technical Phone Screen

Jul 2026
Technical screen at Squarepoint for a software engineer role. The main problem was a payroll file parser built entirely with the Python standard library, which sounds manageable until you realize they want generalized schema handling, type coercion, dedup logic, and three query functions all tied together cleanly.
  • You're given a payroll file as a StringIO object with a header row and manually entered data. Using only the Python standard library, parse it into an in-memory structure that handles missing fields, extra whitespace, inconsistent delimiters, empty lines, and duplicate IDs. The parser should be driven by the header metadata so it works for files with different column sets.
  • After parsing, write a function that counts how many employees have a salary strictly above 30,000. Handle missing or invalid salary values without crashing.
  • Write a function that returns the employee with the longest job tenure based on a start date column. Define and document how you handle rows with missing or unparseable dates, and handle ties explicitly.
  • Write a function that returns the employee with the second-highest salary. Define clearly how you handle duplicate salary values at the top.

“This was the core of the whole problem and I underestimated how much design thinking they wanted up front.”

View Post

Squarepoint·Software Engineer·Technical Phone Screen

Jul 2026
Second part of a Squarepoint quant researcher loop, focused on what you can actually infer from transaction data at different levels of granularity.
  • Given a dataset of transaction records, what kinds of insights or signals could you extract from it, ranging from individual merchant or stock level (e.g. Apple sales) up to sector-wide or macroeconomic trends?

“This was more open-ended than I expected.”

View Post

Squarepoint·Software Engineer·Take-home Assignment

Jun 2026
Squarepoint Capital had me build two React components from scratch and then pick them apart myself. The rating widget was more involved than I expected, and the Todo app follow-ups turned into a pretty wide-ranging design conversation.
  • Build a reusable React rating component that supports configurable icon count, half-step selection, mouse/touch/keyboard interactions, accessibility with ARIA, and both controlled and uncontrolled modes.
  • Build a React Todo application with add/edit/delete/toggle, filtering, localStorage persistence, and basic tests.
  • How would you improve the Todo app's performance, and what techniques would you use?
  • How would you make the Todo app more accessible, including keyboard navigation and screen reader support?
  • What UX improvements would you add to the Todo app, such as inline editing, due dates, or drag-and-drop reordering?
  • How would you scale the Todo app to sync with a backend API, including handling optimistic updates?
  • What would your testing strategy look like for these components, and how would you think about TypeScript adoption and error boundaries?

“The ARIA and keyboard parts took longer than I budgeted.”

View Post

Squarepoint·Software Engineer·Technical Phone Screen

Jun 2026
ML system design round at Squarepoint for a quant researcher role, focused on credit card transaction data. The first part was mostly about data cleaning basics, which felt a bit anticlimactic given the 'finance intuition' billing.
  • You're given a credit card spending time series with timestamp, customer ID, and merchant fields. How would you handle missing values in this dataset?

“Expected something more finance-flavored given how the question was framed beforehand, so the NA handling opener felt weirdly basic.”

View Post

Squarepoint·Software Engineer·Online Assessment (OA)

May 2026
Squarepoint OA for a software engineer role, two coding problems. Nothing too wild but the second one had some annoying edge cases I didn't fully think through until after I submitted.
  • You have an array representing inventory counts for n products. Selling one unit of product i earns revenue equal to its current stock level, then the stock drops by one. Given m total customers each buying exactly one unit, figure out which products to sell to which customers to maximize total revenue.
  • Given a string of text, count word frequencies where words are defined as maximal sequences of letters only (non-letter characters act as separators) and the comparison is case-insensitive. Return up to 3 distinct words sorted by descending frequency, with ties broken alphabetically.

“Greedy with a max-heap, pretty much.”

View Post

Squarepoint·Software Engineer·Technical Phone Screen

May 2026
Quant interview at Squarepoint with a probability question that looks straightforward but has a few ways to go about it. Short and focused.
  • You roll a fair 6-sided die three times. What is the probability that the three outcomes are strictly increasing?

“I started by counting total outcomes (6^3 = 216) then tried to count strictly increasing triples.”

View Post

Squarepoint·Software Engineer·Technical Phone Screen

May 2026
Squarepoint SWE interview, coding round focused on string processing. The problem looked straightforward but there were enough edge cases and design decisions to trip you up if you weren't careful about clarifying scope upfront.
  • Given a string, count word frequencies case-insensitively and return the top words by frequency in descending order, with ties broken alphabetically. The result is capped at 3 words total. How do you approach this, and what design tradeoffs do you consider?

“The part I nearly got wrong was the global cap.”

View Post

Squarepoint·Software Engineer·Technical Phone Screen

Apr 2026
Squarepoint SWE interview with a greedy algorithm problem that looks straightforward but has a few subtle pieces worth thinking through carefully. Pretty standard coding round vibe.
  • You have n products where each product's unit price equals its current remaining stock quantity. Given m customers each buying exactly one unit, design an algorithm to maximize total revenue. Each sale reduces a product's quantity by 1 and earns that quantity as revenue before decrement.

“I saw max-heap pretty quickly, always pull the largest quantity, sell it, push quantity minus one back in.”

View Post

Squarepoint·Software Engineer·Recruiter / HR Screen

Apr 2026
Pretty standard early-round screen for a quant engineer role at Squarepoint. They walked through my resume and asked the usual 'why us' type stuff. Nothing too surprising.
  • Walk me through your resume.
  • Why Squarepoint specifically?

“Standard opener.”

View Post

Squarepoint·Software Engineer·Technical Phone Screen

Apr 2026
Squarepoint quant/dev screen that went sideways fast. The coding problem itself wasn't crazy but the interviewer kept blocking every reasonable approach I tried, and I ran out of time without finishing. Left feeling like the whole thing was rigged against me.
  • What technical indicators do you use when trading stocks?
  • Implement an EMA indicator in pandas from scratch, without looking at documentation.

“Said EMA, which was true and felt like a reasonable answer.”

View Post