IBM · Phone screen
In processIBM Intern Blitz Interviews: 23 Experiences (Part 2 of 3)
IBM software intern and co-op reports, Dec 2025–Apr 2026: 30-minute Blitz screens, résumé talks, one Two Sum, and offers two days to seven weeks later.
At a glance
- Process: often a 30-minute Blitz or résumé interview, sometimes followed by a 45-minute technical round or replaced by one 90-minute panel; one co-op had no OA (24, 26, 29, 31).
- Asked recently: résumé and project discussion in 5 of 23 reports, behavioral in 3, live coding in 2 (Two Sum in 36 and an array problem in 40), and computer architecture with multithreading once (40).
- After the interview: offers came 2 days (31), 12 days (27, 33), about three weeks (37, 38) or seven weeks (41) later. The portal sometimes showed a rejection before any email (22, 35), and some candidates were moved to another team's requisition (25, 38).
- Practise first: Two Sum.
Coverage: IBM software internships and co-ops: Software Developer, SDE, Software Engineering, Application Developer and Developer interns, plus fall software co-ops. Austin, SVL and San Jose where stated. Twenty-three reports, entries 20–42, with interviews from late 2025 to late April 2026.
In this series
- Part 1: Aug–Oct 2026: OAs, video assessments, screening updates and the first live interviews.
- Part 2 (current): earlier interview rounds: Two Sum, résumé and behavioral rounds, a 90-minute panel and interview-to-offer waits.
- Part 3: undated Summer 2026 reviews (Git, ML and motivation questions) and seven reports with role or cycle gaps.
What came up
Most of these candidates shared timing, not questions. The ones who did describe a round talked about their résumé, a few behavioral prompts, and very little coding.
| Topic | Reports | Last seen |
|---|---|---|
| Résumé and project discussion | 5 of 23 | Feb 2026 |
| Behavioral questions | 3 of 23 | Mar 2026 |
| Live coding | 2 of 23 | Feb 2026 |
| Computer architecture and multithreading | 1 of 23 | Jan 2026 |
A candidate can appear in more than one row.
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Two Sum | 1 | Feb 2026 |
| A medium array-manipulation problem (not named) | 1 | Jan 2026 |
Technical discussion
| Question | Reports | Last seen |
|---|---|---|
| Computer architecture, including multithreading | 1 | Jan 2026 |
23 detailed candidate timelines, loops, and screens
20: Application Developer: five weeks in "In Interview Process"
Interview date: about Apr 22, 2026 · Role: Application Developer Intern
- Matched into this role after applying to another. Five weeks after the interview the portal still said "In Interview Process", and no location was ever given.
21: Developer Intern 2026: a 30-minute interview and an offer
Interview date: Apr 10, 2026 · Role: Developer Intern 2026 · Result: Offer (Apr 14)
- A 30-minute interview invite, then an offer four days later. No questions were shared.
22: A portal rejection after an interview that felt good
Interview date: about Apr 2, 2026 · Role: Software intern · Result: Portal showed "No Longer Under Consideration"
- About six days after the interview the portal changed status, which surprised them because it had gone well.
23: A scheduled interview was canceled
Report date: Mar 29, 2026 · Role: SWE Intern · Result: Rejected
- After the assessment and an administrative questionnaire, the live interview was canceled and a rejection followed. A recruiter follow-up went unanswered.
24: Fall 2026 co-op: scheduled with no OA
Interview date: about Mar 17, 2026 · Role: Software Developer Fall Co-op 2026
- A candidate-information form, then a 30-minute interview invite within minutes. No OA for this application.
- About two weeks after the interview the portal returned to recruiter review. No result yet.
25: Austin 2026: rejected on a new requisition
Interview date: Mar 16, 2026 · Role: Software Developer Intern 2026 · Location: Austin · Result: Rejected on the new requisition
- At the end the interviewer said they would attach notes to the résumé and send them to the recruiter.
- A newly created requisition then moved out of consideration with a rejection email, while the original Austin application stayed under recruiter review.
26: A 30-minute Blitz of describe-a-time questions
Interview date: Mar 11, 2026 · Role: Software intern · Result: Rejected (Mar 20)
- Announced as behavioral and technical, the Blitz round was only describe-a-time questions. Their OA had been in November 2025.
27: An SDE fall co-op offer after twelve days
Report date: Mar 11, 2026 · Role: SDE Fall Co-op · Result: Offer
- The offer came twelve days after the interview. No questions or length were shared.
28: Austin 2026: a new application after a rejection
Report date: Mar 10, 2026 · Role: Software Developer Intern 2026 · Location: Austin · Result: Rejected
- Rejected from the Austin application; a general intern 2026 application then appeared in the portal. No further interview was reported.
29: A Blitz screen, then a 45-minute technical
Interview date: Feb 20 and Mar 5, 2026 · Role: Software intern · Result: Offer (Mar 20)
- Blitz (30 min): a résumé deep dive and behavioral questions.
- Technical (45 min): questions not shared. Positive feedback, then an offer on March 20.
30: A 30-minute talk about résumé and interests
Interview date: Feb 20, 2026 · Role: Software Co-op, Fall 2026 · Result: Rejected
- A 30-minute conversation about the résumé and their interests, no coding. Rejected later that week.
31: One 90-minute panel, then a quick offer
Interview date: Feb 16–20, 2026 · Role: Software Engineering Intern · Result: Offer
- A hiring manager reached out early in a week; the 90-minute panel came the next week, and the offer two days later. One round in total; no questions shared.
32: SVL: waiting after last week's interview
Interview date: Feb 16–20, 2026 · Role: SDE Intern · Location: SVL · Result: Pending
- Interviewed the week before and still waiting. No questions were shared.
33: Austin: a February Blitz, a March offer
Interview date: Feb 19, 2026 · Role: SDE Intern · Location: Austin · Result: Offer (Mar 3)
- A Blitz interview; about a week and a half later, a citizenship-information form and then the offer, followed by a background check.
34: San Jose fall co-op: a résumé deep dive that ran long
Interview date: Feb 2026 (by Feb 19) · Role: Software Co-op, Fall 2026 · Location: San Jose
- A résumé deep dive that ran over time. Whether another round followed was unclear. Their LeetCode and system-design prep was not tested.
35: Austin: the portal changed before the email
Interview date: Feb 18, 2026 · Role: SDE Intern · Location: Austin · Result: Rejected
- On February 23 the portal showed "No Longer Under Consideration" with no email; a rejection was later confirmed. They felt underprepared.
36: Austin: ten minutes on experience, then Two Sum
Interview date: Feb 6, 2026 · Role: Software Developer Intern, Summer 2026 · Location: Austin
- About ten minutes on one past experience from the résumé, then Two Sum. The talk ran past the scheduled end. One round; no result shared.
37: Austin summer internship: an offer after three weeks
Interview date: early Feb 2026 · Role: SDE / cloud development intern · Location: Austin · Result: Offer
- The offer came about 20 days after the interview; a recruiter follow-up in the meantime went unanswered.
38: SVL interview, Austin offer
Interview date: Feb 3, 2026 · Role: Software intern 2026 · Result: Offer (Austin)
- After repeated OAs, an unexpected calendar invite. The interview mixed behavioral and technical talk with detailed follow-ups on projects and work experience, and no LeetCode.
- The SVL team was full, so the SVL requisition showed a rejection while an Austin application moved ahead: a verbal offer about two weeks after the interview and the letter on February 24.
39: Austin: the interviewer answered a follow-up
Interview date: about Jan 31, 2026 · Role: Software Development Intern · Location: Austin
- Two weeks after the interview, they emailed the interviewer, who replied within two hours to say they would work with HR and expected an update the next week.
40: Architecture, multithreading and an array problem
Interview date: Jan 23, 2026 · Role: Software intern
- Computer-architecture questions, including multithreading, then one medium array-manipulation problem. Neither was described further.
41: Austin: a January interview, a March offer
Interview date: Jan 22, 2026 · Role: Software Development Intern · Location: Austin · Result: Offer (Mar 10)
- They thought the interview went well and waited about seven weeks for the offer. No questions were shared.
42: Summer 2026: a first interview in late 2025
Interview date: early Dec 2025 · Role: Software Developer Intern, Summer 2026
- They had finished a first interview a few days before December 6, 2025, and were waiting. No other details.
Patterns across the reports
- Blitz rounds are short and behavioral. All three Blitz interviews were 30 minutes on the résumé or describe-a-time questions (26, 29, 33).
- Requisitions change. Two candidates saw a new or replacement requisition appear during the process (25, 38), and one saw a new application after a rejection (28).
- The portal moves first. Status changed before any email in 22 and 35.
Common questions
What is an IBM Blitz interview?
A 30-minute first interview on the résumé and behavioral or describe-a-time questions (26, 29, 33); some candidates then had a 45-minute technical round (29).
How long does IBM take to send an intern offer?
From two days (31) to twelve days (27, 33), about three weeks (37, 38) or about seven weeks (41).
Does IBM ask LeetCode in intern interviews?
Rarely: Two Sum once (36) and one array problem (40). 38 said there was no LeetCode.
Keep practicing
- Two Sum: the coding question from 36.
- IBM problem bank: every IBM coding question on FastPrep (sign-in needed).
- IBM software intern interviews: 15 live-interview reports from the same cycle.
- IBM interview page and IBM hiring insights.
- Experience feed: the latest interview write-ups.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.