Raytheon Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 59 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Raytheon.
Raytheon
Software Engineer
Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical
It kicked off with a quick 15-minute chat with an internal recruiter who found my resume. We chatted about pay, company vibes, if I had clearance, and what the job was about. Then, I had a 30-minute phone call with the hiring manager. They asked me a couple of behavioral questions, some tech questions about embedded systems, and we talked about my past jobs. After that, they flew me to Tucson, AZ for an on-site interview. They covered all the travel costs, hotel, food, and rides. The on-site included a 1-hour behavioral panel with two directors/managers, and a 1-hour technical chat with a tech lead. No live coding, but we went deep on embedded systems stuff, my previous projects, and how I'd fit in. Now I'm in the team selection part, which is usually a 30-minute phone call. The whole thing was really smooth, organized, and professional. I even got to negotiate my salary and a sign-on bonus. Can't wait to start!
Confirmed questions1 question
- Could you explain polymorphism and object-oriented programming?
Raytheon
Principal Software Engineer
Senior Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel
Interview formats
Behavioral Technical Presentation
It was pretty straightforward. The interview was formally set up. Expecting a typical to challenging interview. They want to know about your past experience and if you know about DoD procedures. The panel will assess different parts of the program requirements.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Raytheon
Software Engineer
Entry Easy Neutral experience Accept offer 1 round
Interview process
Recruiter call Onsite
Interview formats
Technical Behavioral
The interview process was described as exciting and tiered, held in a beautiful location. Parking and reaching the building presented some minor difficulties. After signing in with security, I checked in and was directed to a waiting area. I waited for about 30 minutes, observing other candidates being called before my name was eventually called. At the desk, I was given directions to a specific door number and told to follow a hallway to another door number. The overall process was described as easy-going and casual.
Confirmed questions1 question
- Can you explain what a null pointer signifies?
Raytheon Software Engineer Interview Questions
Quoted word for word from Raytheon interview reports.
“Can you explain why allowing all network users to have root access is not advisable?”
Read reports →“Could you explain what a pointer is and also define a smart pointer?”
Read reports →“Can you tell me about the pros and cons of using Java?”
Read reports →“Can you explain the workings of multithreading and how to address race conditions?”
Read reports →“If I give you some code, can you identify all the problems in it?”
Read report →“Which two programming languages do you like the best, and what are the advantages and disadvantages of each?”
Read report →“How do you go about learning a codebase that you haven't seen before?”
Read report →“How do you go about getting up to speed with a codebase you're not familiar with?”
Read report →“How do you handle a situation where your proposed solution differs from your manager's?”
Read report →Formats, difficulty and experience
Across all 59 Raytheon interview reports.