3 ms·
Great. Now everyone will juice his resume with something like this and we'll all end up in the same relative positions we were before, except 1) actual resume i
by quotemstr 8y ago
Great. Now everyone will juice his resume with something like this and we'll all end up in the same relative positions we were before, except 1) actual resume information density will be lower, as we'll have decreased the SNR through keyword juicing, and 2) anyone not paying attention to these tools (and focusing on work instead) will be unfairly penalized in early-stage hiring filter.
This is the best timeline.
- ianai 8y agoYou’re assuming it works well. But less tongue in cheek, this is pretty close to the current market, as it is. Things like this might help close some of the arbitrary gaps. I agree with your sentiment regarding the timeline. We really could manage scarce resources more socially appropriately.
- guitarbill 8y agoI don't think this follows. To a degree, it's already true, because a lot of tech interviews just boil down to "have you learned all the pet CS questions in Cracking the Coding Interview?". A CV just gets you the interview. Of course you're right, some companies have software to filter CVs by keywords, and often it's as dumb as if the ad says "experience with Puppet", you need to say "experience with Chef, which is like Puppet". This is just playing the game, like everything is. Why do they do this? If you've been involved with hiring, you know the number of terrible CVs even a small company will get is shocking, so I'm sympathetic to automating things a bit. A lot of them are minimal effort, but that's the best case. Worst case is a flat out lie, because it takes more effort to catch - usually during the interview. So if we accept that CVs aren't just useful for raw information, but also convey some kind of measure of diligence (e.g. spelling), which you want in a programmer, then knowing about tools is also a useful measure. So I don't think it's going to be as bad as you make it sound.