RepostedIBM logo

IBM · OA → Phone screen

In process

IBM Software Intern Interviews: 44 Experiences (Part 1 of 3)

Software engineer · InternshipSep 2026
Shared byjanebeingjane

IBM software intern and co-op reports, Aug–Oct 2026: a HackerRank OA with coding plus a repository fix, a video assessment, then a résumé-heavy interview.

At a glance

  • Process: a HackerRank OA (one or two coding problems plus a repository task, 80 minutes in one report), a recorded video competency assessment, a screening update saying interviews come 60–120 days after assessments, then usually one live interview of about 45 minutes (03, 04, 06, 10, 15).
  • Asked recently: repository implementation or debugging in 5 of 19 reports (API routes, a Django app with three bugs, filtering, pagination and cache repair); standalone coding in 5; résumé or experience questions in 3.
  • Difficulty: OA coding ranged from easy (03) to medium/hard (15); two candidates gave up on or could not solve a coding task (17, 19). Live rounds had no LeetCode in the reports that described them (01, 07, 10).
  • After the interview: results came in about four days (07) to a week (01); several were still waiting when they posted (09, 11, 12, 14).

Coverage: IBM software internships and co-ops (SWE Intern 2027, Software Developer Intern 2027, SDE Intern, backend intern, Salesforce application developer intern 2027, spring SDE co-ops). Austin, SVL, North Carolina, Rochester and Tucson where stated. Nineteen reports, entries 01–19, from August 16 to October 26, 2026; eight confirm or imply a 2027 start, eleven do not state it.

In this series

  • Part 1 (current): Aug–Oct 2026: OAs, video assessments, screening updates and the first live interviews.
  • Part 2: 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

The OA is where the technical work happens: a coding problem next to a real repository to fix or extend. The live interviews that were described stayed on the résumé.

Topic Reports Last seen
Repository implementation or debugging 5 of 19 Oct 2026 (report date)
Standalone coding task 5 of 19 Oct 2026 (report date)
Résumé or past-experience discussion 3 of 19 Oct 2026
Behavioral or video competency questions 3 of 19 Oct 2026
Backend filtering, pagination and cache repair 2 of 19 Sep 2026 (report date)

A candidate can appear in more than one row. Eleven reports were application or waiting updates with no topic.

Questions we found

Project Coding

Question Reports Last seen
Repair backend listing filters, pagination and cache invalidation 2 Sep 2026 (report date)
Implement API routes in an IDE 1 Sep 2026 (report date)
Fix three bugs in a Django repository 1 Aug 2026 (report date)
Debug an existing repository (details not shared) 1 Sep 2026

Algorithms / Data Structures

Question Reports Last seen
Medium/hard dependency or graph task 2 Sep 2026 (report date)
Easy coding problem (not named) 1 Sep 2026 (report date)
Two-pointer problem (not named) 1 Aug 2026 (report date)

19 detailed candidate timelines, loops, and screens

01: North Carolina: a second invite, then an offer

Report date: Oct 19–26, 2026 · Role: IBM software internship, 2027 · Location: North Carolina · Result: Offer

  1. A second interview invitation came on October 19; an offer by October 26.
  2. The interview centered on knowing their résumé, with no LeetCode question.

09: Rochester: waiting after a Wednesday interview

Interview date: Oct 21, 2026 · Role: SWE Intern · Location: Rochester · Result: Pending

  1. A completed SWE intern interview; they asked others how long they had waited. No length or questions were shared.

07: Austin spring co-op: résumé and behavioral, then an offer

Interview date: Oct 19, 2026 · Role: SDE Co-op, Spring (2027 inferred) · Location: Austin · Result: Accepted offer

  1. One interview on the résumé and behavioral questions, on a Monday; the result came by Friday (October 23) with an email confirmation.

10: A 45-minute interview about their own experience

Interview date: about Oct 18–19, 2026 · Role: Software intern (start year not stated)

  1. A 45-minute mix of behavioral questions and general technical questions about their own past experience, with no implementation task. No result yet.

02: SVL Summer 2027: interviewed on Friday

Interview date: Oct 16, 2026 · Role: SDE Intern, Summer 2027 · Location: SVL · Result: Pending

  1. They asked about the upcoming interview, then confirmed they had done it on Friday and were waiting, noting weekends do not count as business days. No questions were shared.

11: SVL thread: waiting after a Friday interview

Interview date: Oct 16, 2026 · Role: SDE intern (start year not stated) · Result: Pending

  1. Interviewed on Friday and asked whether anyone had heard back. No questions or length were shared.

12: Austin thread: a Thursday interview, result pending

