
IBM Data Scientist candidates report a HackerRank-style screen with SQL and Python, sometimes followed by a competency video or trait assessment, then project-focused conversations that mix behavioral and technical questions.
$123K
Avg. Base Comp
$160K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
IBM's Data Scientist interview, as candidates describe it, starts with an automated coding assessment before any person is involved. Most reports describe one SQL question and one Python question. Several call them easy, such as a join-and-aggregate query or a string-merging task. One candidate faced a harder algorithmic Python problem about peaks and troughs in an array. That candidate passed the visible tests, failed hidden ones and did not advance, so don't assume the Python question is always simple.
After the assessment, the next steps vary. One candidate was told by email that passing would lead to a recorded competency video answering a pre-recorded question, and another describes a competency interview after the coding round. One candidate also took a trait assessment. Candidates who advanced describe conversational rounds in which interviewers pick a project from the resume and keep asking why you chose a tool, how the pieces fit together, and how you protected data quality. One candidate reported applied ML and SQL questions with 30 minutes each. Another got a case-style question about using blockchain for medical records, where the interviewer cared about how the answer was structured.
Three candidates who reached later rounds received offers, while others were rejected after the assessment or a later round. Candidates also mention slow communication and little feedback. Prepare easy-to-medium SQL and Python, with some algorithm practice. Also prepare a project story you can defend decision by decision.
Synthesized from 9 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.
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 | |
|---|---|
| Top 5 Turnover Risk | |
| Merge Sorted Lists | |
| Fair Coin | |
| Find the Missing Number | |
| Largest Salary by Department | |
| 500 Cards | |
| Prime to N | |
| Raining in Seattle | |
| Impression Reach | |
| Encoding Categorical Features | |
| Lazy Raters | |
| P-value to a Layman | |
| The Brackets Problem | |
| New Resumes | |
| Total Transactions | |
| Found Item | |
| Ride Coupon | |
| Cyclic Detection | |
| String Mapping | |
| Expected Tests | |
| Estimated Rounds | |
| Missing Housing Data | |
| Justify a Neural Network | |
| Three Zebras | |
| Valid Anagram | |
| Binary Tree Conversion | |
| Find Duplicate Numbers in a List | |
| Swap Variables | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an automated screen with one SQL and one Python question. Most describe both as easy, for example a join-and-aggregate query or merging strings alternately. One candidate reported a harder algorithmic Python problem with hidden test cases. Expect timed work and practice accuracy on edge cases.
One candidate was told by email that passing the assessment leads to a recorded competency video answering a pre-recorded question, and possibly an English language assessment for some roles. Another describes a competency interview after the coding round. Prepare a few STAR-style examples from real projects.
One candidate who later received an offer described a trait assessment between the coding test and the video meetings, focused more on personality fit than technical depth. Other candidates did not mention this step, so it may not apply to every role or team.
Candidates who advanced describe conversational rounds that combined behavioral and technical questions. Interviewers typically picked resume projects and probed tool choices, model training decisions, data integrity and tradeoffs. One report described an applied ML and SQL round with 30 minutes per question.
Reported outcomes include offers and rejections. Some candidates mention slow updates after the assessments, or a rejection without explanation. Total timelines are not reliably reported, so plan for possible gaps between stages and keep applying elsewhere.