Tech Interview Handbook
I realize everybody&#x27;s going to jump in and rant about algorithms in interviews, but I wish you&#x27;d all add something constructive as well.<p>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.<p>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 <i>something</i>, even if it&#x27;s just willingness to study for the interview.<p>Instead of reading everybody&#x27;s complaints about interviewing, I&#x27;d love to hear how you think it should be done.  Because I have to admit I&#x27;m pretty much lost right now.