IBM New Grad Software Developer Interview: Online Test 400 Points + 3 Technical Rounds

Background

Let me share my situation: I'm a 2026 new grad from a non-elite university (neither 985 nor 211), majoring in Computer Science and Technology. During fall recruitment, I applied for IBM's Software Developer role. Honestly, I was pretty nervous — my university background isn't competitive at IBM, and many 985/211 classmates were also applying. But I ended up getting an offer thanks to a high online test score of 400 points and solid interview performance. I want to share this experience to encourage students from non-elite universities.

Timeline: August 15th applied → August 22nd online test → September 3rd first round → September 10th second round → September 17th third round → September 20th HR round → September 25th offer. The whole process took about 1.5 months. I waited almost two weeks between the online test and first round, almost thinking I hadn't passed.

Interview Process Review

Online Test (August 22nd)

IBM's online test consists of 3 coding problems with a maximum score of 600. I scored 400. The difficulty was roughly 1 easy, 1 medium, and 1 harder problem. My strategy was to secure full marks on the easy problem first, then focus on the medium one, and do my best on the hard one.

Specifically, the first problem was string processing — very easy, done in 10 minutes. The second was a shortest path problem using Dijkstra's algorithm. The third was dynamic programming — I only wrote the recursive version without optimizing to iterative, so it passed only half the test cases. Final score: 400/600, which is quite competitive.

Online test prep tips: IBM's online test is somewhat easier than major internet companies, but don't take it lightly. I recommend practicing IBM-specific problems on LeetCode, focusing on strings, arrays, trees, and graphs. Higher scores give you an advantage — interviewers form a better impression of your fundamentals when they see a high score.

Round 1: C++/Java Fundamentals (September 3rd, ~60 minutes)

IBM's interview lets you choose C++ or Java. I chose Java. The first interviewer was an experienced technical expert who asked detailed questions.

1. Three pillars of Java OOP? How is polymorphism implemented?

Encapsulation, inheritance, polymorphism. Polymorphism implementation: overriding (runtime polymorphism) and overloading (compile-time polymorphism). The interviewer followed up on dynamic binding principles — I explained how the virtual method table determines which method to call at runtime.

2. Java Collections Framework hierarchy? ArrayList vs. LinkedList?

I drew the inheritance diagram for the Collection and Map hierarchies. ArrayList vs. LinkedList: underlying implementation (array vs. doubly linked list), random access performance (O(1) vs. O(n)), insertion/deletion performance (O(n) vs. O(1)), memory usage. The interviewer followed up on ArrayList's resizing mechanism — I explained 1.5x growth and Arrays.copyOf.

3. Interface vs. abstract class? When to use which?

I listed key differences: multiple inheritance for interfaces vs. single for abstract classes, default public for interfaces vs. various access modifiers for abstract classes, no state in interfaces vs. member variables in abstract classes. Use cases: interfaces for behavioral contracts, abstract classes for shared implementations.

4. Hand-write: Implement quicksort

I wrote standard quicksort using the rightmost element as pivot. The interviewer asked me to analyze time complexity — best O(nlogn), worst O(n²), average O(nlogn). Follow-up on optimizing worst case — I mentioned random pivot selection and median-of-three.

5. Operating Systems: What process scheduling algorithms exist?

I listed FCFS, SJF, priority scheduling, round robin, and multilevel feedback queue, focusing on the design philosophy of multilevel feedback queue — balancing response time and throughput. The interviewer followed up on process vs. thread differences, and I compared them across four dimensions: resource allocation, scheduling, communication, and overhead.

Round 2: Project Deep Dive (September 10th, ~65 minutes)

The second round focused on my project, with the project team's technical lead as interviewer.

1. Describe your project in detail

I described an online education platform with three modules: video-on-demand, live classroom, and assignment system. Tech stack: Spring Boot + MyBatis + Redis + RabbitMQ + MySQL. The interviewer drilled into several aspects:

—"How did you implement video-on-demand?" I described integrating Alibaba Cloud VOD, using the player SDK on the frontend, with the backend handling authentication and playback records.

—"How did you handle real-time interaction in live classrooms?" I described a WebSocket + Redis Pub/Sub approach — comments and voice chat pushed via WebSocket, with Redis handling message pub/sub.

—"How did you handle concurrent assignment submissions?" I described using message queues for async processing to avoid overwhelming the database when many students submit simultaneously.

2. What challenges did you encounter in your project?

I described a Redis cache avalanche issue — during a promotion, many caches expired simultaneously, causing all requests to hit the database. Solutions: random expiration times, mutex locks for cache rebuilding, and local cache as a secondary cache. The interviewer followed up on the difference between cache penetration and cache breakdown — I explained Bloom filters for penetration prevention and mutex locks for breakdown prevention.

3. How does your project ensure code quality?

I described code review practices, unit test coverage (JUnit + Mockito), SonarQube static analysis, and CI/CD pipeline automated testing. The interviewer was particularly interested in code reviews and asked about review focus areas — I said logical correctness, exception handling, and code readability.

4. Hand-write: Reverse a linked list

