3 ms·
The nice thing about this method of hiring is that I probably wouldn't want to work for a company that trusts someone with such silly biases to pick candidates
by jeroenhd 5y ago
The nice thing about this method of hiring is that I probably wouldn't want to work for a company that trusts someone with such silly biases to pick candidates anyway. The code I write and push to my self-hosted Gitlab is none of your concern.
If you're going by some trivial standard (github repos, leetcode ranks, whatever the case may be) you're going to be talking to a lot of people who made it a priority to get hired, not to write good code or even work well in a business environment. I'd argue that high-effort resumé stuffing is even worse than the lazy kind, because you might be tempted to give the candidate the benefit of the doubt or skip over some of the validation questions that a resumé-based hiring process might demand. You might even end up hiring bad coders who are better at making stuff up and repeating textbook excerpts than writing or maintaining any real code.
The author states that during interviews he talks through the code the interviewee has written and the decisions they have made, but such a process could easily be reversed as well. Grab some company code with known architectural flaws or technical debt and walk through that. Ask what they would've done differently and why. Ask what they would do to improve it. This probably works best with some archived code from stale branches or sunset products so you don't give off the impression that you're doing this for your gain and you won't risk leaking any important company secrets anyway. Better yet, grab some of your company's open source projects (Your company has a public Github as well, right?)
- inetknght 5y ago> The code I write and push to my self-hosted Gitlab is none of your concern. From an intellectual-property standpoint: it actually might be. But I do think intellectual property laws need to change.
- deleted 5y ago[deleted]
- commandlinefan 5y ago> I probably wouldn't want to work for a company that trusts someone with such silly biases to pick candidates anyway The good news is, it's probably not true anyway. Whenever you see these posts, they're almost always written by somebody with a weak resume who spends all of their free time maintaining open source, hoping to convince somebody else to read their github profile.
- PenguinCoder 5y ago>The code I write and push to my self-hosted Gitlab is none of your concern. Agree and this is a reason I selfhost my own git server and repositories. I still want to use git, but what I personally write is none of a third parties business. I have a bunch of scripts and a few programs in various language's, some side project websites and the like. But none of that is something a potential employer needs to see or start dissecting.