This may seem trivial but your interviewer may get feedback from others so always be nice to the receptionist, the person who see’s you to the interview room etc. If you appear rude to others that you interact with – although not part of the formal interview process this can create negative feedback.
The trouble with first Impressions, you only get one. So make sure it is a good one. Good body language, smiling, eye contact, manners and be well presented.
Dress code for IT interviews is always quite difficult. If you are at an agency or studio chances are the people work there will be casual. However it is a risk to assume this unless they specify on the interview instructions. Therefore always look as professional as possible.
No one will hold it against you putting on a suit and a tie, but someone may hold casual wear against you in the recruitment process. Smart dress demonstrates a sign of respect.
Do not fall at hurdles that are easily avoidable. Understand in detail about the company you are meeting – what they offer to clients, their history and their future. Try and understand what technologies, project methodologies etc they use. This will demonstrate a strong interest.
Ideally understand the sector as well. Additionally research those individuals that will be interviewing. This won’t get you the job on its own but can often be a cause for non progression.
All interviews will start with the interviewer asking basic pleasantry questions about yourself and maybe aspects of your CV. These conversational questions are designed to delve deeper into your profile and find out about your personality.
Technical questioning or tests will undoubtedly be part of the recruitment process in IT to test your expertise. You will need to be prepared for this. Obviously this should be relevant to the job you applied for and your experience. Do not try and blagg your way through.Be honest with what you know. If a technical question is beyond you explain this is not something you have come across to date.
Provide examples and references to previous projects. When answering technical questions if there is an opportunity reference previous and relevant work. This brings to life answers and provides a much greater demonstration of your application. Previous experience is always hugely important. PLUS reference achievements and success based on YOUR work not just stating examples.
Gratuitously rambling on is never going to help your cause, irrespective of what job you are going for. The focus needs to be on your knowledge experience and culture fit. You can’t win an interview by trying to talk your way into convincing them you are better than any other techie they have.
There can be instances of interviews going wrong because technology candidates try to explain how the company has used the wrong development process or technology and that they clearly should have done it a different way. Be humble!
A common pitfall that candidates fall for is failing to ask questions to their interviewer. An interview is also an opportunity for you to find out more about the role you are applying for and the company itself, and not asking questions can come across as a lack of interest in the role. The company wants to see that you are an enthusiastic and inquisitive applicant.
Should the opportunity arise to ask a question during the interview, take it. Don’t rely on questions popping into your head during the interview, but rather come with a few pre-prepared questions. Keep your questions brief and engage in the responses provided.
On closing the interview feel free to ask key questions about the recruitment process and your performance i.e. when will you be making a decision? Or even what are the barriers to hiring me? Be bold. Of course, end the interview politely and thank the interviewer.