Real, anonymous reports from people who interviewed for Software Engineer at Raytheon Technologies Corporate Headquarters, newest first and distilled into what to expect across the loop.
After a recruiter conversation, I ended up in two back-to-back rounds. The first one felt pretty easygoing and mostly revolved around how I think about code, including core OOP ideas and software engineering fundamentals. I remember walking through my reasoning on what I’d built and how those concepts showed up in practice.
My process started through a career fair, and then it moved quickly into a Teams Q&A to cover my background, technical expertise, experience, and behavioral responses. Recruiter follow-up scheduled the next Teams interview, and I ended up talking with a mix of hiring manager(s) and senior technical leadership. The interview atmosphere felt casual and professional, which made it easier to focus on giving complete answers.
The interview process typically begins with a recruiter conversation, followed by multiple rounds that include resume walkthroughs and behavioral questions, often leading to a panel interview. The overall flow is organized and predictable, with clear expectations set at each stage.
Interviews emphasize discussing past projects and technical experience rather than traditional coding tests or algorithm challenges. Candidates are expected to explain their work in detail, demonstrating a solid understanding of the technologies and concepts they have listed on their resumes.
Behavioral questions are prevalent throughout the interview process, often using the STAR technique to gauge candidates' past experiences and how they handle teamwork and problem-solving. The focus is on communication and cultural fit rather than purely technical prowess.
Candidates report a generally friendly and relaxed atmosphere during interviews, which helps ease stress and encourages open communication. Interviewers are described as approachable, making the experience feel more like a conversation than a high-pressure test.
While technical questions are present, they tend to focus on practical applications and reasoning rather than abstract problem-solving. Candidates are encouraged to discuss their thought processes and the specifics of their technical experiences rather than memorized answers.
Many candidates do not receive offers, often reflecting that a clearer articulation of their technical experiences and project details could have improved their chances. The interviews are seen as opportunities for growth, with candidates wishing they had prepared more thoroughly for the depth of questions asked.