How IBM fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
IBM placement process includes: 1. Online Assessment (90 minutes) - Aptitude, technical, and coding sections. 2. Technical Interview (45 minutes) - Programming problems, technical concepts, and project discussion. 3. HR Interview (30 minutes) - General discussion about compensation and role expectations. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 6.5+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): Associate: ₹4.5-6 LPA . Confirm on your offer letter.
How to use this page
Read the round table first, then the experiences. Practise the coding patterns with edge cases, and keep one clear story each for ownership, conflict, and a project failure.
Round
Duration
What they test
Online Assessment
90-120 min
Aptitude + coding
Technical Interview
30-45 min
OOPs, SQL, DSA basics, projects
HR Interview
20-30 min
Relocation, shifts, motivation
Profile: B.Tech CSE, ~8.0 CGPA, tier-2 college, one internship, steady DSA practice
Online aptitude / written round
Sections matched what the college placement email promised, speed and accuracy mattered more than fancy tricks.
Shortlist usually followed within a week if you cleared the cutoff.
Technical interview
Coding: Palindrome / reverse a linked list, expected approach: two pointers. They probed complexity and edge cases.
Follow-up: Character frequency in a string, hashmap.
Domain chat around OOPs and SQL . Plain explanations worked better than buzzwords.
Detailed project discussion: stack choice, hardest bug, and what you would rebuild.
HR / managerial
Why this company?
Night shifts / relocation
Keep answers short, situation, what you did, result.
Result: Selected
What helped: Talking through the approach before coding, and connecting project work to IBM’s world (OOPs).
Profile: B.Tech IT / ECE, ~7.2 CGPA, strong projects, average contest rating
What differed
Screening felt tighter on time; one question needed an optimised pass to stay competitive.
Later round leaned into Java : APIs, data choices, and failure modes at a fresher depth.
Warm-up: SQL: max salary per department: GROUP BY / joins.
Mistakes that hurt other candidates
Coding before clarifying constraints
Treating HR as a formality
System-design jargon without a simple bottleneck story
Result: Selected after HR / managerial
Takeaway: At IBM, clear DSA plus a coherent story on OOPs usually beats a high CGPA with weak explanation.
Palindrome / reverse a linked list . Usually expects two pointers
Character frequency in a string . Usually expects hashmap
SQL: max salary per department . Usually expects GROUP BY / joins
Discussion on OOPs and SQL , bottlenecks, failure modes, simple APIs
Detailed project discussion, architecture, hardest bug, what you would change
Why this company?
Night shifts / relocation
Bond (if mentioned in the college placement email)
Where you see yourself in a few years
Clear the screening round first. Timed practice beats last-minute topic hopping.
For domain questions, explain OOPs in plain language, inputs, outputs, what breaks at scale.
OOPs and SQL still open a lot of IBM panels. Do not skip fundamentals.
HR answers should be concrete. One story with a result beats five slogans.
If you do not know something, say so and outline how you would find out.
After technical rounds, IBM usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
HR interview questions→
Common IBM HR questions, sample answer frames, and STAR tips.
TCS · Microsoft · Accenture · Infosys · Wipro · Cognizant