Along with (as was the main point of the original blog post) probably quite a few false negatives, Like the author of that post, for example.
Meanwhile, you can achieve the same filtering benefit by far less obnoxious and more accurate means (a cursory glance at their repo, fore example).
Everyone likes to think they are the good candidate and not the bad one that slipped through…
We have flat hierarchy. Just volunteer to interview because your voice is on the same level as others.
When your organization can recognize a poor investment but cannot act on it, you have an organizational problem. Why would someone get to hire more "bad" (for whatever that means) if you can recognize it? Even if you're doing all the hiring yourself, it's unlikely you'll have a 100% record over time.
Right. But we can't talk about that, of course.
Instead the corrective strategy seems to be: "Let's torture some more candidates. It's cheap and it's easy, after all."
For another, even if "an organisational problem" or inconvenient labour laws don't get in your way, firing employees can have a serious effect on the morale of those left behind. And for good reason! Usually companies that regularly fire people for poor performance has a different sort of culture than companies that don't. In my experience, that's the worse organisational problem.
The right solution is just to be more careful about who you hire in the first place.
So if someone lied their way through interviews, in the first couple of months you should be able to detect that and terminate their trial period.
Managers hates firing people, it is really uncomfortable. So instead of firing this person to look for a new, they keep the person and say they need even more headcount and hope the next one is better.
It doesn't have to be a public repo of course. They can just send zip file.
You need an equal comparison across all candidates.
"We'd like to see a code sample -- something we can build and compile, that you feel is representative of your skill level."
Sounds pretty straightforward and egalitarian to me.
Long before open source was a thing, and repos were even thought of -- I always had a few 1,000+ line personal projects I could dig up and show people.
1,000 lines isn't that large, btw - but yeah, maybe 500 would be a better number.
With Leetcode, everyone starts on equal footing (there's no bias towards people who code in their free time)
Yeah, it's extremely irritating as a candidate but it's something
>usually being close to runnable with a few small bugs was a good submission and runnable with no bugs was a great submission
This is exactly what we do: check the solution, and if it's close we continue the hiring process. There is a huge difference between an almost working solution and what you get 70% of the time: code that will never, ever, ever work, even if it could run.
A lot of hiring managers have no concept of experiment design.
You can’t invent a measure (or copy it from a blogs about how other companies hire), look at who it rejects, and conclude they are bad. You don’t know if they were good or bad. You never worked with any of them. You only know that you applied your measure.
The only candidates you have any information about are the ones you hired, yet you are insulting the others on the internet today
What's interesting is that the people doing all this "weeding out" seem so sure that they're bravely defending the fort against an onslaught of incompetent hordes... and yet they're missing this extremely basic point about the nature of the process they've chosen to use.
How so?
> turnover rate on your team like?
2 years since I joined, hired one dev recently, no one left so far.