Ok, today I gave a technical interview for a software developer position here at Bebo.  Afterwards, I really felt the need to write a do’s and dont’s for technical phone interviews.

First off, if you write it on your resume, know it.  All that, “I did “x” 10 years ago but I don’t remember it today” is crap.  You should at least remember the basics of it, if not, make sure you do before the interview.  Related to that is actually saying, “I don’t remember/know”, if you are asked something, and you really don’t know, just say it, rather then inventing a story, or telling me a story about something else you do know. 

Second, if what you are saying is not answering the question, don’t.  What I mean is, as an interviewer, I have some set amount of time, and I need to spend it trying to evaluate what you know, not about whatever else you might want to tell me.  Sure, if you have hours, talk about whatever you want.  But keep in mind that the interviewer has a set agenda and not much time.  Also, Brevity is a virtue.

That last point also relates to the resume.  If you were in fact called back, it was because of something on your resume.  There is no need to upsell me on something else, simply prove to me that the stuff on your resume is legit (since it was the resume that got the call in the first place).  Once I believe that, we can move on to other things.

Also, don’t feel that you have to put every tech buzzword on your resume.  That makes it difficult for the interviewer focus on those things you do know well.

Lastly, if you are going for an interview where they might ask you to actually write Java code, like at Google or Microsoft, brush up on utility and collections classes.  Make sure you know the practical stuff well.  You’ve surely used it, but make sure it’s on the tip of your tongue just before the coding interview.