just got through the Bain onsite for a senior ML engineer role. writing it up same day while it's fresh.
it's done virtually now. four sessions back to back with a 10-minute break between each. total time about 4.5 hours.
session 1: coding (60 min) one interviewer. two problems, lighter and harder. i got a dynamic programming problem (medium) and a string parsing one (harder). they let you code in whatever language. i used Python. the harder problem had an edge case i didn't catch until they nudged me. felt medium-hard overall.
session 2: coding (45 min) one problem but more discussion-heavy. they asked me to code a solution then immediately said 'now walk me through what breaks at scale.' it transitioned into a mini design conversation. this felt deliberate, like they want to see if you just write code or actually think about it.
session 3: system design (70 min) two interviewers this time. the prompt was designing a data pipeline for aggregating client engagement data across multiple enterprise tenants with freshness SLAs. right in my wheelhouse but still took 10 min of clarifying questions to scope properly. they seemed pleased that i slowed down.
they probed: failure recovery, data quality monitoring, schema evolution, how you'd alert on freshness degradation. all real problems i've dealt with. felt like a conversation rather than a test.
session 4: behavioral / values (45 min) coverage of standard STAR questions but with follow-up probes. 'tell me about a time you disagreed with a senior stakeholder' and 'describe a project that didn't go as planned' both came up.
overall: the day felt long but well-structured. no trick questions, no weird brain teasers. they're hiring for people who can actually think through problems, not people who've memorized solutions.
7 respuestas
ds_dmitri (Primly starter)
the 'coding then immediately what breaks at scale' transition is actually a pretty smart format. tests whether the candidate has any operational intuition or just grinds algorithms in a vacuum. did they tell you upfront that was the format or did the pivot happen mid-session?
ml_mike (Primly starter)
no heads up. mid-session pivot. the interviewer said 'ok great, that works. now let's say this runs in production and you're ingesting 10x the load - what do you change?' felt like a natural extension but you have to mentally shift gears.
de_derek (Primly starter)
the schema evolution question in system design is one i always prep now. it sounds boring but it filters out a lot of candidates who haven't had to maintain a production data pipeline for more than 6 months.
corp_refugee (Primly starter)
how long after the onsite did you hear back? i'm at the waiting stage and the silence is starting to do things to me.
ml_mike (Primly starter)
got an email from my recruiter 8 days later saying they were completing debrief. then an offer call 4 days after that. so 12 days total from final round to verbal offer. not fast but not egregious either.
member
Hii same i received the call from recruiter she forwarded my resume to HM that role i have applied is for software engineer role tech solutions she said if shortlisted i will get interview call 4-5 rounds will be there coding and design so whats you thiught in my case they will follow the same process i have 4 yrs of exp
hardware_hugo (Primly starter)
don’t know for your exact “tech solutions” SWE loop; my debrief was specifically senior ML eng and it was 4 virtual sessions (2 coding, 1 design, plus another round i didn’t finish typing up). safest assumption is similar mix of coding + design, but scope/level will vary,ask the recruiter what the round types are and how they map to your level.