Respect

I’ve written before about how one of my goals is to create a software development company that respects its employees. A throwaway remark about why people put "references available upon request" in their CVs made me realise that as well as respecting its employees, a good company also respects its prospective ones.

When you interview someone, turn up on time. Introduce yourself, and describe what you do in the company and what relationship you will have with the interviewee if she accepts an offer. Even if it's obvious the candidate isn't a good fit, conduct a proper interview and be polite – make your case after she's left. If you find that you have a hard time justifying your verdicts, try politely excusing yourself in the first few seconds of the interview ("I just have to fill out the top of my notes page") and write down your first impression. Afterwards, if you haven't changed your mind, justify why not.

When you've decided to make an offer, bear in mind that it's human nature to talk. Don't call in references without making an offer first, and don't call old friends that may have worked with the candidate before unless you have permission or are absolutely certain that your contact will be discreet. Finally, when it comes to the offer, don't forget that you chose this person because you believe she will make you lots of money – starting off by trimming pennies off their package is not respectful.

By the way, I'm not sure I agree with Seth that a CV should be just references, but I think that if you can't name a champion you trust enough to recommend you without broadcasting your job hunt, it may have been a poor life choice to have stayed in that position.

Comments

[Tim Haughton]

I agree, respect is absolutely paramount here.

I recently contracted at a company that produced a really whopping piece of eye candy. The CEO, concerned that the product might attract poachers, insisted that the developer's names be taken off the product web site.

Result: Seriously miffed developers.

What he should have done: Undertaken to write, himeself, a small article on each of the developers, bigging them all up and saying "these are my guys, and they're *this* good."

Just a little respect goes a long way.

[Bruce Chapman]

With the whole discussion of 'references available on request' - the number 1 reason for not putting any references on my CV/Resume is respecting the privacy of those that may produce a reference for me.

Unscrupulous employment agents love nothing more than a CV with a list of references including contact numbers on the end. The first thing they do is go through and cold-call those people and try and get them on as accounts. It's akin to putting your referees email addresses on your personal blog page to be scooped up by spam-bots.

Ok, you might say, don't send your CV to unscrupulous employment agents. Firstly, there's no external way of telling which are good and which are bad. Secondly, the agent often is the gatekeeper to the job you want. You'll have to go through them.

So : references upon request should actually be appended with ', and on condition all contact is confidential and related to the job application only'.

-Bruce