RepostedSquarepoint Capital logo

Squarepoint Capital · OA → Phone screen → Onsite

In process

Squarepoint Capital C++ and Python SWE Interviews: 7 Experiences

Software engineer · New GradReported Jul 1, 2026
Shared byjanebeingjane

Squarepoint Capital software interviews, 2024–2026, level not confirmed: C++ ownership and concurrency, Python generators, and HackerRank coding rounds.

At a glance

  • Process: an OA → two or three technical rounds of 60 to 120 minutes, often on HackerRank → an HR, manager or fit round (01, 02, 03, 04).
  • Asked recently: C++ ownership, copy and move in 3 of the 7 reports (02, 03, 05); OS, memory or concurrency in 4 (01, 02, 03, 04); resume or fit talk in 6 (all but 07).
  • Difficulty: one candidate called the three OA tasks easy (02); another put one OA task near Codeforces 1600 (03); Python rounds used unnamed medium LeetCode tasks (04, 06).
  • Practise first: Fixed Worker Pool with a Shared Queue, String Copy and Move Lifecycle, Repair an Owned Vector and Optimize a Bounded Queue.

Coverage: 7 Squarepoint Capital software candidates (reports 01–07) whose graduate status or exact role is not confirmed: an IIT Kanpur profile listed as Infrastructure Engineer, a C++ SWE / Quantitative Developer, C++ and Python software engineers, and two campus SWE/SDE applicants (London and India). Interview or report dates from September 2024 to July 2026.

Related Squarepoint roundups: New grad and campus SDE, Part 1 (Python OAs, C++ torch and exact-decimal rounds) · New grad and campus SDE, Part 2 (Linux and OOP, currency conversion, flight-queue debugging)

What came up

The C++ reports go deep on memory and ownership; the Python reports on generators, decorators and OOP. Counts are out of 7.

Topic Reports Last seen
Coding or debugging 7 of 7 Nov 2025
Resume, project or fit 6 of 7 Nov 2025
OS, memory or concurrency 4 of 7 Nov 2025
C++ language and ownership 3 of 7 Nov 2025
Python language features 2 of 7 Apr 2025
Networking 2 of 7 2025–26 cycle

Questions we found

Coding

Question Reports Last seen
Classify Heap Addresses from a Memory Snapshot 1 Nov 2025
Fixed Worker Pool with a Shared Queue 1 Nov 2025
String Copy and Move Lifecycle 1 Nov 2025
Match an XOR-Adjusted Sum 1 Oct 2025
Maximize Palindromic Words 1 Oct 2025
Minimize the Sum with Ceiling Halves 1 Oct 2025
Count C++ Constructor and Assignment Calls 1 Jun 2025 (report version)
Observe a Lazy Generator 1 Feb 2025 (report date)
Suggested Products 1 Sep 2024 (report date)

Project coding and LLD

Question Reports Last seen
Manage a Resource with Smart Pointers (LLD) 1 2025
Repair an Owned Vector 1 Jun 2025 (report version)
Optimize a Bounded Queue 1 Jun 2025 (report version)

C++, OS and networking questions

Question Reports Last seen
What std::move does; can it take an rvalue? 1 Nov 2025
RAII and why to use it 1 Nov 2025
std::function and where it helps 1 Nov 2025
Process memory layout; why system calls exist 1 Nov 2025
&v vs &v[0] for {1,2,3}; the vector's memory size 1 Nov 2025
Struct padding, uint8_t and the kinds of C++ cast 1 Nov 2025
Process vs thread 1 2025–26 cycle
Revoke an API key committed to a repository 1 2025–26 cycle
TCP vs UDP 1 Jun 2025 (report version)

Behavioral (BQ)

Question Reports Last seen
Why do you want to join the firm? 1 Nov 2025
Disagreeing with your manager on a project 1 Nov 2025
Approaching a new technology stack 1 Nov 2025
Your ideal work environment 1 Apr 2025
Your favorite past experience, and why 1 Apr 2025
What work excites you? 1 Apr 2025
Pros and cons of the languages you have used 1 Apr 2025
Where do you see yourself in three and five years? 1 Apr 2025

7 detailed candidate timelines

01: IIT Kanpur, two technical hours and a fit talk

Interview date: 2025–26 placement cycle · Role: listed as Infrastructure Engineer; the student targeted SDE roles · Location: IIT Kanpur · Result: Offer

  1. Round one (60 minutes): interests and resume, OS and networking basics, then one Python DSA task with attention to Python efficiency (task not described).
  2. Round two (60 minutes): two more DSA tasks, process versus thread, pipelines and IPC, and how to revoke an API key accidentally committed to a repository.
  3. Round three (30 minutes): company fit, team fit and interests. The offer came before the candidate's next interview elsewhere.

02: C++ campus loop with mismatched OA cards

Interview dates: October–November 2025 · Role: SWE (C++) in the heading, C++ Quantitative Developer in the story · Result: Selected

