Bristol-Myers Squibb Data Scientist interview typically runs 3 rounds: hiring manager chat, HR call, final presentation and roundtables. It usually takes about 3 weeks and is notably presentation-heavy and cross-functional.
$160K
Avg. Base Comp
$220K
Avg. Total Comp
3
Typical Rounds
3 weeks
Process Length
Our candidates report that Bristol-Myers Squibb cares less about flashy algorithm talk and more about whether you can defend your work in a scientific, business-aware way. The strongest signal in the experience we saw was the presentation: it wasn’t just a recap of past projects, but a test of how well the candidate could explain the research question, the choices behind the approach, and the results in a way that held up under scrutiny. That tells us the bar is not simply technical competence; it’s whether you can make your thinking legible to people who may come from different functions.
A recurring theme is the company’s interest in drug-development context. The follow-up discussion went beyond the candidate’s own project into broader industry judgment, including what matters most in drug development and how a molecule would be synthesized. We’ve also seen that they pay attention to influence and collaboration: one behavioral prompt asked about persuading someone to accept an idea, which suggests they value scientists who can move work forward across teams, not just analyze data in isolation. In practice, the candidates who seem to do best here are the ones who can connect technical decisions to scientific tradeoffs and explain why those choices matter to the organization.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Bristol-Myers Squibb process.
The part that stood out most to me was how much weight they put on the presentation and the follow-up discussion. My process lasted about three weeks and had three rounds. It started with a chat with the hiring manager and two other people, which felt more like an introduction than a deep technical screen. They wanted to hear my background, why I was interested in the role, and how I would talk about my previous work. After that I had an HR call that was mostly basic background and logistics, including salary and visa questions.
The final round was the real test. I gave a one-hour presentation on my prior work, and then had two roundtable interviews with three to four people each. That part was much more technical and cross-functional. They asked about my research topic, the process and results, and why I chose that direction. There were also broader questions about field knowledge and industry awareness, like what I considered the most important factor in drug development and how I would synthesize a molecule. One behavioral question that came up was whether I had ever had to convince someone to accept my ideas, so they were clearly looking for both technical depth and communication skills. Overall the process felt structured but not overly aggressive, and the people were engaged throughout. I ended up receiving an offer, and my main takeaway is to be ready to defend your past work clearly and connect it to the business and scientific context, not just the technical details.
Prep tip from this candidate
Prepare a tight one-hour research presentation and expect detailed follow-up on your topic’s process, results, and why you chose it. Also be ready for practical drug-development and synthesis questions, plus a behavioral example about persuading others.
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 Bristol-Myers Squibb
How would you design data pipelines to handle rapid growth in data volume while maintaining reliability?
| Question | |
|---|---|
| Justify a Neural Network | |
| Employee Brand Ambassadors | |
| 2nd Highest Salary | |
| Monthly Customer Report | |
| Cumulative Distribution | |
| Experiment Validity | |
| Last Transaction | |
| Weighted Keys | |
| Hurdles In Data Projects | |
| Always Excited Users | |
| Brain Cancer Treatment Outcomes | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| P-value to a Layman | |
| Reducing Error Margin | |
| RMS Error | |
| Detecting ECG Tachycardia Runs | |
| Fair Coin | |
| Size of Joins | |
| Cumulative Reset | |
| Random Forest Explanation | |
| Time Difference | |
| Causal Email Journey | |
| Greatest Common Denominator | |
| Subscription Retention | |
| Sum to Zero | |
| Secret Wins | |
| Missing Housing Data | |
| Valid Anagram |
Synthesized from candidate reports. Individual experiences may vary.
The process began with a conversation with the hiring manager and two other team members. This felt more like an introduction than a deep technical screen, with questions focused on the candidate’s background, motivation for the role, and how they would describe their prior work.
Next was an HR call covering basic background and logistics. The discussion included salary expectations and visa-related questions, along with other standard administrative topics.
The final stage centered on a one-hour presentation of prior work, followed by two roundtable interviews with three to four people each. These discussions were much more technical and cross-functional, covering the candidate’s research topic, methods, results, industry knowledge, drug development considerations, and behavioral questions about influencing others.