3 ms·
I took it as satire. Guaranteed somebody could find a way to disqualify an applicant for this. Here are some hiring manager thought bubbles: * "Oh boy, this ta
by thesmallestcat 10y ago
I took it as satire. Guaranteed somebody could find a way to disqualify an applicant for this. Here are some hiring manager thought bubbles:
* "Oh boy, this takes me back to installing Slackware from floppies. So I guess you're more of a backend/systems guy? This is a full stack position. Are you sure you want to work on the frontend?"
* "Amateur hour. Copied somebody else's bootloader. We really would like to see more systems-level contributions to open-source projects."
* "Overkill. Somebody who can't see how a PDF is appropriate here won't be a culture fit. Does he think I have all day to figure out how to open this thing?"
* "Doesn't know Linux."
Because in the end, it's all bullshit.
- frozenport 10y ago* Couldn't hold down a job because he spent too much time working on personal projects.
- bbcbasic 10y ago* And his Github commit calendar isn't lit up like a Christmas Tree.
- vidarh 10y agoBeing disqualified isn't inherently a bad thing. I work hard to ensure my "profile" ensures I get disqualified from things I don't have any interest in, to keep focus on the areas I do well. E.g. if he is a backend guy, then making that exceedingly clear is a good way of a) avoiding recruiter spam about frontend positions, b) stand out as someone qualifying themselves as a specialist. The latter is more important the more senior positions you go for - nobody will believe you're an expert at everything, and clearly qualifying yourself with respect to which areas you know in depth makes demonstrates confidence (contrast with the candidate who changes his tune about which subjects they specialise in the moment you mention another technology, trying to be perfect for anything you mention - it is rarely credible)