
Two candidates for computational roles at the Broad Institute describe an online coding assessment, with one also reporting a short video interview on motivation and mission fit. Both candidates were not offered the role.
$114K
Avg. Base Comp
$140K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The two reports behind this guide come from adjacent roles rather than a Data Scientist title: a Computational Associate I applicant and a Data Science Co-op applicant. Both describe a coding assessment as the first hurdle, so treat it as the part of the process to prepare for most seriously.
The co-op candidate describes a two-hour coding assessment with two algorithm problems and a data manipulation exercise built on sample data. That candidate felt the data manipulation task was closest to real analyst work. Practice it as carefully as the algorithm questions. The Computational Associate candidate was invited to an assessment soon after submitting a resume. They say it checked programming proficiency and problem-solving approach, but they shared few specifics.
The Computational Associate candidate also completed a short-question video interview. It covered communication, motivation, and whether their goals matched the institute's mission. The question they remember most was what interests them about working at the Broad. Prepare a specific answer tied to the institute's research rather than a generic wish to make an impact.
Both candidates were not offered the role. The co-op candidate also describes confusing recruiter messages: a scheduling email with no available slots, then a deactivation notice that was later corrected. Keep copies of recruiting emails and ask for clarification in writing if messages conflict.
Synthesized from 2 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 Broad Institute process.
I applied for the Computational Associate I role at the Broad Institute, which was a different title from the one I was originally looking at, so keep that in mind as you read this. After I submitted my resume, I was invited to a coding assessment promptly. It was meant to check my proficiency in relevant programming languages and how I approach problem-solving. The details I can share are limited. Once that was done, I completed a video interview made up of short questions rather than a long technical grilling. They focused on how I communicate, what motivates me, and whether my goals lined up with the institute's mission. The question I remember most was what interests me about working at the Broad. I'd recommend walking in with a specific answer tied to the research and the institute's work, not a generic line about wanting to make an impact. I did not receive an offer. The process felt structured and thorough, and it seemed designed to evaluate both technical skills and cultural fit.
Prep tip from this candidate
Expect short video-interview questions on motivation and mission alignment, so prepare a specific answer for why the Broad's work interests you. Be ready for a coding assessment shortly after you submit your resume.
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.
| Question | |
|---|---|
| Fair Coin | |
| Cumulative Distribution | |
| Experiment Validity | |
| Cumulative Reset | |
| Always Excited Users | |
| Time Difference | |
| P-value to a Layman | |
| Total Spent on Products | |
| Normal Distribution Sample | |
| Subscription Retention | |
| Hurdles In Data Projects | |
| Random Forest Explanation | |
| PCA and K-Means | |
| Brain Cancer Treatment Outcomes | |
| Causal Email Journey | |
| Regularization and Validation | |
| Digit Accumulator | |
| Unbiased Estimator | |
| Concentric Circles | |
| LRU Cache 1 | |
| Greatest Common Denominator | |
| RMS Error | |
| Slow SQL Query | |
| 85% vs 82% | |
| Statistically Significant Test | |
| Client Solution Pushback | |
| Sum to Zero | |
| Processing Large CSV | |
| Secret Wins |
Synthesized from candidate reports. Individual experiences may vary.
One candidate applied for Computational Associate I, a different title from the one first considered, so confirm the exact role and title before you apply. That candidate was invited to the coding assessment promptly after submitting a resume.
Both candidates report a coding assessment. The co-op candidate describes a two-hour test with two algorithm problems and a data manipulation exercise on sample data. The other candidate says it covered programming proficiency and problem-solving but gave few details. Practice both algorithms and hands-on data work.
One candidate completed a video interview made up of short questions rather than a long technical grilling. It focused on communication, motivation, and alignment with the institute's mission. The question they remember best was what interests them about working at the Broad. A specific, research-grounded answer is likely to help.
Both candidates report no offer. The co-op candidate received a scheduling email with no available times, was told it was sent in error, and then received a deactivation message that was later explained as the wrong automated reason. Candidates may want to keep written records and ask for clarification if messages conflict.