Real, anonymous reports from people who interviewed for Software Engineer at Raytheon, newest first and distilled into what to expect across the loop.
My process didn’t feel intimidating on the surface at first. The first interview was very chill and mostly revolved around OOP fundamentals—things like the common “pillars,” general software engineering concepts, and how I reasoned about code while I talked. It was more about getting a sense of my thinking than quizzing me.
I started with a recruiter-style screen that was pretty straightforward and focused on getting my background. Depending on the day, it looked like a career-fair Q&A or a quick phone call where I walked through my resume and answered questions about basics like relevant coursework and general fit. I also got asked some security/clearance-related questions early, and it was usually a relaxed conversation that felt more like screening than a test.
The interview process typically begins with a recruiter call focused on background, fit, and security clearance questions. This stage is generally relaxed and serves as a preliminary screening before moving on to more technical discussions.
Candidates can expect a significant focus on behavioral questions and discussions about past projects, with interviewers probing for details and clarity on experiences listed on resumes. The STAR method is often employed to evaluate problem-solving and teamwork skills.
Technical interviews emphasize understanding core programming concepts, particularly in C++ and OOP, without relying on timed coding challenges. Candidates are expected to explain their reasoning and problem-solving approaches in detail, often through conversational formats.
Many candidates experience panel interviews where multiple engineers assess their fit and technical knowledge, often through a mix of behavioral and technical questions. The atmosphere tends to be friendly, but the evaluation can feel rigorous and detailed.
The overall interview process is described as efficient, with quick scheduling and a clear structure from initial screening to final interviews. Candidates report timelines ranging from a few days to a month, depending on the stage of the process.
Throughout the interviews, candidates are assessed on their ability to communicate effectively and present their work clearly. This includes discussing past experiences and technical concepts, which is often seen as critical for success in the interviews.