23andme Data Scientist interview typically runs 7 rounds: scientific screen, technical screen, four team interviews, and a 45-minute presentation. The process usually takes a few weeks and is structured and rigorous.
$111K
Avg. Base Comp
$137K
Avg. Total Comp
7
Typical Rounds
3-5 weeks
Process Length
Our candidates report that 23andMe is looking for more than a data scientist who can ship analysis — they want someone who can explain the scientific logic behind the work. A recurring theme is the emphasis on statistical judgment: one candidate was asked about mixed-effects models and Bayes’ theorem, and the interview felt focused on when those tools are appropriate rather than on reciting definitions. That tells us the bar is less about trivia and more about whether you can reason through uncertainty in a biotech context.
We’ve also seen that the company pays close attention to clear, correct execution. The coding questions described were simple on the surface, but the signal came from writing clean code and handling fundamentals without overcomplicating things. Just as important, multiple candidates noted that the project presentation carried real weight. That suggests 23andMe is evaluating whether you can take a past analysis and walk a team through it end to end, with enough precision that the science feels trustworthy.
The pattern across experiences is a team that wants strong technical grounding paired with thoughtful communication. Our candidates report that the conversations felt collaborative, but not casual; interviewers were looking for people who could discuss methods, defend choices, and fit into a group that works closely across scientific and product questions. In practice, the candidates who do best here are the ones who can connect code, statistics, and business context into one coherent story.
Synthetized from 1 candidates 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 23andme process.
The interview process was fairly structured and started with an initial scientific screen over phone or Zoom where we talked through my background and the role itself. That first conversation was pretty standard, but it set the tone for the rest of the process because they clearly cared about both the technical side and how I would fit with the team. After that, I had a technical screen that mixed coding with statistics, and that was the part that felt most substantive. The coding portion included writing a script to generate the first n Fibonacci numbers and then solving a classic two-sum problem where you return the indices of the two values that add to a target. It was straightforward algorithmically, but they wanted clean, correct code rather than anything overly fancy.
What made the screen more interesting was the statistical portion. I was asked about mixed-effects models and Bayes’ theorem, so it was less about memorizing formulas and more about showing that I understood when and why those methods are used. After that, I went through four separate interviews with team members, which gave me a better sense of the group and how they worked together. The process also included a 45-minute presentation where I walked through a previous project in detail, and that was a big part of the evaluation since they seemed to care a lot about scientific communication and how I approached problems. Overall, the process felt rigorous but fair, and I ended up receiving an offer. My main takeaway is to be ready for a blend of practical coding, core statistical concepts, and a project presentation that you can explain clearly from end to end.
Prep tip from this candidate
Be ready to code simple exercises like Fibonacci generation and two-sum quickly and cleanly, then switch into statistics questions on mixed-effects models and Bayes’ theorem. Also prepare a 45-minute project walkthrough, since the presentation was a meaningful part of the process.
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 23andme
Given an array and a target integer, write a function that returns the indices of two integers in the array that add up to the target integer.
| Question | |
|---|---|
| Implementing the Fibonacci Sequence in Three Different Methods | |
| 2nd Highest Salary | |
| Cumulative Distribution | |
| Experiment Validity | |
| Prime to N | |
| Weighted Keys | |
| Last Transaction | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Always Excited Users | |
| Size of Joins | |
| Total Spent on Products | |
| Detecting ECG Tachycardia Runs | |
| Bagging vs Boosting | |
| Reducing Error Margin | |
| RMS Error | |
| Fair Coin | |
| Brain Cancer Treatment Outcomes | |
| The Brackets Problem | |
| Cumulative Reset | |
| Valid Anagram | |
| Time Difference | |
| Causal Email Journey | |
| Greatest Common Denominator | |
| Random Forest Explanation | |
| Subscription Retention | |
| Sort Strings | |
| String Mapping | |
| Secret Wins |
Synthesized from candidate reports. Individual experiences may vary.
An introductory phone or Zoom conversation focused on your background, the role, and overall fit. This stage sets the tone for the process and assesses both scientific/technical experience and alignment with the team.
A substantive interview combining coding and statistics. Candidates may be asked to write simple scripts such as generating Fibonacci numbers or solving a two-sum problem, along with conceptual questions on topics like mixed-effects models and Bayes’ theorem.
A series of interviews with different team members to evaluate collaboration, problem-solving, and day-to-day fit with the group. These conversations help the candidate understand how the team works and give the team a broader view of the candidate.
A presentation where you walk through a previous project in detail. The interviewers place strong emphasis on scientific communication, how you structure your thinking, and how clearly you can explain your approach end to end.