Real, anonymous reports from people who interviewed for Software Engineer at General Atomics, newest first and distilled into what to expect across the loop.
I went through a fairly standard, multi-round software interview flow with C/C++ focus over ~a few steps.
I had a lighter-weight process that focused more on fit and conversation than heavy coding, with C++/experience checking rather than deep algorithms.
The interview process typically begins with a recruiter screen, focusing on background and fit, often without technical questions. This initial step sets the tone for the rest of the interviews.
Candidates can expect multiple technical rounds, often centered on C/C++ fundamentals, coding concepts, and sometimes practical assessments like whiteboarding or LeetCode-style problems.
Behavioral interviews are common, with a focus on discussing past projects and experiences, emphasizing how candidates approached challenges and collaborated with teams.
The onsite or panel interviews often involve multiple interviewers and can vary in tone, with some candidates reporting unhelpful or critical dynamics that affect the experience.
Candidates frequently report a lack of clear communication regarding outcomes, with delays in feedback and closure after interviews being a common frustration.
Candidates should be prepared for questions that tie technical skills to domain-specific knowledge, particularly in engineering contexts relevant to the company's focus.