The one that was rejected because he did not use semicolons in his JavaScript is interesting. So are a few others that were rejected for not knowing specific things about whatever language the company used.<p>These rejections at first seem idiotic, especially the semicolon one. Surely the company could have simply told the developer "our style standard requires semicolons" and the developer would have been able to quickly and easily adapt. And surely any decent developer could learn in a reasonable amount of time those parts of the language that the company uses that the develop has not previously used enough to memorize.<p>30-40 years ago that is what would have happened. It was not at all uncommon to get hired for a new job that used a language you didn't know or had not used much, on an operating system you hadn't used, and involving hardware that was new to you.<p>But 30-40 years ago, we stayed at our jobs a lot longer. I wonder if that is why it was different? If it took a couple months or so to start getting productive and a year to become expert at the stuff that was new to you it was no big deal. You were likely going to be there for the better part of a decade.<p>So maybe now, if you can only expect employees to stay on average 2-3 years at the big SV tech companies employers want people who start out as experts in as much as possible of the tools they use, so the only training to get up to speed needed learning that company's particular systems?