Real, anonymous reports from people who interviewed for Software Engineer at Johns Hopkins University Applied Physics Laboratory, newest first and distilled into what to expect across the loop.
I started with an initial screening with a team member, and after that I moved into a longer sequence with three short rounds, each around fifteen minutes, with different people on the team. The whole thing felt tightly scheduled and more conversational than interview-y, but the focus stayed on how I work and how my background fit what the group was doing.
My application process started online, and once I was selected, the scheduling was handled by a recruiter. I got contacted to schedule the first round with a team member, and if I passed that step the recruiter let me know I was moving forward and coordinated the next interviews with managers.
The interview process typically begins with a phone screen, followed by a series of back-to-back interviews that may include both behavioral and technical discussions. The overall flow is structured, but candidates noted variability in communication and timelines, leading to feelings of frustration in some cases.
Many interviews emphasize behavioral questions, focusing on candidates' past experiences, teamwork, and problem-solving abilities rather than technical coding challenges. This approach aims to assess cultural fit and how candidates handle real-world situations.
While there are some technical components, they often revolve around discussions of past projects and specific domain knowledge rather than traditional coding tests. Candidates are expected to demonstrate their reasoning and understanding of technical concepts relevant to the role.
Several candidates reported a requirement to present their work or projects during the interview, which involved explaining their contributions clearly and engaging with follow-up questions from the interviewers. This aspect can be a significant part of the evaluation process.
The overall atmosphere of the interviews tends to be conversational and relaxed, encouraging candidates to ask questions and engage in dialogue. However, some candidates felt that this informal tone could lead to misunderstandings about expectations for their participation.
Candidates experienced a range of timelines for the interview process, with some reporting quick turnarounds while others faced prolonged waits and communication gaps. This inconsistency can affect candidates' perceptions of the organization.
