
Three candidates describe Millennium's Data Scientist interviews: a timed coding screen, then technical and conversational rounds on statistics, time series, and past project work. All three report no offer.
$200K
Avg. Base Comp
$250K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
Millennium's Data Scientist interview, as three candidates describe it, begins with a timed online screen and moves into conversations about statistics and applied work. Expect a real coding screen up front. One candidate describes a HackerRank-style round mixing Python and SQL, where speed mattered. Another reports a 60-minute assessment with multiple-choice questions and three coding problems, including a longest common subsequence dynamic programming task. A third describes a HackerRank with four problems, mostly order book reconstruction plus a dynamic programming problem.
The technical rounds lean on practical statistics and data handling. One candidate was asked to implement OLS regression in NumPy without scikit-learn. In a later round, the same candidate discussed time series analysis in pandas, including how to structure and manipulate temporal data. Another had a Zoom round on linear algebra, probability, and statistics. It included an order book class to complete with submit and cancel methods, a question on the maximum of correlated random variables, and ridge regression properties. That candidate called the questions on the easier side.
Later conversations can be more behavioral. One candidate walked through a data project and then discussed their alpha research pipeline, including how they test ideas, which statistics they use, and how they think about overfitting. Another worked through a verbal case study with no live coding.
All three candidates report no offer, and their accounts stress speed and clean execution more than exotic theory. One reports hearing nothing for about a month after the second round, so applicants should be prepared for uneven communication.
Synthesized from 3 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 Millennium process.
The interview felt pretty casual overall, but the first round caught me off guard because it was a Hackerrank-style screen and leaned much more on coding than theory. It was a mix of Python and SQL, and the main thing was speed — there wasn’t much room to overthink, so you had to move quickly through common data science tasks. After that, the rest of the process was much more conversational. I went through three rounds total, and the later interviews were mostly behavioral with a few basic technical threads woven in. The questions stayed pretty high level and centered on how I work, not on trying to stump me.
One of the main prompts was to walk through a project involving data, and that led into a broader discussion about my alpha research pipeline: how I test ideas, what statistics I look at, and how I think about overfitting in specific cases. Everyone I spoke with seemed smart and friendly, and the feedback loop was fast at every stage once the process started, which made it feel organized. The vibe was laid back and more like a conversation than an interrogation, but I’d still prepare for the first round to be a real coding screen rather than a pure DS theory interview. I ended up not getting an offer, so my biggest takeaway is to be ready for quick Python/SQL execution up front and then to explain your research or project work clearly and conversationally in the later rounds.
Prep tip from this candidate
Practice a fast Hackerrank-style screen that mixes Python and SQL, since the first round was coding-heavy and time pressured. Also be ready to explain a data project and your alpha research/testing process, including how you think about overfitting and what statistics you use.
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 Millennium
Write a query to display the top three users by downloads each day
| Question | |
|---|---|
| Customer Analysis | |
| WallStreetBets Sentiment Analysis | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Cumulative Distribution | |
| Experiment Validity | |
| 500 Cards | |
| Compute Deviation | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Button AB Test | |
| Prime to N | |
| Session Difference | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Last Transaction | |
| Rain in N Days | |
| Attribution Rules | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a timed first screen. One describes a HackerRank-style mix of Python and SQL. Another describes a 60-minute test with multiple-choice questions plus coding. A third describes four problems, mostly order book reconstruction plus dynamic programming. Applicants should typically prepare for speed and clean state handling.
One candidate's technical round reviewed the resume, worked through code snippets, and asked for an OLS implementation in NumPy. Another candidate's Zoom round covered linear algebra, probability, and statistics. It included an order book class with submit and cancel methods, the maximum of correlated random variables, and ridge regression properties. That candidate called the questions on the easier side.
One candidate reports a second technical round on pandas time series analysis, plus a verbal case study with no live coding. The discussion centered on how to structure and manipulate temporal data and on practical trade-offs. Applicants may want to practice working with temporal data in pandas and reasoning aloud.
One candidate describes later rounds that were mostly behavioral with light technical threads. They included a data project walkthrough and a discussion of the candidate's alpha research pipeline, covering how ideas are tested, which statistics are used, and how overfitting is handled. Applicants may want a clear story about their own research choices.