Real, anonymous reports from people who interviewed for Software Engineer at Supermicro, newest first and distilled into what to expect across the loop.
I can’t group these further without risking mixing distinct timelines/paths into the same story, so I’m leaving them out where details are either unique or insufficient for a coherent shared journey.
I applied for the Software Engineer role and got through an online assessment, but I was rejected shortly after, in a quick OA-to-decision timeline.
The interview process begins with an online assessment that typically includes DSA coding questions and may also feature behavioral or situational questions. Candidates should treat this stage as a critical cutoff point, as many report being rejected shortly after this step.
Candidates can expect multiple technical interview rounds focusing on DSA, system design, and sometimes role-specific topics. The difficulty tends to increase progressively, requiring strong coding skills and the ability to discuss design principles.
Behavioral interviews are integrated throughout the process, often requiring candidates to align their responses with leadership principles using the STAR method. Deep knowledge of personal experiences related to these principles is essential.
The interview process can be lengthy and demanding, with some candidates experiencing back-to-back interviews that test their stamina and consistency in responses. It's advisable to prepare for a potentially exhausting schedule.
Many candidates report not receiving offers, often due to a combination of insufficient technical depth and inadequate preparation for behavioral questions. It's important to reflect on feedback and adjust preparation strategies accordingly.
For certain roles, especially those with a technical focus, candidates may need to demonstrate domain-specific knowledge, such as networking or physical design methodologies, alongside general coding skills.