F*** You, I Quit — Hiring Is Broken
Sahat Yalkabov
3.3K263

I’m a hiring manager (off and on) and on the other side of it, hiring is HARD. A year ago I was hiring a single angularJS developer and found it very, very difficult. I only asked angular / javascript questions and was lenient on responses — if they were in the ballpark, hey they can google it or hop on Stack Overflow.

Some of the folks we saw, though, were terrible. I ask some basic JS coding questions (along the lines of FizzBuzz, though usually they were custom made ones or reverse a string or something) and I’d estimate around 75% (three in four, yes) could not write a line of code on a whiteboard. This was our VP’s idea — make sure they can write ANY code, because that’s important to know. But they couldn’t. It would devolve to things like “okay how do you make a function in Javascript? Okay just use pseudo-code. What do you mean you still don’t know how?”

This was for a Senior position.

This leads to burnout as a hiring manager. I got sooo many resumes day in day out that all said the same freaking thing. X years of Javascript. Y years of Angular. I have a github page and contribute to open source and I worked at Microsoft/Google/whereever blah blah blah. The resumes mean nothing, unfortunately, because most people, especially those working with recruiters, put down all the keywords we’re looking for even if they’re not strictly true. For example, people putting they had 3 years of Angular experience because the company they worked for used Angular even though that was a different project and they never wrote a line of Angular code.

For what it’s worth, I agree with you and try to make sure that interviews are relevant. Front End devs (which I consider myself) should not be doing complex algorithm tests, in my opinion. The best interview I had was recently, when I was the interviewee, and the angular test was “build an angular page from this skeleton that would manage a contact list”, essentially the ToDo list demo. It was easy, so they said “okay now refactor it into Services and Directives” [Angular 1.4, fwiw]. An hour later, got a call about the job.

The half day interviews are sometimes unavoidable. Lunch? I mean, if you left at 4:30 and it was 3 and a half hours, that means you got there at 1:00, which most people would consider solidly “after lunch”. But I’ve been on both sides of those too. I feel TERRIBLE when I say no to someone who came in for a half or WHOLE day interview, but it happens. Bad vibes, culture mismatch, and so on. It’s tough to cut those short because not everyone is in all phases of the half-day interview, and often it’s not a single dealbreaker thing that gets a “no” but rather a lukewarm response from everyone.

I do agree with folks saying it sounds like you have a bit of a chip on your shoulder. What is your attitude like at the interviews?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.