Point72 Data Scientist candidates describe an online assessment, recruiter and team conversations, probability and statistics questions, resume deep dives, and often a case study or data project.
$155K
Avg. Base Comp
$205K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Point72 Data Scientist process as assessment-heavy and broader than a standard coding screen. Most reports begin with an online test, and formats vary. One candidate had a 90-minute test with an easy SQL question and medium coding questions. Another had a 45-minute test with two SQL and three Python questions, and a third reported five Python and SQL questions. One candidate also described a fast math and pattern assessment with sequences and dice-style probability.
The live rounds lean toward probability, statistics and explaining your own projects. Reported topics include:
Several candidates say interviewers pushed on resume projects, so be ready to defend your choices and describe a time something went wrong.
The later stages differ by candidate. Some report a case study or modeling test, including a week-long case study with a presentation. Another reports a roughly one-week Python data project aimed at finding potential alphas, where familiarity with financial data mattered. Candidates also describe long processes, so confirm the timeline with your recruiter. Split your preparation between timed SQL and Python practice and clear explanations of regression, probability and ML tradeoffs. Most of these reports ended without an offer. One candidate accepted an offer, and one did not share an outcome.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Point72 process.
OA via HackerRank: 3 questions in 90 minutes. The candidate had been contacted by a recruiter and had not prepared for this type of interview recently.
The assessment included one easy SQL question and two medium/hard LeetCode-style questions. The candidate expected possible Pandas or statistics questions but did not receive either. The SQL question involved aggregation, a subquery, and formatting. The coding questions focused on arrays and strings, including sliding-window and hashmap concepts.
One question asked for the number of combinations of three integers in an array whose sum, divided by parameter d, leaves remainder 0. Another involved server sizes and parameter x: find a combination whose total equals x exactly, returning one if it exists and -1 otherwise.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Point72
Write a query to select the top 3 departments with at least ten employees and rank them according to the percentage of their employees making over 100K in salary.
| Question | |
|---|---|
| Monthly Customer Report | |
| Duplicate Rows | |
| Sum to N | |
| Assumptions of Linear Regression | |
| Precision and Recall | |
| Hurdles In Data Projects | |
| Car Recommendation Architecture | |
| Divisible Triplets | |
| Same Characters | |
| Variate Anomalies | |
| Truncated Distribution | |
| k-Means from Scratch | |
| Concentric Circles | |
| Linear vs Logistic Regression | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Last Transaction | |
| Find the Missing Number | |
| Cumulative Distribution | |
| Top 5 Turnover Risk | |
| Experiment Validity | |
| Payments Received | |
| Paired Products |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter conversation. In one account the recruiter reached out on LinkedIn and set up a coffee chat. Another describes a 30-minute call about role and fit. Prepare a clear reason for choosing Point72 and a short account of your data science experience.
Candidates report different assessments, typically timed. Examples include 90 minutes with an easy SQL question and medium coding questions, 45 minutes with two SQL and three Python questions, and a fast math and pattern test with dice-style probability. Some candidates also mention a video assessment. Practice SQL, array and string problems, and quick probability under time pressure.
Candidates describe interviews with data scientists, researchers, developers or portfolio managers, mixing behavioral and technical questions. Reported topics include Bayes' rule, lasso versus ridge, OLS outliers, k-means and accuracy versus precision. Resume deep dives are common, so know each project well enough to justify your decisions.
Several candidates report a take-home or onsite case study, a modeling test, or a data project. One describes a week-long case study with a presentation. Another describes a roughly one-week Python project to find potential alphas with limited guidance. Expect substantial time and open-ended analysis, and plan to explain your approach clearly.
Final stages vary. One candidate reports a final conversation with a compliance officer after four earlier conversations and accepted an offer. Another expected an onsite after the case study but heard nothing back. Others describe an onsite or superday. Ask your recruiter which stages apply to your team and how updates will be shared.
