IBM AI Engineer interviews reported here begin with a HackerRank screen, then move to project-centered technical discussion and a manager/architect conversation with behavioral questions.
$173K
Avg. Base Comp
$208K
Avg. Total Comp
3 rounds
Typical Rounds
2-4 weeks
Process Length
For the IBM AI Engineer role, the clearest reported path is a three-round process: a HackerRank assessment, a technical and resume discussion, then a conversation with a senior manager and technical architect. Prepare coding and SQL as a timed screen, then be ready to connect your AI work to concrete decisions. One candidate reported two easy-to-medium DSA questions and two MySQL queries in the first round; another report describes a timed, auto-graded assessment with two medium LeetCode-style problems and a SQL join-and-aggregation task.
The technical discussion was centered on the candidate’s own work alongside Python, machine learning, deep learning, RAG, LLMs, and performance metrics. That makes a concise explanation of what you built, how you judged quality, and the tradeoffs you made more useful than a broad theory-only review. Another report for an IBM AI internship similarly mentions project discussion, DSA, Transformers, attention, RNNs, convolution, cloud experience, and a research-project pitch, so candidates whose background overlaps those areas may want clear, plain-language explanations ready.
The final reported AI Engineer conversation included behavioral questions such as handling unrealistic customer expectations and a short resume-linked demo. Rehearse a focused demo and answers that show how you communicate with stakeholders. The available reports do not give an explicit end-to-end timeline.
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 Ibm process.
The first technical stage was a timed HackerRank assessment consisting of two medium-difficulty, LeetCode-style problems. Both were standard algorithmic questions rather than domain-specific or SQL-heavy — the kind that test data-structure fluency and clean implementation under time pressure rather than deep system knowledge. I worked through both within the allotted window, focusing on getting correct, passing solutions first and then tightening time complexity where I had room. The auto-graded format meant no interviewer interaction at this stage; it was purely about clearing the hidden test cases, including the edge cases that usually separate a full pass from a partial one.
The assessment felt like a screening filter rather than the core evaluation — a gate to confirm baseline coding ability before investing interviewer time. I made sure to handle boundary conditions (empty inputs, single elements, and off-by-one cases) since medium problems are often scored on completeness of test coverage rather than cleverness.
The SQL component was a multi-table join and aggregation problem involving grouping logic and schema interpretation under time pressure.
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 | |
| Find the Missing Number | |
| Raining in Seattle | |
| Impression Reach | |
| Encoding Categorical Features | |
| Lazy Raters | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| The Brackets Problem | |
| New Resumes | |
| Total Transactions | |
| Fair Coin | |
| Transformer Encoder Layer | |
| Found Item | |
| Cyclic Detection | |
| String Mapping | |
| Ride Coupon | |
| Valid Anagram | |
| Estimated Rounds | |
| Flatten JSON | |
| Missing Housing Data | |
| Find Duplicate Numbers in a List | |
| Expected Tests | |
| Binary Tree Conversion | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
Two AI Engineer reports describe a timed, auto-graded HackerRank-style opening. Candidates reported LeetCode-style data-structure problems; SQL also appeared as MySQL queries in one report and a multi-table join and aggregation task in another. Practice delivering complete solutions under time pressure.
One candidate reported a technical round that moved from project work into Python, ML, DL, RAG, LLMs, deep learning, and performance metrics. Prepare to explain your own implementation choices, model evaluation, and tradeoffs; the exact topic mix may vary.
One AI Engineer candidate met with a senior manager and technical architect for a generally broad final conversation. It included behavioral discussion about unrealistic customer expectations and a brief demo tied to the resume, so a concise project walkthrough may be worthwhile.
