Point72 interview notes, page 1 of 4

Large Enterprises

Most of these Point72 write-ups come from Data Scientists (13), then Software Engineers (13) and Machine Learning Engineers (10). The most reported rounds are the technical phone screen (26), the online assessment (5), the hiring manager screen (2) and the behavioral / leadership round (2).

38 interview notes · updated Jul 2026

Point72·Software Engineer·Online Assessment (OA)

Apr 2026

Point72 gave me a 30-minute coding task for a Data Engineer role, basically a portfolio trading optimizer built around a classic buy/sell stock problem but with extra structure they wanted around it. More Python-specific than I expected for a data engineering screen.

Implement a Python decorator called 'validate_prices' that checks a stock prices array against defined input constraints before processing.
Write a function 'find_transactions' that takes a stock prices array and returns a list of tuples containing buy day, buy price, sell day, sell price, and profit for each transaction to maximize total profit.
Build a 'generate_report' function that prints a formatted summary of all transactions and the total profit.

“I don't write decorators from scratch that often so I had to think for a second about the wrapper function structure.”

View Post

Point72·AI Engineer·Online Assessment (OA)

Apr 2026

Took an online assessment for an AI Engineer role at Point72 and one of the questions was a multi-part prompt engineering scenario. Time management was a real issue and the later sub-questions were pretty rough.

Design a prompt to filter news for an Olympic champion athlete, given a specific coaching scenario. The question had five sub-parts.

“Made the mistake of typing everything manually instead of using AI to generate and paste, which the platform actually encouraged.”

View Post

Point72·Machine Learning Engineer·Technical Phone Screen

Apr 2026

A technical screen for an ML Engineer role at Point72 that was basically one long open-ended design question about predicting short-term volatility. No leetcode, no fluff, just a deep dive into how you'd actually build the thing end to end. Left feeling okay about it but not confident.

How would you define and isolate idiosyncratic volatility as a prediction target for a 30-minute horizon?
Walk through how you'd construct the training dataset from historical market data, including how you'd handle the train/validation/test split.
What features would you engineer for this prediction task?
Describe a modeling architecture you'd propose for this problem and justify your design choices.
How would you evaluate model performance, and how would you ensure it holds up across different market regimes?

“This is where I stumbled a bit at first.”

View Post

Point72·Software Engineer·Technical Phone Screen

Apr 2026

A 30-minute technical screen for a Data Engineer role at Point72 that stayed pretty squarely in the PySpark and data pipeline space. Nothing behavioral, just back-to-back technical questions. Felt fast.

How do you approach data orchestration in a data pipeline? Walk me through your process.
What data quality checks do you implement in your pipelines? Things like thresholds, primary key validation, upstream dependency checks.
How would you design a data observability framework for a production pipeline?
What techniques do you use to optimize Spark jobs?
Can you explain how Spark's lazy evaluation works and why it matters?
How does Spark handle distributed data processing under the hood?
You're running a streaming pipeline and about 2% of incoming records fail your data quality checks. Do you stop the pipeline or keep it running?

“Talked through scheduling, dependency management, retry logic.”

View Post

Point72·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026

Interviewed for a Data Engineer role at Point72. One behavioral question about cross-team collaboration, pretty standard stuff for a finance-adjacent tech shop.

Can you walk me through a time you had to work with multiple stakeholders to reach a solution that worked for everyone?

“I had an answer ready but it kind of fell apart in the middle because the example I picked had too many moving parts to explain quickly.”

View Post

Point72·Data Scientist·Technical Phone Screen

Apr 2026

Point72 data scientist interview with a single heavy SQL question that covers multiple aggregation layers, conditional filtering, and edge case handling all in one shot. No fluff, just write the query and defend your logic.

Write a single ANSI SQL query that returns, for every customer with at least one non-canceled order: their most recent completed or shipped order timestamp across all time, the count of distinct products purchased in the last 7 days (completed/shipped only), and net spend in the last 7 days after subtracting refunds whose return timestamp falls in that same window. Customers with no activity in the window should still appear with 0s for the last two metrics.

“This took me way longer to untangle than I expected.”

View Post

Point72·Software Engineer·Technical Phone Screen

Apr 2026

Got a probability question for a quant role at Point72. Short and sweet on the surface, but it requires you to actually think about geometry or covariance, not just plug into a formula.

X and Y are independent standard normal random variables. What is P[X > 3Y]?

“My first instinct was to set up an integral and I immediately started second-guessing myself on the bounds.”

View Post

Point72·Machine Learning Engineer·Technical Phone Screen

Apr 2026

Interviewed for an ML Engineer role at Point72 and got a coding question that looked straightforward but had a subtle wrinkle worth thinking through carefully.

Given a string of lowercase letters, you must choose exactly one contiguous substring and decrement every character in it by one (with 'a' wrapping around to 'z'). Return the lexicographically smallest result.

“My first instinct was to just decrement the whole string, which is obviously wrong because 'a' wraps to 'z' and makes things worse.”

View Post

Point72·Machine Learning Engineer·Technical Phone Screen

Apr 2026

First round for an MLE role at Point72, done with a junior engineer on the team. About 25 minutes, split between walking through my resume and fielding Transformer questions mixed in throughout. Pretty low-key but the technical questions came faster than I expected.

Walk me through your resume, with Transformer-related questions asked throughout.

“It wasn't a clean resume walkthrough where you just narrate your history.”

View Post

Point72·Data Scientist·Technical Phone Screen

Apr 2026

Coding screen for a Data Scientist role at Point72. One algorithmic question, pretty self-contained, nothing too wild but the tie-breaking condition is the kind of thing that trips you up if you're not paying attention.

Implement a function that takes a list of color strings and returns the one appearing most frequently. If two colors are tied in count, return the lexicographically smallest one.

“The frequency counting part is straightforward, hash map, done.”

View Post