I applied through college or university. The process took 1 week. I interviewed at Northrop Grumman (McClellan, CA)
Interview
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 questions [1]
Question 1
Nothing unexpected, just be prepared to effectively elaborate on anything pertinent you have done.
I applied through an employee referral. The process took 2 weeks. I interviewed at Northrop Grumman in Mar 2008
Interview
The interview was extremely straightforward. They asked me a few questions about my work experience and what my unique talents were. The questions were all very broad and high-level, like about what design patterns I was familiar with. Overall the interview was not challenging, and I got the job mainly because I knew people there.
I applied online. The process took 1 day. I interviewed at Northrop Grumman (El Segundo, CA) in Jul 2012
Interview
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.
Interview questions [1]
Question 1
I didn't think any of the questions were difficult, unexpected, or off-the-wall. But here's an example: You've been given an assignment, a piece of code to write, and you're reaching your deadline and realize "Hey! There's know way I'll be able to finish this in time!" What do you do?