cswork / libraryOpen practice workspace

Interview experiences · Raytheon

Raytheon Software Engineer interview: resume-depth second round

RejectedTech screen

The first interview was surprisingly laid-back. We spent a lot of time on OOP, including the classic four pillars, and broader software-engineering fundamentals. I explained how I thought about code, and it did not feel like they were trying to catch me out. The second round was a real step up. Several engineers and the hiring manager joined, and they examined the details behind what I had put on…

The first interview was surprisingly laid-back. We spent a lot of time on OOP, including the classic four pillars, and broader software-engineering fundamentals. I explained how I thought about code, and it did not feel like they were trying to catch me out.

The second round was a real step up. Several engineers and the hiring manager joined, and they examined the details behind what I had put on my resume. They expected more than a project headline. I had to explain technical specifics, including C++ concepts. I did not get past that round, although everyone I spoke with was respectful.

The main lesson was that it was not enough to have projects on a resume. I needed to explain their technical underpinnings in depth.

Location: Plano, TX. Overall feedback: neutral. Offer status: no offer.

Comments

Nothing here yet.

Join in on CSWork →