Real, anonymous reports from people who interviewed for Software Engineer at Collins Aerospace, newest first and distilled into what to expect across the loop.
My process leaned much more technical than I expected. I started with a quick screening format and then moved into a virtual interview that was shorter than it sounded like it would be, but still packed enough technical checks to feel real. Instead of mostly talking through my résumé, I was pushed into fundamentals—coding and core engineering concepts—where the questions were often tied to things I’d worked with before.
My Collins Aerospace interview felt pretty human and low-pressure from the start. After an initial recruiter touchpoint, I sat down for a call and then moved into a zoom-style discussion where the focus was almost entirely behavioral. I talked through my background, what I’d been working on, and the way I approach projects, including the “why Collins” and “hardest engineering challenge” style questions. The interviewers gave me room to ask questions at the end, which made it feel less like an interrogation and more like a real conversation.
The interview process typically begins with a brief HR screening, followed by a mix of technical and behavioral interviews that may include multiple rounds with different team members. Candidates noted that the structure felt organized and efficient, with a clear progression from initial screenings to more in-depth discussions.
Technical interviews often emphasize core engineering concepts, particularly in programming, OOP, and system-level thinking, with candidates expected to demonstrate their problem-solving approach. While some candidates faced intense technical questioning, others experienced a more conversational style that prioritized fit over deep technical knowledge.
Behavioral interviews are a significant component of the process, focusing on candidates' past experiences, teamwork, and communication skills. Many candidates reported that these rounds felt more like conversations aimed at assessing cultural fit rather than rigorous evaluations of technical prowess.
Candidates expressed mixed feelings about the overall experience, with some appreciating the conversational tone while others noted frustrations with scheduling and communication delays. A lack of transparency regarding next steps and feedback was a common concern, impacting the overall impression of the process.
Despite many candidates feeling they performed well during interviews, several reported not receiving offers, often without clear feedback on their performance. This lack of constructive feedback left candidates feeling uncertain about their standing and the reasons for the outcome.
Candidates reflected on the importance of solid foundational knowledge in engineering principles and programming, with some wishing they had prepared more thoroughly in specific areas like aeronautics or advanced coding concepts. A clear understanding of the role's technical requirements was highlighted as crucial for success.