Real, anonymous reports from people who interviewed for Software Engineer at Johns Hopkins Applied Physics Laboratory, newest first and distilled into what to expect across the loop.
After applying, I had a quick recruiter/team intro call where I walked through my resume and talked through how I present myself, plus a mix of high-level technical and behavioral questions. It felt pretty laid-back, and the tone was friendly, but it also made it clear that the interview experience could vary a lot by team—mine skewed toward “explain yourself and your fit” more than tricky problem-solving.
My first step was a short zoom call with a small group from the team. We mainly covered behavioral topics and how I’d handled challenges, worked in different environments, and dealt with disagreements. I didn’t get real technical questions there, and it ran about half an hour with four people.
The interview process typically begins with a relaxed phone or video call focused on the candidate's background, interests, and fit for the role, rather than technical assessments. These initial conversations often involve multiple interviewers and emphasize behavioral questions and personal goals.
Candidates can expect a mix of technical discussions that may include presenting past projects or experiences, rather than traditional coding tests. While some interviews touch on technical fundamentals, the focus is often on discussing specific projects and their relevance to the role.
Later stages often involve panel interviews where candidates face multiple interviewers in a structured format, with a strong emphasis on diving deep into their resume and past experiences. Interviewers frequently ask follow-up questions to gauge understanding and clarity on technical topics.
Overall, the interview tone is described as friendly and low-pressure, with a focus on conversation rather than high-stakes testing. Candidates report that the process feels organized and welcoming, although some have experienced misalignment in expectations between interviewers.
Candidates have noted delays and lack of clarity in communication following interviews, with some experiencing long waits for feedback or feeling that the process lacked respect for their time. This can lead to frustration, especially after engaging in lengthy interviews.
While some interviews involve basic technical discussions, candidates should be prepared for questions that require a solid understanding of their past work and the ability to articulate technical concepts clearly. The expectation is to demonstrate practical application rather than just theoretical knowledge.