Two Sigma Interview Questions — Page 4

Two Sigma·Data Scientist·Technical Phone Screen

May 2026

Two Sigma data scientist interview with a coding question that looked straightforward on the surface. One round, math-heavy, no ML libraries allowed which tripped me up at first since I kept reaching for numpy instinctively.

Implement simple linear regression from scratch using the ordinary least squares closed-form solution. No ML or stats libraries. Given a list of x and y values, return the fitted slope and intercept.

“My first instinct was to just call numpy's polyfit and I had to stop myself.”

View Post

Two Sigma·Software Engineer·Technical Phone Screen

May 2026

Interviewed for a Research Engineer role at Two Sigma. One coding question, pretty algorithmic in nature. The problem itself wasn't crazy hard but the efficiency angle is where they actually care.

You're given a set of discrete (x, y) points forming a polyline. For a query x value, compute the corresponding y using linear interpolation if x falls between two points, or extrapolation using the nearest boundary segment if x is outside the range.

“My first instinct was to just loop through all the points and find the neighbors.”

View Post

Two Sigma·Software Engineer·Hiring Manager Screen

May 2026

Two Sigma interview for a Quant Software Engineer role. Two questions back to back, one pretty standard and one that really made me think on my feet. Left feeling like I could have prepared my project walkthrough a lot better.

Why are you looking to leave your current role, and what draws you specifically to a Quantitative Software Engineer position?
Walk me through your most recent project from start to finish: the goals, what you personally owned, the architecture and key decisions you made, any major problems you hit and how you solved them, and what the actual impact was. Also what would you change if you did it over?

“Pretty routine opener but I fumbled the second half.”

View Post

Two Sigma·Software Engineer·Technical Phone Screen

Jun 2026

Two Sigma software engineer round, one algorithmic problem the whole time. The problem itself was well-constructed and I can see why they like it, but I went in underprepared for the greedy heap approach and paid for it.

You have a startup with initial capital w and a list of n projects, each with a capital threshold and a profit. You can complete at most k projects (one at a time, in any order), and profit is added to your capital immediately after each project. Find the maximum capital you can end up with.

“My first instinct was brute force: at each step, scan all projects, pick the highest-profit one you can afford, repeat.”

View Post

Two Sigma·Data Scientist·Technical Phone Screen

Jun 2026

Two Sigma data scientist interview with a coding problem that looked like a simple merge exercise but had enough edge cases to slow me down. The problem was algorithmic but clearly motivated by real data pipeline work, which I appreciated.

Given two time-sorted lists of sensor readings (temperature and humidity), each record containing a timestamp, city, and value, for every temperature record find the most recent humidity reading from the same city where the humidity timestamp is less than or equal to the temperature timestamp. Return null if no such humidity record exists.

“My first instinct was to just do a nested loop and move on, but I caught myself and realized that's embarrassing given both lists are already sorted.”

View Post

Two Sigma·Software Engineer·Technical Phone Screen

Jun 2026

Two Sigma quant engineer screen, heavy on stats fundamentals. Four questions, all math, no fluff. You need to know your formulas cold and be ready to explain why they work, not just compute the answer.

What is the valid range of the Pearson correlation coefficient, and what's the reasoning behind it?
Given a small matrix, calculate its determinant.
Find the eigenvalues of a given small matrix.
Given two vectors, compute the cosine similarity between them.

“Knew the range is -1 to 1 but fumbled a bit explaining why.”

View Post

Two Sigma·Software Engineer·Technical Phone Screen

Jun 2026

Two Sigma coding screen, pretty much one algorithmic problem the whole time. Classic stock profit question but they wanted strict O(n) time and O(1) space so you couldn't just brute force it.

Given an array of daily stock prices, find the maximum profit from at most one buy-sell transaction. Return 0 if no profit is possible. Must run in O(n) time and O(1) space.

“I knew the answer pretty quickly, track the running minimum price and compare each day's price against it to update the max profit.”

View Post

Two Sigma·Data Scientist·Technical Phone Screen

Jun 2026

Two Sigma Data Scientist round, algorithmic coding question focused on assignment optimization. Clean problem statement but the O(n log n) constraint is what makes or breaks you here.

You have 2n workers and two tasks. Each worker has a time cost for task A and a different time cost for task B. You must assign exactly n workers to each task. Return the minimum total hours across all workers.

“My first instinct was brute force and I basically said that out loud before catching myself.”

View Post

Two Sigma·Data Scientist·Technical Phone Screen

Jun 2026

Two Sigma data scientist interview, heavy on ML design and statistical rigor. The whole session was basically one long open-ended question about building a signal from Google Trends data, with the interviewer pushing deeper at every step. Felt less like a quiz and more like a research discussion where they were actively probing for where your thinking breaks down.

You have access to relative search volume data over time plus standard daily stock market data. Design a model end-to-end that uses search data to predict stock prices, covering target framing, feature engineering, model choice, training/validation, and signal evaluation.
With thousands of stocks and basically unlimited query terms to choose from, how do you pick which search queries to use without the whole thing becoming data snooping?
Your backtest shows a strong in-sample Sharpe ratio that collapses out of sample. How do you diagnose what went wrong?
Search volume often reacts to price moves rather than leading them. How would you actually establish that your feature leads returns rather than just lagging them?
If the firm already runs momentum and reversal signals, how would you test whether your search-based signal adds genuine incremental value versus just repackaging what they already have?

“This is the kind of question where you can sound smart for five minutes and then completely fall apart when they keep asking 'what else.' I started with predicting forward returns instead of price levels, which felt right, but I underestimated how much they'd push on the cross-sectional vs time-series framing.”

View Post

Two Sigma·Software Engineer·Technical Phone Screen

Jun 2026

Two Sigma research engineer interview with a meaty data analysis problem that blends stats, ML, and feature selection into one question. The kind of problem where you can tell they actually want to see how you think, not just whether you memorized a formula.

You're given historical temperature data for NYC and a bunch of small towns. How would you identify which town has the highest volatility, which is most similar to NYC, then use the towns' data to predict NYC temperatures (evaluated with MSE), and finally do greedy forward feature selection to pick the best subset of towns up to some specified count?

“This is basically four questions stitched together and they just kept going.”

View Post