Two main stages, Phone interview and In-person. The phone interview is where you get the standard "Test Questions". Most of it was pretty basic, and it seems like this is standard for the Missile Systems Segment.
The next stage was in person. Big event, flown out to Tuscon for 2 days. Most of it was trying to convince you to join up, interview was pretty short and seemed like they just wanted to check and make sure you were legit. It feels like if you made it this far, you're probably going to be fine. All questions were about experience at previous company. Just make sure you can explain in the correct jargon like you actually worked on the things you say you did and you should be good.
Understand that here (Missile Systems) you need a clearance. If you don't have one you have to wait until you do before you can start, this can take a few months of time so be aware.
Phone question stuff: Basic OOP stuff, best know your encapsulation, polymorphic, etc.
Know your C++, they asked about what a Friend is, so it seems like they wanted to know exactly how much you've played in the language.
Memory stuff, Stack vs Heap.
In person: Tell me about a difficult project you've done?
Tell me about a project you enjoyed
They may ask you things about different processes you've worked before or how you go about finding solutions to problems in general. Nothing specific.
The following metrics were computed from 3 interview experiences for the RTX Embedded Software Engineer role in Tucson, Arizona.
RTX's interview process for their Embedded Software Engineer roles in Tucson, Arizona is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for RTX's Embedded Software Engineer interview process in Tucson, Arizona.