Real, anonymous reports from people who interviewed for Software Engineer at NASA Jet Propulsion Laboratory, newest first and distilled into what to expect across the loop.
I went through a lighter-weight set of rounds for a Software Engineer role, mostly behavioral/resume review, and it usually moved quickly.
I interviewed for a Software Engineer role in an average-difficulty process where the emphasis was on conversational fit plus being able to clearly reason from my experience.
The interview process typically begins with a quick introductory call with a recruiter or team member, focusing on the candidate's background, fit for the role, and availability. This step is crucial for setting the tone of the subsequent interviews.
Candidates can expect light technical discussions that may include basic programming concepts or problem-solving questions, but heavy coding challenges are often not a central focus. Some interviews may involve project presentations with follow-up questions.
Behavioral interviews are common, with a strong emphasis on understanding the candidate's past experiences and how they relate to the role. Candidates should prepare to discuss their contributions and thought processes in detail.
Some candidates experience panel interviews where multiple engineers or managers assess their fit and technical knowledge. These sessions can be intense, with a focus on specific technical expertise and problem-solving skills.
Candidates reported varying experiences with scheduling, including last-minute changes or unclear communication about the interview process, which can create a sense of disorganization.
The outcome of interviews can vary widely, with many candidates not receiving offers despite feeling well-prepared. Success often hinges on the alignment of technical skills with specific role requirements.