The Try-it-on Approach

When lunch is impractical (as with remote candidates), you have to find another way to backstop your research findings and figure out if this developer is any damn good. You can do a lot of this over the phone, mind you, but it’s never going to be the same…

Why are you hiring?

You need to know why this developer decided that weed-infested, brown grass of his new employer is greener than yours. Image by Robert S. Donovan, used under Creative Commons This is the first question you need to ask, because it informs most everything else. Essentially, the environment you're hiring into…

Your hiring mindset

The reasons for why you're hiring have a great deal of impact on how you go about the hiring process. If you're hiring because of another developer leaving, you're going to be much more time-crunched than, say, a situation where you need more developer bandwidth for upcoming projects or simply…

Developer Stereotypes: The Neckbeard

The next in a series of posts walking through various developer stereotypes. Read the first entry to get a better idea of what this is all about. Know Your Neckbeard If you've worked in or with a traditional IT department, you'll know this type right away. They're the by-the-book, dogmatic…

Developer Stereotypes: The Brogrammer

I'm not going to do a book on hiring developers after all, at least not right now. The good news? Instead, all the things I had written for the book, are going to be free, here instead. Or on my mailing list. Because really, I want to help you get…

Explorations in the developer hiring market

I've been exploring the hiring space for a while now, looking for a pain to solve. The Hiring Handbook is aimed at hiring managers like myself, addressing the pain of sourcing and self-recruiting developer candidates. The issue? It's time-consuming to do right, which is why recruiters exist in the first…