Skip to main content

Why do so many technical recruiters suck?


It’s Tuesday, I get a call from an unknown number.  There is a little hesitation, but I finally pick it up.  My number is listed on my business card and I feel like I should get these calls unless I am in a meeting.

- Hi, is this Mike?
- Yes, speaking….
- Hi Mike!  How are you today?
- Fine…
- I am calling from XYZ Co, and we deal with recruiting and staff augmentation.  I was wondering if you are looking for software developers.

We are in San Francisco and it’s late 2011.  Every tech company is looking for developers.  If they were not looking… just wait till one of their devs gets recruited away. Now guess what?  You are looking!

Yes, I am on the market for some developers and this guy bought himself a few minutes…

- Have you looked at the website?
- Honestly I have not had a chance to yet, but I have a couple of Ruby candidates that are really good.

Hmm…. so you don’t know what we are looking for. You didn’t care to open up our website and look at the career page, and I have a feeling that it doesn’t even matter what we want.  You have a couple of people you are trying to pitch to every company you can.

- I can’t really source candidates from agencies that are not on the vendor list.  You have to go to HR first.
- Okay…  in that case why don’t we have coffee or lunch next week?

I am thinking – does this guy not want to hear me? I am detecting a pattern: not only he doesn’t want to listen, he actually doesn’t care to consume any information at all.

I know that type! He probably refers to himself as a “people person”.  On Friday in the Marina when drinking with his buddies he probably talks about people he barely knows using their first name only. I bet he claims to have known people from LinkedIn for a long time and reiterates the values of connections.

This is why on a very basic level we can’t work together: I am at my core an engineer and a scientist.  He is at his core a connector.  I want facts, due diligence and real value.  He thinks that as long as he is nice and interesting we can do business.  One of us is going to have to adjust and since he will, eventually, want $15,000 - $20,000 for his services - it ain’t going to be me.

I do value having an agent out there who can source and screen candidates, but somehow this industry has fallen to some amazing lows.  People who don’t know what they are looking for, what they are looking at, and why they are looking, believe that pounding the pavement and setting up a boiler room is the path to make some money.

So what do good tech recruiters do? They get into the details! They figured out that they are dealing with some detailed folks.  We (other software engineers) want you to do what we could do if we had more time.  As it stands right now a lot of these “people persons” can’t compete with the most connected person of all – Craig from Craigslist.

-mb

PS: by the way I am hiring web and iOS devs, Tech PMs and QA. Apply here: http://jobvite.com/m?3m2Xbfwg 

2 comments

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…