Report date: Oct 15, 2026 · Role: Software Developer intern (start year not stated) · Result: Pending

  1. Interviewed on a Thursday and was still waiting. No questions were shared.

08: Spring co-op: coding plus repository debugging in the OA

Report date: Oct 14, 2026 · Role: Spring Co-op Software Developer Intern (2027 inferred)

  1. The OA, taken one or two months earlier, had LeetCode-style coding and a repository-debugging section; neither task was identified.
  2. A live technical interview was booked for that week.

13: SVL: interviews had started

Interview date: Oct 12, 2026 · Role: SDE intern (start year not stated) · Location: SVL

  1. They interviewed at SVL the day before posting and said interviews had begun. Question details went to private messages.

14: Austin thread: no answer a week later

Interview date: about Oct 5–9, 2026 · Role: Software Developer intern (start year not stated)

  1. Interviewed the week before and still had no response. No questions or result were shared.

16: Assessments done in September, scheduling pending in October

Report date: Sep 22 – Oct 2026 · Role: Software Engineer Internship (start year not stated)

  1. The portal showed "All Assessments Complete" on September 22, recruiter review on September 28 and "In Interview Process" on October 13, with a candidate-information form.
  2. Still waiting for an actual interview booking, with no recruiter contact.

15: Backend intern: an 80-minute coding and repository assessment

Report date: Sep 25, 2026 · Role: Backend Intern (start year not stated)

  1. An 80-minute assessment: a medium/hard coding task they tied to a dependency or graph problem, and debugging a codebase.
  2. The repository task was the same one another candidate described: repair backend filtering, pagination and cache invalidation. No score or result was shared.

03: SWE Intern 2027: an easy task and API routes

Report date: Sep 23, 2026 · Role: SWE Intern 2027

  1. A two-question HackerRank assessment: an easy coding problem and an IDE task implementing API routes (endpoints not described).
  2. A competency-interview invite came the next day.

17: A second intern on the same repository assessment

Report date: Sep 12, 2026 · Role: Software intern (start year not stated)

  1. They got the same assessment as 15: a dependency or graph coding task and the backend filtering, pagination and Redis-cache repair exercise.
  2. They gave up and submitted. No score was reported.

04: SWE Intern 2027: passed the initial screen

Report date: Sep 3, 2026 · Role: SWE Intern 2027

  1. Assessments done around "the 18th", then under review.
  2. The update said they passed the initial screen and that interviews come roughly 60–120 days after assessments. No booking yet.

18: An OA, then a virtual-interview link

Report date: Aug 29, 2026 · Role: Software intern (start year not stated)

  1. Finished the OA and received the next-stage virtual interview link; a later October invite mentioned Tucson. No questions or score were shared.

19: A two-pointer task and three Django bugs

Report date: Aug 29, 2026 · Role: Software intern (start year not stated)

  1. A HackerRank test with one coding problem (two pointers), which they did not solve.
  2. A mock repository: run a Django development server and fix three bugs. AI was not allowed and they had to unplug a second monitor. Another commenter remembered six bugs, possibly a different variant.

05: Salesforce application developer: a screening email

Report date: Aug 28, 2026 · Role: Intern Application Developer – Salesforce 2027

  1. An initial-screening update saying selected candidates would be interviewed 60–120 days after assessments.
  2. They had not taken a coding section or the recorded behavioral assessment for this role, and guessed a perfect score from another IBM intern OA was reused; IBM did not confirm that.

06: Software Intern 2027: done, but the portal said otherwise

Report date: Aug 16, 2026 · Role: Software Intern 2027

  1. Completed the coding OA and the digital competency assessment, which played videos and asked for spoken responses; the portal still showed a start-assessment prompt.
  2. A co-op application's link said the same OA was already complete. No result yet.

Patterns across the reports

  1. A repository task in the OA. Five candidates described one: API routes (03), unnamed debugging (08), filtering, pagination and cache repair (15, 17) and Django bugs (19).
  2. A long wait between assessment and interview. Two screening emails said 60–120 days (04, 05); 16 waited from September 22 into October without a booking.
  3. Résumé-first live rounds. Every described live interview focused on the résumé or past experience (01, 07, 10).

Common questions

What is on the IBM software intern OA?

A HackerRank test with one or two coding problems and a repository task, such as API routes or fixing a Django app (03, 15, 19). There is also a video competency assessment (06).

How long after the IBM assessment do interviews start?

The screening email said 60–120 days after assessments (04, 05).

Does the IBM intern interview have LeetCode?

Not in the live rounds described here (01, 07, 10); coding was in the OA.

How fast does IBM reply after the interview?

Four days for an Austin co-op (07) and about a week for a North Carolina intern (01).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.