Ewan's Corner

Over the years I’ve gathered a bit of experience on both sides of a job interview, so here are some of my suggestions for candidates (including recommended reading) since I often find myself sending these out in response to queries about Derivco.

These are biased towards technical developer type interviews since that’s my area of experience, but I reckon most of them are generally applicable – still, see the disclaimer below and as always caveat lector. I think they’re common sense, but apparently not for some candidates…

1. Find out as much as you can about the position you are applying for, especially if this is not your first interview for the position.
2. Be positive, and show enthusiasm for the position (and the company in general). Nothing worse than a negative, unenthusiastic candidate – we love what we do, so we expect you to do the same. Attitude is important.
3. Try and find as much about the company as you can – Google, Google news, friends or people you may know who already work there… shows enthusiasm and passion.
4. Be honest and open, admit when you don’t know something, or can’t do something (especially important in a technical assessment or code walk through). I’ve seen candidates who refuse to admit something has them baffled – they end up um-ing and ah-ing and annoy the interviewer(s) who have other important things they could be doing.
5. Depends on the position, but perhaps bring a portfolio of previous work (the things you are really proud of achieving). Also feel free to mention previous projects which may have failed overall (e.g. for reasons beyond your control) but which you are still proud of (or proud of a component / idea which was your own).
6. Should go without saying, but you’d be surprised – be a little early, and make sure you’re well rested.
7. ASK questions, as well as answer them.
8. Don’t lie! Mad that I feel it necessary to say this, but I’ve seen candidates tell outright lies or make claims they can’t back up. We will check your working background, and we will catch you out in tech assessments – you’re only hurting yourself here.
9. Dress smart, but not overly so (no suit and tie required – unless that’s your most comfortable gear, or you’re applying for CEO :-)
10. Turn off your cellphone / pager / pda! As unbelievable as it may sound, I have witnessed more than 3 interviewees forget this common courtesy – one of them even answered a call!

Essential reading:
The Guerrilla Guide to Interviewing (Joel on Software, v3)
and if it’s a developer position, so is:
Why Can’t Programmers.. Program? (Coding Horror, Jeff Atwood)

Standard disclaimer: I don’t speak on behalf of Derivco, these are my *personal* comments. Although many of these *may* assist you with interviews for positions here, they also may not – they may not even apply – and in some areas may even ensure you *don’t* get the job :-)

One Response to “Job Interview Opinions”