Three candidates describe Medtronic's Data Scientist interviews as HR and manager conversations; two report a take-home or test task before a final stage, and two describe slow communication. All three report no offer.
$107K
Avg. Base Comp
$132K
Avg. Total Comp
Not reported
Typical Rounds
1-2 months
Process Length
Reports on the Medtronic Data Scientist interview point less to a puzzle gauntlet and more to a test of whether you can explain your own work. Two candidates describe a task-based stage. One was given a coding problem in the language of their choice plus a theoretical question about a modelling choice, and the final panel opened by asking them to defend the take-home decisions. Another prepared a test task to present in the final stage. Either way, practise explaining why you chose a method, not only what it produced.
The early conversations are described as fairly general. One candidate had an HR call about availability, visa status and salary expectations, then a manager conversation on past projects, leadership and how quickly they pick up new tools. Another was asked why they chose Medtronic and how they had used data to solve a problem, and was also asked about clinical experience, so healthcare examples may help. A third said questions began with why they were interested in the role and moved into the specifics of the role and their experience.
The most detailed final-round account, an in-person session with four interviewers, covered unit testing, machine learning concepts, SQL and a situational problem worked on a blackboard. That candidate found that reasoning aloud and adjusting to new constraints mattered.
All three candidates report no offer. Two describe silence after their interviews; one also had unscheduled calls from hiring managers, and another's follow-up email to HR went unanswered. Asking about next steps at each stage seems sensible.
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 Medtronic 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 Medtronic
Describing a data project and its challenges
| Question | |
|---|---|
| RAG Strict Source Control | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Data Preparation for Imbalanced Data | |
| Impossibly Iterative Fibonacci | |
| Scalable Data Pipelines | |
| Your Strengths and Weaknesses | |
| WallStreetBets Sentiment Analysis | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Experiment Validity | |
| Cumulative Distribution | |
| Button AB Test | |
| Prime to N | |
| Rain in N Days | |
| Last Transaction | |
| Always Excited Users | |
| Flight Records | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| Job Recommendation | |
| Bagging vs Boosting | |
| RMS Error | |
| Brain Cancer Treatment Outcomes | |
| Size of Joins | |
| Fair Coin | |
| Cumulative Reset | |
| Instagram TV Success | |
| Group Success |
Synthesized from candidate reports. Individual experiences may vary.
One candidate describes an HR call covering availability, visa status and salary expectations. Another says the process began with a few rounds with HR and hiring managers, online first, with early questions about why they were interested in the role. Have a specific answer on why this role.
One candidate had a one-on-one with a manager focused on past projects, skills, leadership and learning new tools. Another describes sessions of roughly 30 to 60 minutes covering why Medtronic, how they used data to solve a problem, and clinical experience. Some of those calls came unscheduled.
One candidate received a coding problem, solvable in any language, plus a theoretical question on the reasoning behind a modelling or analysis choice, and says the team cared about the written explanations. Another prepared a test task to present in the final stage. Be ready to explain your reasoning.
One candidate had an in-person final round with a manager and three senior team members. It opened with the take-home, then covered unit testing, machine learning, SQL, a blackboard situational problem and behavioural questions on leadership and teamwork. Another describes an onsite stage with team members.
All three candidates report no offer. One describes weeks of silence before a rejection email, and another received no feedback after the final interview and no reply to a follow-up email to HR. Reported timelines run from over a month to about two months from application to final interview.
