Real, anonymous reports from people who interviewed for Software Engineer at JPL/NASA, newest first and distilled into what to expect across the loop.
I experienced an average-difficulty interview process where the early rounds were conversational, and the later parts emphasized how I think through problems and exactly what I did in my own work.
I went through a more demanding, average-to-difficult JPL loop with many interviews and a strong emphasis on technical understanding of real systems and how I would respond to an ongoing problem.
The interview process typically begins with a recruiter or HR reaching out to coordinate interviews, which may include initial screenings and discussions about the candidate's background and fit for the role.
Candidates can expect multiple rounds focused on behavioral questions and discussions about their past experiences, often using the STAR method to articulate their contributions and motivations.
Interviews emphasize technical understanding of systems and problem-solving approaches, often without live coding but requiring detailed explanations of past work and contributions to projects.
Some candidates will need to deliver a presentation on previous work, followed by a panel interview where they face in-depth questions from multiple interviewers, testing both technical depth and communication skills.
The interview experience can vary from low-pressure, conversational styles to high-pressure, technical environments that require precise and detailed responses, with candidates noting the importance of clarity and confidence.
Candidates often report not receiving offers, with common takeaways highlighting the need for concrete examples of past work and a clear demonstration of technical and operational understanding.
