IBM Software Developer Engineer interview questions
based on 1.8K ratings - Updated Jun 22, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
48%
Applied online
Applied online
29%
Campus Recruiting
Campus Recruiting
8%
Employee Referral
Employee Referral
7%
Recruiter
Recruiter
3%
In Person
In Person
2%
Other
Other
2%
Staffing Agency
Staffing Agency
Interview search
1,840 interviews
Viewing 6 - 10 of 1,840 Interviews
IBM interviews FAQs
Software Developer Engineer applicants have rated the interview process at IBM with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 80% positive. To compare, the company-average is 71% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer Engineer roles take an average of 19 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at IBM overall takes an average of 40 days.
Common stages of the interview process at IBM as a Software Developer Engineer according to 5 Glassdoor interviews include:
Other: 25%
One on one interview: 25%
Skills test: 25%
Group panel interview: 25%
Here are the most commonly searched roles for interview reports -
Describe the interview process: The process consisted of three rounds: an initial online assessment focusing on data structures and algorithms, followed by two technical video interviews. The technical rounds were intensive, covering system design, live coding, and deep-dive questions into previous project experience and database optimization.
Interview questions [1]
Question 1
Design a scalable URL shortener system and explain how you would handle high read/write throughput.
First round interview. with the hiring manager,then get ghosted for a long time.After nearly two months,the status showed rejected.During waiting,i emailed the hr but get no response.I experenced this situation twice.
Interview questions [1]
Question 1
Basically the tech stack i used in my past experience.
The process started with a recruiter screen, followed by two technical rounds with LeetCode-style problems on trees and graphs, then a system design round, and finally a behavioral interview with the hiring manager. Overall it was well-structured but pretty intense.
Interview questions [1]
Question 1
Implement an LRU cache with O(1) get and put operations.