Point72 Data Science Internship Onsite Interview Experience
Interview Experience
First, there was an online hireview and coding session. A week later, I received an invitation for a three-round onsite interview, each lasting 30 minutes. The main job involves using alternative data
Full Details
First, there was an online hireview and coding session. A week later, I received an invitation for a three-round onsite interview, each lasting 30 minutes. The main job involves using alternative data to predict earnings or other market data for discretionary traders, somewhat like enhancing Bloomberg data. The first round of interviews focused on general data science experience, asking about previous projects. The second round included technical questions, such as how beta, t-statistic, and r^2 change when x and y are swapped in linear regression. It also included questions about multiplying x by 10 or the multiplication of x. These were standard quantitative, linear regression, and machine learning questions. The third round involved the hiring manager asking case studies, such as how to predict next season's earnings using credit card spending data. I think to impress the interviewer, you need to carefully consider what alternative data projects you can work on and how to create value for the front office. This is crucial for hiring interns. There's a post listing a comprehensive question bank. I didn't pass the audition, but I got a job at another HF doing systematic trading. I heard that Point72's full-time DS salary is average, around $175k base plus $50k bonus. Maybe the bonus will be higher after negotiation. Within HF, it's definitely not as good as the turnover rate for front-office quants. I recently watched a documentary about Steven Cohen and learned about his insider trading at SAC, which seemed a bit too dirty. While I'm not exactly a paragon of virtue, and HF is indeed a jungle where the strong prey on the weak, understanding the details of this incident, the fate of those involved, and Steven's situation, makes me feel a bit stigma if I were to work for him in the future.
Topics
More from Point72
About Point72 Interview Reports
This question was reported by a candidate who interviewed at Point72. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Point72 are the higher-signal extractions to take from this report.
For broader preparation context, the Point72 interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Point72 reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Point72 Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Point72 reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.