IBM · Primly Community

went through IBM's full loop for a Staff Software Engineer role last month, here's what actually happened

corp_refugee · 5 replies

applied to a Staff SWE role on the hybrid team in Austin. here's the timeline and what hit:

Round 1: recruiter screen, 30 min. pretty standard. she told me upfront it was 5 rounds total. i respect the honesty.

Round 2: online coding assessment via HackerRank. 3 problems, 90 minutes. medium difficulty, nothing crazy. one DP problem that I'd call LeetCode medium-hard. got through 2.5 of them.

Round 3: 'technical interview' with two engineers. one systems design question (design a notification service for a distributed system), one coding question done live on a shared IDE. no autocomplete, which is fine if you're used to it.

Round 4 + 5: back-to-back behavioral panels, each 45 minutes, each with a different IBM manager. this is where the process gets interesting. both panels were fully STAR-format, no technical at all. they asked things like: 'tell me about a time you had to influence without authority' and 'describe a project where you had to work across geographies and time zones.'

the second one was clearly looking at cultural fit in IBM's 'growth mindset' framework. they literally referenced IBMer values by name.

what surprised me: the behavioral rounds were harder to fake than the coding. they have a rubric and they follow it. if you ramble without structure you can tell they're not writing anything down.

offer came back Band 7. total timeline was 5.5 weeks from application to verbal offer.

5 replies

director_dee

the 'influence without authority' question is literally on every IBM behavioral rubric I've ever seen. i reviewed IBM's competency framework when we were benchmarking our own process. it maps to their 'Collaboration' dimension. if you're prepping, build 2-3 stories around cross-team alignment with stakes, that question is guaranteed.

corp_refugee

yeah i had three of them ready. the one i used was about pushing a security standard adoption across 4 teams that didn't report to me. they responded well to specifics about HOW i got buy-in, not just that i did.

visa_vik

5.5 weeks is actually faster than what I've heard. a friend did the IBM loop for a cloud architect role and it was 8 weeks. did you have any H1B complications or is IBM generally good on sponsorship?

newgrad_neil

what was the HackerRank pass rate like do you know? i've heard IBM screens pretty hard on the OA and a lot of people get stuck there.

corp_refugee

no idea on the aggregate pass rate. anecdotally the problems weren't tricky, they were more about getting through the logic cleanly. no weird edge case traps. just actually code something that works.