
IBM Data Scientist candidates describe an automated coding screen with SQL and Python, followed for those who advance by conversational interviews about their projects, behavioral topics and applied ML.
$130K
Avg. Base Comp
$160K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
The IBM Data Scientist interview usually opens with an online coding screen. Five of the six reports we reviewed describe an automated assessment with a SQL question and a Python or general coding question, most of them on HackerRank. Difficulty varies. One candidate called it easy, with a simple alternating string merge. Another got a join-and-aggregate SQL task plus a much harder Python problem about minimizing peaks and troughs in an array, passed the visible tests, failed hidden ones, and did not advance. Don't treat the Python portion as a formality.
Candidates who got past the screen describe conversations about their own work. Two reports call the process three rounds in total, with a coding assessment followed by two interviews. One offer-holder said the last two rounds had no coding at all. Interviewers picked projects from the resume and asked why a given service was chosen, how the pieces fit together and how data integrity was handled. Another offer-holder had a conversational role discussion, then a video interview on their background and problem-solving approach. A third was asked about ML fundamentals, model evaluation, client work, and how blockchain might secure medical records, where the interviewer cared about structured tradeoffs.
One candidate who did not get an offer reported a timed round with an ML question and a SQL question at 30 minutes each. Several candidates mention slow or sparse communication after assessments. Be ready to defend design choices on your projects, and practice timed SQL and algorithmic Python.
Synthesized from 6 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 Ibm process.
I went through a screening that consisted of a one-way video interview and a HackerRank online assessment. The online assessment had one SQL question and one Python question, both easy-to-medium level. The one-way video had 6 questions and focused on my projects and the STAR method.
Questions asked: Describe a project where you had to work with a non-technical stakeholder. How did you explain complex concepts?
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 Ibm
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| First to Six | |
| 500 Cards | |
| Top 5 Turnover Risk | |
| Prime to N | |
| Largest Salary by Department | |
| Raining in Seattle | |
| Find the Missing Number | |
| Impression Reach | |
| Lazy Raters | |
| Encoding Categorical Features | |
| P-value to a Layman | |
| The Brackets Problem | |
| New Resumes | |
| Total Transactions | |
| Fair Coin | |
| Found Item | |
| Ride Coupon | |
| Cyclic Detection | |
| String Mapping | |
| Estimated Rounds | |
| Expected Tests | |
| Missing Housing Data | |
| Three Zebras | |
| Valid Anagram | |
| Binary Tree Conversion | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Secret Wins | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
Five candidates describe an automated screen with SQL and Python or general coding questions, mostly on HackerRank. One reported two questions in a one-hour session. Difficulty varied: one found it easy, while another failed hidden test cases on an array-based algorithm problem and did not advance.
Reports of extra steps differ. One candidate describes a trait assessment focused on personality fit after the coding screen. Another's IBM email listed a recorded competency video and possibly an English assessment as next steps. A third mentions a competency interview after a coding round.
One offer-holder had two back-to-back video meetings, the first exploring the role and the second walking through their resume and projects. Another reported behavioral questions about client work, ML fundamentals, model evaluation and an open-ended blockchain-for-medical-records question judged on structured reasoning.
One offer-holder said the final two rounds had no coding. Interviewers chose resume projects and asked why a service was picked, how components fit together, what to keep in mind when training a model, and how data integrity was ensured. A different candidate had a timed ML and SQL round, 30 minutes each.