OA (90 minutes)

  1. Three tasks the candidate called easy. The shared problem cards and the written approaches disagree; our practice follows the approaches.
  2. Pool pairs of equal characters, sort the word lengths and give each word floor(length/2) pairs to complete as many palindromes as possible: Maximize Palindromic Words.
  3. Pick the bits of x so that sum(a[i] XOR x) hits a target, tracking carries and backtracking up to bit 61: Match an XOR-Adjusted Sum.
  4. Replace the current maximum with its ceiling half exactly k times to minimize the sum: Minimize the Sum with Ceiling Halves.

First technical (120 minutes, HackerRank)

  1. An isHeap(void*) check (our version gives a memory snapshot), a thread pool with mutexes, semaphores, threads and a queue and a String class with copy and move construction and assignment.
  2. Process memory layout, why system calls exist with examples, whether std::move accepts an rvalue and what it really does, std::function and RAII. Interviewers helped and accepted pseudocode.

Second technical (90 minutes, HackerRank)

  1. uint8_t, &v versus &v[0] for v = {1,2,3}, the vector's memory footprint, struct padding, casts, std::move and pointers, plus a basic DSA task (not named).

HR (30 minutes)

  1. Why the firm, how they would handle disagreeing with their manager on a project, and how they would approach a new tech stack.

03: An owned vector, C++ call counts and queue tuning

Report version: June 8, 2025 (interview date not given) · Role: C++ Software Engineer · Context: full-time applications around IIT Delhi · Result: Not stated

  1. OA: a two-pointer task the author put near Codeforces 1600 and a tricky implementation task; neither was shared.
  2. Screen one (60 minutes): ten minutes of resume, twenty on virtual memory, process management, page tables, real-time systems, TCP versus UDP and dangling pointers, then thirty on HackerRank repairing a vector class that had no destructor, a bad copy constructor, leaks and no range checks. The candidate fixed them.
  3. Screen two (60 minutes): CV, TCP state-machine questions, counting constructor, copy, move and assignment calls in a snippet, a char** exercise and twenty minutes of live coding.
  4. Screen three (about 45 minutes): given a thread-safe queue and a benchmark, suggest optimizations: moves instead of copies, condition waits instead of busy waiting, a bounded queue, RAII locks and the container's cache behavior. No finished code or measured speedup was reported.

04: A Python loop with three technical hours and a manager round

Report dates: February 28 and April 2025 · Role: Software Developer, Python · Result: Verbal offer

  1. Three technical rounds (about 60 minutes each): resume and experience, OOP, OS and detailed Python. Rounds one and three had unnamed medium LeetCode tasks; DP came up often. Git basics appeared in later rounds.
  2. Round two: write a generator and a decorator and read data from a file for a computation. Practice: Observe a Lazy Generator. The values, decorator behavior and file format were not shared.
  3. Manager and fit (about 45 minutes): ideal work environment, favorite past experience and why, what work excites you, pros and cons of languages used, and where you see yourself in three and five years. Language questions can also come up here. The author said fit can eliminate candidates.
  4. The verbal offer took a week.

05: A C++ interview centered on smart pointers

Interview year: 2025 (report July 1, 2026) · Role: C++ software engineering

  1. A resume walkthrough, then smart-pointer internals, RAII, OOP, polymorphism and virtual functions. Questions got harder as answers got better.
  2. Coding: use smart pointers to manage a resource. The original object was not remembered. Looking up syntax was allowed.
  3. No LeetCode task that the candidate remembered; unsure whether there was an OA.

06: London campus interview starting with projects

Interview date: December 2024 · Role: Software Engineer, university recruiting · Location: London · Result: No offer

  1. The process took one to two months.
  2. The first one-on-one began with an in-depth resume and project talk, then Python decorators and easy-to-medium LeetCode problems (not named).

07: A suggestions-style OA and a C++ debugging task

Report date: September 29, 2024 · Role: SDE, placement · Result: Not stated

  1. One task was like Search Suggestions System: Suggested Products. Every rule of the original variant was not shared.
  2. The other was debugging a C++ function; the author mentioned rechecking logic such as loop exits. The function was not shared.

Patterns across the reports

  1. C++ memory and ownership, in depth. Reports 02, 03 and 05 all asked about copy and move, RAII or smart pointers, and both 02 and 03 had candidates write or fix a class that owns memory.
  2. Concurrency you can code. A thread pool (02) and a thread-safe queue to tune (03).
  3. Python specifics. Generators and decorators (04), decorators (06) and Python efficiency (01).
  4. A fit round that counts. Reports 01, 02 and 04 ended with a fit, HR or manager round; 04 said candidates can be cut there.

Common questions

What C++ questions does Squarepoint Capital ask?

std::move, RAII, smart pointers, std::function, struct padding, casts and vector memory (02, 05), plus fixing or writing classes that own memory (02, 03).

How many rounds is the Squarepoint Capital interview?

Usually an OA, two or three technical rounds of 60 to 120 minutes, then a 30–45 minute fit, HR or manager round (01, 02, 03, 04).

What Python questions does Squarepoint Capital ask?

Generators, decorators, OOP and Python efficiency, alongside medium LeetCode tasks (01, 04, 06).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.