The Lion, The Witch, and the audacity of recruiters

The Lion, The Witch, and the audacity of recruiters(hauleth.dev)

10 points by birdculture 3 hours ago | 9 comments

I figured out fairly early in my career that if a company/team really wants you, the recruiter is going to roll out the red carpet, irrespective of seniority. It's happened multiple times for me, and has led to the few successful offers I've had. But if they're ambivalent, or you're just there to fill in the statistics, then problems will pop up: lack of proper communication, no clear timelines, canned responses, ghosting, the list goes on.

So I look for markers: if I see a quick turnaround time for my emails, I know that I'm in the right interview loop. Else I spend as much time as the other party spends on me, ie not much.

appplication 1 hour ago | |

This approach works extraordinarily well for essentially all interpersonal communications. Friendships, relationship prospects, etc.

joshstrange 1 hour ago |

Every time I've gone through the hiring process I contemplate starting my own recruitment agency because to a man (or women) every recruiter I've worked with has been shit. The internal ones are decent but 3rd-party recruiters know almost nothing. It's a revolving door of staff with zero expertise of recruiting and zero understanding of the roles they are hiring for. They are terrible at communicating, will ghost you for scheduled calls, and you have to prod them constantly.

In once case I knew someone at the company I was apply to, the recruiter I was forced to interact with did nothing and kept stalling. Finally I had my friend end-run the process and hand my resume to someone and a day later I had an interview and got the job.

That said, while I know it sucks being on the receiving end, giving feedback is a minefield and not an easy task. I understand the frustration, I've felt it myself many times but being on the other side of the table helped clarify the challenges.

andy99 1 hour ago | |

> every recruiter I've worked with has been shit

That’s a feature, not a bug. It’s an obviously solvable problem but companies don’t solve it because incentives push them to this model.

There are of course exceptions where recruitment is well run, but for the most part they want (to the extent that emergent behavior from an institution can want something) useless people doing it.

(As an analogy, it’s sort of the same reason why all corporate training is shit, all HR is dumb, etc. Part of the explanation, but not all of it is the need to give the appearance of doing something for compliance purposes. You need something and to be seen to be doing it, but the quality is irrelevant so you get the worst possible.)

kjellsbells 1 hour ago |

I wanted to sympathize with OP, but I sense that the blog post was written while they were still fuming, and some of their behavior during the process (esp the first job) gave me pause. Maybe its just the timing that makes it feel aggressive.

Imagine you are a contractor on a gig. You don't wait until things break before you ask for access. You ask, before the job starts, what all the doors are and who has the the keys. So: "hey, Recruiter, in order to make this task a success next week and make you and me both look good I will need some stuff ready on day 1: what's your code repo system ? MFA?internal comms channel? bug system? internal knowledge base? and most importantly, if it's not you who can administer access to these things, who is the person I talk to, and can you arrange an intro on day 1?"

To not show this level of initiative, and sit around while your friend navigates the corporate machine for you, is the behavior of a new intern, not a senior developer. OP also doesnt say that they arranged a live end of Day 1 checkin with their task manager, which is another miss, since it allows for the latter to mop up any lingering issues ("oh yeah I forgot you need access to X, let me sort that out") and for the former to remind them that this is an odd task ("it was interesting that you asked an Elixir dev to work on a browser extension")

As far as being asked to work in TypeScript not Elixir, thats certainly odd, but could have been deliberate and not necessarily foolish. Maybe they wanted to see how intellectually adaptable OP was. Maybe they wanted to see if you would speak up and handle potential conflict. Or maybe they had a mixup between two candidates. We'll never know because OP sent a wall of text which surely would not have helped defuse the situation.

appplication 1 hour ago | |

I think I agree with the spirit of your post mostly, but this bit:

> Imagine you are a contractor on a gig. You don't wait until things break before you ask for access. You ask, before the job starts, what all the doors are and who has the the keys. So: "hey, Recruiter, in order to make this task a success next week and make you and me both look good I will need some stuff ready on day 1: what's your code repo system ? MFA?internal comms channel? bug system? internal knowledge base? and most importantly, if it's not you who can administer access to these things, who is the person I talk to, and can you arrange an intro on day 1?"

I could not imagine asking a recruiter this, if it’s anything like the current recruiters we use, they know none of this, are likely incapable of figuring out how to learn this, and it’ll be blind leading the blind to expect this.

Honestly, it’s fine to expect a fair bit of inefficiency in your first few weeks as you onboard to systems, learn who people are, etc.

andy99 52 minutes ago | |

I think it’s just as well he was opinionated and realized it wasn’t going to work. Ironically, if this was actually the start of the job, I think bailing might have made more sense. Given that it was just a one week work trial, I feel like there’s little downside in just toughing out the remaining couple days and then deciding. Personally, if I found out the Typescript thing was a secret test of adaptability (which seems extremely unlikely) I would move on, I wouldn’t want a place that plays those kind of games.

hauleth 54 minutes ago | |

OP here

> Maybe they wanted to see if you would speak up and handle potential conflict. Or maybe they had a mixup between two candidates.

I did speak up during the call if that is really what they want me to do as I have literally 0 experience with that. It was literally my first action after I heard that. I pointed it out to them, that it is not what I was expecting from this position.

They didn't care. It was how they roll.

arnab777 2 hours ago |

AUDACITY !!!!!!!