interview advice
Nov. 8th, 2006 05:02 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
dsrtaoThe only sure way to not be caught lying on your resume is.... Class? Very good - don't lie on your resume.
If you list a technology on your resume and you also list a project involving that tech, assume that someone is going to ask you questions about it. Listing a language you don't like is semi-acceptable, if you know it well. Not being able to answer basic data structures questions for a programming job is Right Out. Apparently one can get a master's in CS with an A- GPA and not get an education.
I have decided I quite like the pair approach to interviewing candidates. You get exposure to another interviewer's style, time to think about your questions, and the opportunity to evaluate the candidate's reactions without being focussed on the question. Larger groups I don't like - too much pressure on the candidate, not enough time to ask your questions.
If you list a technology on your resume and you also list a project involving that tech, assume that someone is going to ask you questions about it. Listing a language you don't like is semi-acceptable, if you know it well. Not being able to answer basic data structures questions for a programming job is Right Out. Apparently one can get a master's in CS with an A- GPA and not get an education.
I have decided I quite like the pair approach to interviewing candidates. You get exposure to another interviewer's style, time to think about your questions, and the opportunity to evaluate the candidate's reactions without being focussed on the question. Larger groups I don't like - too much pressure on the candidate, not enough time to ask your questions.
(no subject)
Date: 2006-11-14 05:06 pm (UTC)Which is precisely why we *do* do it for our followup interviews. First interviews are either one-on-one or two-on-one (for the reasons you cite). If they pass that, we hit them with The Design Session -- they are told to lead an open design session with the team. Relatively high-pressure, but that's the point: if you're going to fold under that, you're probably not going to survive here. We have a lot of forceful personalities here, and expect programmers to be able to hold their own in that environment...