Tech Interview Handbook
I realize everybody's going to jump in and rant about algorithms in interviews, but I wish you'd all add something constructive as well.I just had to conduct a round of interviews in a non-SF large US city, and it was a hellish crapshoot.  Resumes are meaningless, and often re-written by recruiters to match the job anyway.  Everyone has the same canned answers to the stupid behavioral questions.  And as for the code, we included what we thought was a trivial nested for-loop problem and virtually nobody could even get started on it.Is this kind of code problem too complicated in your opinion?   For all I join in when complaining about irrelevant algorithmic questions, I have to admit that they at least test something, even if it's just willingness to study for the interview.Instead of reading everybody's complaints about interviewing, I'd love to hear how you think it should be done.  Because I have to admit I'm pretty much lost right now.