Live data from Hacker News

Tips For Tech Recruiters, From an Engineer

danrodriguez.me

31–40 of 41 posts

Re: Tips For Tech Recruiters, From an Engineer

#31
Here's the thing that weeds out recruiters for me: If you get far enough to get me to respond, I'm going to ask a couple specific questions in my response. Answer them.

Just yesterday I responded to a recruiter, explained my situation and asked a couple specific questions. The response was a totally generic email that made it clear he didn't bother to read what I wrote, and just was eager to get me on the phone.

One thing I've learned is they want to get you on the phone ASAP so that they can waste your time, because somehow in their minds, the more time they waste on the phone with you, the more likely your'e going to be interested in them sending you jobs. (If I'd ever had a productive, business like conversation with a recruiter that wasn't full of weasely words and them evading questions, I might feel differently.)

I think this must be a Sales 101 tactic.

Well, I'm in a position to be picky. That makes me the kind of person you probably are really desperate to hire.... so why not take the time to read my reply and respond to it?

I mean, I expressed interest. Now I know I'm going to get follow up mails along the lines of "you expressed interest in blah... lets set up a call" for weeks... he'll never go back and actually read my response, I'm almost certain.

Re: Tips For Tech Recruiters, From an Engineer

#32
post #17

> Most experienced engineers get several solicitations a day As an engineer who's just starting out, I get no solicitations at all. I've heard about people being constantly contacted about work, but that's just not happening to me. If I lost my job, I'd have no idea what to do. How do you get on these people's radar? I'd love to feel more in control of my career instead of like my whole life depends on the good grace…

Make LinkedIn/Careers 2.0 as good or better than your resume. When someone wants my resume I usually just export my Careers 2.0 profile to PDF and send them that.

Re: Tips For Tech Recruiters, From an Engineer

#33
One of my main gripes with external recruiters are the in-person meeting.

One external recruiter contacted me on Linkedin and said they knew of open positions I might be a fit for, but insisted, like most of them do, that I come in and meet them. So I wasted an afternoon meeting them. Then I hear nothing for months. Then I get an e-mail from the same firm. The last guy I met moved on from the company, a new person is now handling me there. They know of some positions I might be a fit for. But since this was a new person handling my account, they wanted me to come in for another meeting before they referred me to any of these clients they theoretically had. Of course I didn't go.

Once when I was on the other side of things, when we were dealing with recruiting firms for a hire, my boss said he wanted to phone screen interviews before bringing them in. One of the recruiting firms was unhappy with this, and was insisting its interviews come in without a phone screen. Luckily I had a good boss, he insisted on the phone screen and they gave in.

Who benefits from no phone screen? As an interviewee, I don't want to a waste an afternoon, maybe a whole day going in to interview for a position which I am unqualified for, or which has some requirements (50% travel, whatever) that I do not want to go along with. As an interviewer, why waste my time, and my co-workers time, and their time bringing in someone who can't answer the most basic technical questions I can ask? I wonder how many people who gave those recruiters their resumes knew the recruiter was pushing against phone screens and for in-person interviews only.

Re: Tips For Tech Recruiters, From an Engineer

#34
post #25

Don't work with recruiters, period. Why? From the hiring side of the table, here's why. 1) they misrepresent you and lie. "Kevin has 10+ years of experience with Ruby on Rails". I go "huh, Kevin's a lying shit. Bin." 2) 40% of your goddamned salary finders fee?! Fuck that shit I'll find someone else. 3) why would I be interested in employing you if you're not interested in us? The fact that you've gone to a recruiter…

1) You worked with the wrong recruiters.

2) Same as 1. Standard is 25-30%.

3) Some of the best hires at firms I've worked at came from recruiters. From the candidates' point of view, it's often a lot more efficient to find matching positions and land offers through recruiters.

4) Same as 3. Loyal employees use recruiters too.

Re: Tips For Tech Recruiters, From an Engineer

#35
post #13

I've talked to experienced recruiters and hiring managers about this. The interesting thing is that the content of the email actually doesn't matter much at all. Personalization, mentioning mutual contacts, etc helps but not a lot. The single biggest determinant of a successful recruit is (drumroll, please) whether the candidate is currently looking for a job. I just went back to read the recruiting email that kicked…

Note that they told you a heck of a lot in that email by mentioning Facebook. You already know about them, engineering culture, programming language, open source contributions, lots of online videos etc.

Many of the non-personalized emails tell you virtually nothing useful about the company, certainly almost never the name.

Re: Tips For Tech Recruiters, From an Engineer

#36
post #25

Don't work with recruiters, period. Why? From the hiring side of the table, here's why. 1) they misrepresent you and lie. "Kevin has 10+ years of experience with Ruby on Rails". I go "huh, Kevin's a lying shit. Bin." 2) 40% of your goddamned salary finders fee?! Fuck that shit I'll find someone else. 3) why would I be interested in employing you if you're not interested in us? The fact that you've gone to a recruiter…

True,

But how much of your time or HR's time goes to scanning through resumes. If you only spend time reading 30 resumes. And it possible a recruiter database has 100's, possibly with good candidates, then you must missed a good set of candidates.

And then there is a timing issue. How long is your job post out there? 2 weeks, 2 months? So in the window of time that your post is out there, candidates have to find your site and your job post.

Recruiters, that is what they do. Everyday, they are scanning for candidates, filling positions.

I don't like it but at least it makes sense.

Re: Tips For Tech Recruiters, From an Engineer

#37
I have to say, I struggle to see the benefit technical recruiters bring. They rarely know enough about the tech to do any sort of reasonable matching. They don't give me as much information that I could find about the job as if I went to the website. Obviously exclude the company, but if you aren't going to give me a vague impression of salary or reqs, why would I roll the dice?

Re: Tips For Tech Recruiters, From an Engineer

#38
post #2

If I hear anything about you looking for “ninjas”, “pirates”, “hackers”, “samurais”, or anything of the like, I’m just going to assume you’re looking for a new saturday morning cartoon character and not an engineer. Grow up. This needs to be on a billboard.

Like the sibling poster, I think "hacker" perhaps shouldn't be on the list.

I'm not a pirate, a samurai, or a ninja. But I am a hacker.

Re: Tips For Tech Recruiters, From an Engineer

#40
post #25

Don't work with recruiters, period. Why? From the hiring side of the table, here's why. 1) they misrepresent you and lie. "Kevin has 10+ years of experience with Ruby on Rails". I go "huh, Kevin's a lying shit. Bin." 2) 40% of your goddamned salary finders fee?! Fuck that shit I'll find someone else. 3) why would I be interested in employing you if you're not interested in us? The fact that you've gone to a recruiter…

I once contacted a company about a job offer they had published on a university's alumni website. First thing they did was redirect me to their favorite recruitment agency so they would screen me before they considered my application.
Post reply on HN