Stop calling, maybe?

Ah, recruiters and their phone calls. You start the search with a quick email blast to anyone that matches a keyword, and then hit the phones. It's efficient, and you are seen to be doing lots of stuff towards filling that role.

Geeks don't like it. Let me count the ways:

  1. It crashes us out of the Zone - if we are deep in concentration, we can lose hours of concentration. I'll talk more about Flow and 'The Zone' in another post.
  2. We need to know who you are, and what the job is about. If we care anything about the role you've offered, follow it up quickly with the details - of the job, and you - by email. Even better - just email me those details first up, and we can check them when we want to.
  3. Most of the time - we're at work, and we are perfectly happy there. We don't want the calls - we're not looking for a new job, or contract. We'll let you know if we are.
  4. There's another reason to prefer an email up-front with some minimal amount of details - it's ignorable. It's also mark-as-spam-able. Either way, we can deal with it quickly and then get rid of it, if we aren't looking. If we are - we can get back to you, maybe in a few hours, maybe overnight.

Well, that's pretty definitive! Also quite a popular opinion :)


What does a developer do?

The developers you place are writing Javascript, Python, Java, C#, PHP, Ruby, and so more. What’s the difference, and how do you find the good ones?

You don't need to become a developer to find great developers - but knowing more about what the really good developers your clients are seeking, helps you to find the candidates - developers, designers, hackers, ops, and everyone else that make the 21st century work online.

These emails won't teach you to be a developer, but you'll get a hint of the day to day work of those you are looking for.

Header image by Alan Levine via Flickr (CC BY 2.0)