Northrop Grumman Software Engineer I Interview Questions & Reviews

Interview Details – I was contacted for an initial interview, which was the basic interview which was with a HR. Basically just went over my resume, plans, what I was looking for etc. Got an e-mail for a second interview with an engineer. Had a problem scheduling the interview, but finally found one that works. Waited an entire hour after the given interview time but no call.

Interview Details – My initial contact with the company was through our school career fair. I did not receive an on-campus interview; however, after about a month I was invited to an on-site interview. Several other candidates attended as well. We were introduced to the company by several panels of employees (young and old). We were then put through two interviews. Each interview consisted of 2-3 interviewers in a small office. The interviews were very down-to-earth. There were standard H.R. type questions and several questions regarding project and job experience. Several of the candidates were asked very technical oriented questions. I myself was not.

Negotiation Details – I did not attempt to negotiate. The initial offer was more than satisfactory.

Interview Details – Got an email saying they had my resume in their database and wanted to schedule an interview. I interviewed with two team leads, which consisted completely of behavioral questions and went very well. Got a call back for a second interview with one of those team leads, plus two others, plus the department head. It was mostly a rehash of the first interview with the only technical question being about Unit Testing. The team lead that interviewed me both times said I did great and they would do my review, which was about 3 weeks ago. Haven't heard from them since.

Interview Details – I applied for the position through my university's job board. Was contacted for a 45-minute phone interview. It was fairly standard, essentially just a resume walk-through and a discussion of skills and experience with languages list on the resume in addition to any projects I have used the languages in.

Interview Details – Basic Phone Interview that gives you a chance to go over your resume. If that goes well you get flown out to the office for an in-person interview. If you are being considered for more than one program/project then expect a longer (possibly all day interview). If it's just one program/project then expect maybe an hour to two hours. You're going to be interviewed by your manager(s) and prospective coworkers. It's ok if you're nervous just tell them about yourself and elaborate on what you told them during the phone interview. The questions they ask you are usually relevant to the program/project that you will be added to. For example you focused on Communications in school then expect a basic communication question or be able to talk about a project related to that experience. They might have videos for you to watch and they'll tell you more about what you could be doing.

The questions aren't too difficult just know your basics.If the job description has to do with object oriented programming, for example, then it would be prudent to know and be able to explain what object oriented programming is in a nutshell. What's polymorphism, abstraction, etc.? Don't worry if you don't remember some rigid definition you memorized in school just explain it the way you know it. If you think you can show it to them better than telling them then by all means let them know that and show them. Just prove that you are competent, can do the job, and are personable...they called you for a reason and flew you out for a better one.

Negotiation Details – You tell them what you want and they tell you what they got. Sometimes they give you more, sometimes they give you what you ask for, and sometimes they try to get close but are a little under. Be honest and just tell them the range you're looking for. It depends on the program you get hired for. This is of course the experience of a "college hire". I got the offer the same day. If (Nice location && pay on par or better && interesting project) {Satisfied = True;}

Interview Details – Applied through the company website and received an email from a recruiter just a few days later. Had one in-person interview that had hardly any technical questions; mostly just asking about projects I had worked on and how I felt about them. Honestly, no real curveball questions to speak of.

Interview Details – I applied for a Software Engineer I position with Northrop Grumman in Colorado Springs. About a week later I received a polite call from a Northrop Grumman recruiter to set up an interview. We agreed on a time some days later, and at the specified time the hiring manager called me. The hiring manager asked me about myself, and immediately told me it was "strange" that I had graduated in March. I had to explain to him how a school with a quarter system works. After that he asked me a series of very specific technical questions like "what is systems engineering?" (this topic was not on the job description) or "how many lines of code have you programmed?" He seemed to be looking for a candidate with certain pre-existing skills, not someone who was willing to learn. He was critical of me during the interview and I did not find the experience pleasant.

Interview Details – I was first contacted by a recruiter. Then she briefly explained the job and its compensation then set up an interview for me.

The interviewers first described the job; what is it about? what is a daily work cycle? Then they asked about my background; what had I done so far? what did I do in my previous/current jobs/research position? No technical questions were asked.

Followed up by the recruiter, she said I did a good job in the interview and they would extend me an offer. No negotiation was done. The offer was given a few days after the interview.

Negotiation Details – I did not negotiate with the hiring manager regarding salary. I believe the negotiate phrase started when you are contact by the recruiter.

Interview Details – Lengthy process and difficult technical questions. It seems to me that they are trying to eliminate candidate who don't have the insider's help. In all, "It was not about what you know, but who you know."