IBM Data Scientist candidates report an initial HackerRank screen followed by project-focused technical and behavioral conversations, with SQL, Python, ML reasoning, and clear explanation of tradeoffs recurring.
$120K
Avg. Base Comp
$167K
Avg. Total Comp
3 rounds
Typical Rounds
2-4 weeks
Process Length
IBM Data Scientist candidates most consistently report an early HackerRank assessment before conversational interviews. The screen can combine SQL with Python: one account describes a straightforward join-and-aggregate SQL prompt alongside a harder array-algorithm problem about minimizing peaks and troughs after changing one value; another encountered simple SQL and alternating-string merge. Prepare for both database fluency and algorithmic reasoning, rather than assuming Python will be only basic data manipulation.
Later conversations are less about live coding in some reports and more about how you think through work. Candidates describe detailed resume and research walkthroughs, including why a particular service or modeling approach was selected, how components fit together, and how data integrity was handled. One candidate also described a project-style discussion about comparing two signatures; another reported ML and SQL questions under separate 30-minute limits. Be ready to explain an applied ML approach step by step, including assumptions, alternatives, and tradeoffs.
Behavioral and competency discussion also appears in the process, with client-work questions and prompts that test structured reasoning about an analytical scenario. The exact sequence and difficulty vary by role and team, but the recurring pattern is a coding gate followed by evidence-based discussion of your technical judgment. The available reports do not establish one universal process length.
Synthesized from 5 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.
The part that stood out most was that the interview felt very project-oriented rather than purely theoretical. Everything was in English, and they spent time asking about my work experience and how I would approach an upcoming project. The interviewer would give examples from the project and then ask how I’d solve the problems, so it felt closer to a practical case discussion than a standard quiz. One question I remember was about comparing two signatures, which was asked in the context of how I would reason through the problem and explain a solution.
The process started with a coding round where I was asked an ML question and a Python question. Those were fairly easy overall, and then I had a competency interview afterward. In another round, I was given two questions, one on ML and one on SQL, and each had 30 minutes. I’d describe the ML part as the harder one, closer to medium-to-hard LeetCode style, because I got through 13 out of 14 cases but ran out of time on the last one. The SQL question was more manageable and felt like a LeetCode medium. After that, I didn’t hear back for a while, which was frustrating. My main takeaway is to be ready for applied ML discussion, a practical SQL problem, and to explain your reasoning clearly around project scenarios rather than just giving a final answer.
Prep tip from this candidate
Be ready for an ML coding question with tight time limits and edge cases, since one round had 14 test cases and the last one mattered. Also practice explaining how you would solve project-style problems in English, including questions like comparing two signatures and walking through your approach clearly.
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 | |
| Top 5 Turnover Risk | |
| 500 Cards | |
| Prime to N | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Raining in Seattle | |
| Impression Reach | |
| Encoding Categorical Features | |
| Lazy Raters | |
| The Brackets Problem | |
| P-value to a Layman | |
| New Resumes | |
| Total Transactions | |
| Fair Coin | |
| Found Item | |
| Cyclic Detection | |
| String Mapping | |
| Ride Coupon | |
| Valid Anagram | |
| Estimated Rounds | |
| Missing Housing Data | |
| Find Duplicate Numbers in a List | |
| Expected Tests | |
| Binary Tree Conversion | |
| Three Zebras | |
| Target Indices | |
| Hurdles In Data Projects | |
| Secret Wins |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial timed HackerRank assessment before a live interviewer is involved. Reported versions include SQL plus Python; one account had two coding questions in one hour, while another described an SQL question and a simple coding task.
Reported SQL work includes a join-and-aggregate question, while Python may range from string manipulation to an algorithmic array problem involving peaks and troughs. Candidates should expect accuracy under time limits, including hidden test cases.
Candidates report technical conversations centered on projects, research, model training, data integrity, and design choices. Some also encountered an ML question and a SQL question with 30 minutes allotted to each, so practical explanation and timed problem solving may both matter.
Candidates report competency or behavioral interviews after the coding stage, including questions about client work and structured reasoning through an analytical scenario. Be prepared to make tradeoffs legible, not merely state a conclusion.
