IBM software engineer candidates describe an online coding assessment, a technical interview built around the resume and CS fundamentals, and a behavioral or manager conversation. Here is what they report and how to prepare.
$133K
Avg. Base Comp
$170K
Avg. Total Comp
Not reported
Typical Rounds
1 month
Process Length
Candidates who interviewed for IBM software engineering roles describe a loop that rewards solid fundamentals and clear explanations more than hard algorithm puzzles. Many start with an online assessment. Reported formats include:
Problems named include binary conversion and Roman numerals. One candidate also heard the process could include an English assessment and a group discussion.
The live technical round usually leans on the resume. Candidates report questions about the languages and frameworks they listed, including Java, Spring Boot, SQL, microservices and JavaScript's == versus ===. Others describe encapsulation, Java multithreading with synchronized versus Lock, operating systems and networking questions. Some also had small live coding tasks, such as implementing a reduce method. One candidate was asked to explain a real-time collaboration project in depth. Another was told the team wanted Next.js and unit testing experience beyond the React stack they had listed. Interviewers seemed to care whether you actually understand the tools you claim.
The last stage is typically a hiring manager, HR or behavioral conversation about past projects, teamwork, challenges and fit. One candidate also discussed salary expectations at this stage. Outcomes were mixed, with both offers and rejections reported, and the loop appeared to vary by team and role. One candidate said the process took about a month. Another said things slowed down considerably after the assessment.
Synthesized from 48 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 process felt pretty structured and, overall, smooth. I first had an online English assessment run by AI, which was a little unusual but straightforward enough. After that came an offline coding round with one fairly long string-manipulation problem. The coding time was 45 minutes, and that felt tight because the prompt itself was lengthy, so I had to spend a bit of time just unpacking what was being asked before writing anything. After that, there were additional interview rounds, including a technical screen and conversations with a manager and a technical lead.
The technical parts were a mix of fundamentals and practical discussion. In one round I started with basic OOP concepts and then the interviewer gradually moved deeper into DSA, with trees coming up for me specifically. There were also questions about my projects, and I got the sense that if I could explain my work clearly and answer follow-ups well, that carried a lot of weight. Another round was more experience-focused, where I had to walk through my thought process on a problem and talk about how my background matched the role. The manager conversation was mostly about past projects, while the technical lead asked one hardware-oriented question about the pros and cons of larger cache lines for CPUs, which was a bit unexpected for a software engineer interview. One of the other technical interviews also touched on architectural challenges and conundrums, so it wasn’t just coding.
I didn’t get an offer in the end, but the process itself was organized and the interviewers were professional. My main takeaway is to be ready for a broad mix: string coding under time pressure, OOP and tree-based DSA, project deep-dives, and at least one architecture or systems-style question.
Prep tip from this candidate
Practice writing clean solutions for long string-manipulation prompts within 45 minutes, and be ready to explain your projects in depth. I’d also review trees, basic OOP, and a few systems questions like cache-line tradeoffs and architecture discussions.
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 | |
|---|---|
| Top 5 Turnover Risk | |
| Prime to N | |
| Largest Salary by Department | |
| Raining in Seattle | |
| Find the Missing Number | |
| P-value to a Layman | |
| The Brackets Problem | |
| New Resumes | |
| Total Transactions | |
| String Mapping | |
| Cyclic Detection | |
| Three Zebras | |
| Valid Anagram | |
| Flatten JSON | |
| Binary Tree Conversion | |
| Find Duplicate Numbers in a List | |
| Target Indices | |
| Hurdles In Data Projects | |
| Move Zeros Back | |
| Transformer Encoder Layer | |
| Equal Binary Subarrays | |
| Swap Variables | |
| Slow SQL Query | |
| Find Square Root | |
| String Palindromes | |
| Targeted sum | |
| Client Solution Pushback | |
| Stakeholder Communication | |
| Why Do You Want to Work With Us |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with an online assessment, often on HackerRank. Reported formats include one easy and one harder problem, two medium LeetCode-style array questions, and a one-hour test with a coding problem plus an API mini-project. Others had a 75-minute test with three string-focused problems, or an MCQ test. One candidate heard the process could also include an English assessment and group discussion.
Some candidates describe an early HR call or virtual screen. For one candidate, this call set up the interview flow. Another candidate's screen covered introductions, the team, their resume and soft skills, and a question about a disagreement with a coworker, then closed with a technical question. Whether this step appears seems to depend on the team and role.
Technical rounds focus on the stack listed on the resume, and one ran about 30 minutes. Questions mentioned include Java and OOP basics, encapsulation, synchronized versus Lock, Spring Boot, SQL, microservices, operating systems, networking, and JavaScript == versus ===. Live coding included implementing a reduce method and solving string problems. Some interviewers asked for project deep dives.
Candidates report a closing conversation with a hiring manager, HR, or both. Reported topics include past projects and challenges, how prior work relates to the role, teamwork, salary expectations and cultural fit. One candidate described a 30-minute manager round as friendly and brief. Another said the process slowed after the assessment.
