IBM Software Engineer candidates report online coding assessments, technical and resume-based discussions, and behavioral or manager conversations. Prepare for a variable two-to-four-round process spanning coding, fundamentals, and project depth.
$194K
Avg. Base Comp
$265K
Avg. Total Comp
2-4 rounds
Typical Rounds
2 months
Process Length
IBM Software Engineer interviews in these candidate reports commonly begin with an online assessment, although the format varies: some candidates encountered a LeetCode- or HackerRank-style coding task, while another described an AI-run English assessment followed by a 45-minute string-manipulation problem. Several reports then move into technical conversations that mix coding with discussion of the candidate’s background.
For coding preparation, prioritize clear problem interpretation and verbal reasoning. Reported prompts included array and string work and trees; difficulty ranged from straightforward to more demanding medium- or hard-style problems. Project depth is a recurring theme in the reports. Candidates were asked to explain past work, implementation choices, challenges, and follow-up details, sometimes in a manager conversation as well as a technical one.
Technical follow-ups were broad rather than uniform. Individual candidates reported OOP and language fundamentals, SQL, operating systems, networking, architecture, and systems questions such as cache-line tradeoffs. A focused review of the skills on your resume is therefore more useful than assuming every topic will appear. Behavioral discussion may cover teamwork, conflict, role fit, and how you handle project setbacks.
The evidence is varied by team and candidate, so exact sequencing and questions may differ. The supplied reports do not establish a consistent end-to-end timeline.
Synthesized from 36 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 | |
|---|---|
| Largest Salary by Department | |
| Prime to N | |
| Find the Missing Number | |
| Raining in Seattle | |
| Top 5 Turnover Risk | |
| P-value to a Layman | |
| The Brackets Problem | |
| New Resumes | |
| String Mapping | |
| Cyclic Detection | |
| Valid Anagram | |
| Flatten JSON | |
| Three Zebras | |
| Find Duplicate Numbers in a List | |
| Binary Tree Conversion | |
| Target Indices | |
| Hurdles In Data Projects | |
| Total Transactions | |
| Move Zeros Back | |
| Transformer Encoder Layer | |
| Swap Variables | |
| Equal Binary Subarrays | |
| Slow SQL Query | |
| Find Square Root | |
| String Palindromes | |
| Targeted sum | |
| Stakeholder Communication | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening assessment in many processes. Formats varied from a LeetCode- or HackerRank-style coding task to aptitude, reasoning, or communication components; one account described an AI English assessment followed by a 45-minute string-manipulation exercise. Practice reading long prompts carefully and producing a clean solution under a stated time limit.
Technical discussions may combine live or verbal problem-solving with fundamentals. Individual candidates reported arrays, strings, trees, OOP, JavaScript or language basics, SQL, operating systems, networking, and architecture-oriented questions. The specific stack and depth appear to vary, so connect preparation to the technologies and projects on your resume.
Several candidates describe explaining prior projects, technical choices, implementation challenges, and their own contribution. Be prepared to give a structured account of the problem, approach, tradeoffs, outcome, and follow-up questions; some reports place this discussion inside the technical interview and others in a manager conversation.
Candidates report behavioral or manager conversations covering teamwork, conflict, motivation, project setbacks, and role fit. This stage may be separate or combined with technical discussion. Use specific examples that show how you communicated, made decisions, and responded when work did not go as planned.