I wrote both iterative and recursive versions. The interviewer asked me to analyze the recursive version's space complexity — O(n) due to the call stack. Follow-up on O(1) space methods — I explained that the iterative version is O(1) space.

Round 3: Comprehensive (September 17th, ~50 minutes)

The third interviewer was a department director who asked more about overall qualities.

1. How do you understand "customer-centricity"?

This is IBM's core value. I answered by combining project experience — when building the online education platform, we collected student and teacher feedback before each feature iteration, prioritizing issues affecting user experience rather than pursuing technically "cool" solutions. The interviewer nodded.

2. What role do you play in a team?

I described myself as the team's "glue" — not the strongest technically, but good at communication and coordination, bringing teammates with different opinions together. I gave an example: early in the project, there were disagreements about tech selection, so I organized a technical review meeting where everyone expressed their views and we reached consensus.

3. What are your strengths and weaknesses?

Strengths: learning ability and teamwork. Weaknesses: sometimes too perfectionistic, causing slower progress — now I've learned to use MVP thinking: finish first, then optimize. The interviewer smiled and said, "Perfectionism isn't bad, but you need to learn to make trade-offs."

4. What do you know about IBM? Why do you want to join?

I discussed IBM's technical capabilities, global platform, and culture of dedication. Why join — because IBM provides young people with opportunities to work on large-scale projects, and the engineering culture is strong. The interviewer followed up with "Can you accept overtime?" — I honestly said, "I can work overtime when projects require it, but I'll work hard to improve efficiency and minimize unnecessary overtime."

5. Any questions for me?

I asked, "What's the growth path for new hires at IBM?" The interviewer detailed the progression from junior engineer to senior engineer to architect, plus IBM's internal training system. This gave me more specific expectations about IBM.

HR Round (September 20th, ~25 minutes)

The HR round was fairly standard — family situation, only child or not, preferred work location, other offers, salary expectations. The HR specifically asked, "Are you aware of IBM's work intensity?" I said I understood and was mentally prepared. Finally, the HR said, "Your online test score was high and your interview performance was good," which made me feel confident.

Key Questions Summary

1. Java OOP three pillars and polymorphism implementation

2. Java Collections Framework and ArrayList vs. LinkedList

3. Interface vs. abstract class differences

4. Hand-write quicksort and optimization

5. Process scheduling algorithms

6. Project architecture and core feature implementation

7. Redis cache avalanche/penetration/breakdown

8. Code quality assurance measures

9. Hand-write linked list reversal

10. Understanding of core values

11. Team role and collaboration

12. Personal strengths and weaknesses

Tips and Advice

1. Online test scores matter — aim high. IBM's online test is a hard cutoff — below 150 points, you basically have no chance. I scored 400, and the interviewer proactively mentioned "good online test score," showing that high scores do add points. I recommend practicing in advance and aiming for 300+.

2. Non-elite university students shouldn't be afraid — let your skills speak. While IBM values educational background, it values actual ability more. A high online test score + solid interview performance can fully compensate for a less prestigious degree. Several classmates from non-elite universities I know got IBM offers.

3. Projects should clearly explain "why." IBM interviewers love to drill into "why did you choose this approach" and "did you consider alternatives." Every technical decision in your project should reflect your own thinking, not just "I followed a tutorial."

4. Understand the company culture. IBM interviews include values-related questions like "customer-centricity" and "dedication culture." I recommend learning about core values in advance and preparing answers that connect with your own experiences.

5. Don't neglect hand-written code. IBM's hand-writing problems are medium difficulty but cover a wide range — sorting, linked lists, trees are all fair game. Practice common hand-writing problems to ensure you can write correct code quickly during interviews.

FAQ

Q: What online test score is needed to advance to interviews?

A: Generally, 150+ gives you a chance, but cutoffs vary by department and role. I recommend aiming for 300+ for safety and 400+ for a clear advantage. Higher scores create better first impressions with interviewers.

Q: Can non-elite university students get into IBM?

A: Yes. While IBM prioritizes 985/211 graduates, it's not a hard requirement. Several classmates from non-elite universities got offers — the key is strong online test and interview performance. Note that some departments (like research labs) have higher degree requirements, but general software development roles are relatively accessible.

Q: Does IBM ask algorithm questions in interviews?

A: Yes, but the difficulty isn't high. Mainly basic algorithms like sorting, linked lists, and trees — not complex dynamic programming or graph theory. Hand-writing problems are guaranteed, so practice common algorithm implementations.

Q: Is IBM's work intensity really that high?

A: It depends on the department and project phase. Some departments do have significant overtime, but not all teams work 996. During the interview, you can ask about the specific team's work pace. IBM's compensation is above industry average, and overtime is paid.

Q: What's the approximate IBM new grad compensation?

A: For 2026 new grads, Level 14 (undergrad) total compensation is roughly 250K-350K RMB, Level 15 (Master's) roughly 300K-450K RMB. Specifics depend on location, department, and performance. Year-end bonuses make up a significant portion — good years may yield 4-6 months' bonus.