Through my phone interview I had a discussion about my experience and was given the impression I would be a good fit. At the face-to-face interview, which was supposed to be the "technical" interview, I was asked some unclear questions that were irrelevant to my experience. It felt like the interviewer had looked up terms from a certification prep book and came up with a vague way to ask questions to get me to define them.
I was able to trudge through that part, and finally he got over himself and finally asked questions relevant to the work I was interviewing for. I went in excited about the opportunity and left feeling disenchanted about working there.
How are some ways to use inheritance in Java? The follow up question: What are the differences between an interface and abstract class?
He asked about layers of past projects that I had stated I did not directly work on, that were also not relevant to the position I was interviewing for, and that he had no first-hand familiarity with himself.
The following metrics were computed from 8 interview experiences for the Lockheed Martin Software Developer role.
Lockheed Martin's interview process for their Software Developer roles is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Lockheed Martin's Software Developer interview process.