- If you don’t know it, don’t put it on your resume.
This is perhaps the most simple task. If you don’t embellish the technical portion of you resume you’re likely to find yourself interviewing for a position that matches your technical skills. This is critical because if you list it on your resume, and it’s a skill that they are looking for, you’re probably going to have to answer some questions about it.
This is just too simple. Don’t push it so far as arrogance, but definitely show some confidence in yourself and in your past work.
- Don’t be afraid to say you don’t know.
Nothing makes me want to end an interview faster than someone blowing smoke. If you don’t know, say so, we can move on to things you do. Also be prepared to answer, “Well since you don’t know, how would you go about learning to do that.”
- Be prepared to write some code.
Although the recruiters often prepare the candidates of the fact that they are going to have to write some code. The technical interviews are very fluid and generally not written in stone. They can be adjusted to allow you to demonstrate your skill, but at the minimum you should be able to write some SQL, some data access and some basic programming such as methods, constructors, etc. (Ask questions if you don’t understand what they are asking for…)
- Don’t waste their or your time.
If you don’t think that your skills are a technical fit to the requirement, don’t bother interviewing. All your doing is wasting their time and yours.