Real, anonymous reports from people who interviewed for Software Engineer at Sandia National Laboratories, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role in a difficult, remote multi-interviewer panel that was strongly technical over a month-plus timeline.
I interviewed for a Software Engineer role with a very structured, presentation-led journey culminating in a visit.
The interview process typically spans several weeks to over a month, often involving multiple rounds including phone screens, technical presentations, and panel interviews. Candidates should be prepared for a lengthy decision wait, as follow-ups can be slow.
Many candidates are required to deliver a technical presentation on their past work or research, followed by in-depth discussions with interviewers. This aspect emphasizes the importance of clear communication and technical depth related to one's projects.
Interviews often include significant behavioral components, focusing on cultural fit and past experiences, with questions framed around STAR techniques. Candidates should be ready to discuss their teamwork and problem-solving approaches.
While some interviews include light technical questions, others may delve into more complex problem-solving scenarios, particularly during panel discussions. Candidates should be prepared for varying levels of technical scrutiny depending on the interview format.
The interview atmosphere is generally described as friendly and supportive, with a focus on ensuring candidates feel comfortable. However, some candidates noted instances of rushed interviews or disorganized processes that impacted their experience.
Candidates reported that the interviews often assessed alignment with the specific role and its requirements, sometimes prioritizing fit over technical prowess. Understanding the role's expectations and how one's background aligns is crucial.