Earlier quoted context omitted.
A degree is a proxy. A recruiter without specific knowledge cannot assess a developer's technical abilities in any meaningful way (even an extremely experienced developer can't reliably do so). The degree implies a school continuously assessed the individual abilities over the course of several years and found them acceptable enough to issue the degree. A degree offsets responsibility from the recruiter to the school…
> offsets responsibility from the recruiter Also from the potential hire himself. It's not that he sucks, his college didn't prepare him for this new role. It's not his lack of passion and really any deep interest in the craft, it's just that he had wrong lecturers, also most of them even weren't there to lecture most of the time, so what can you expect? So now we can hire him and train him for a year or more, becaus…
For large companies, predictability beats quality. Keep in mind strict business processes exist to defend organizations from incompetent workers, even at the cost of limiting competent ones. Incompetent workers are cheaper. Since the processes prevent competent ones from achieving outstanding results, there is an obvious incentive to hire only incompetent ones.
> I can't help but feel it's somehow unfair.
Not sure about fairness. I certainly don't like it.
> Yeah. Some abilities.
Those are the abilities large banks and insurance companies want. For the average non-technical manager, being able to consider developers as interchangeable cogs beats developers that are impossible for managers to characterize or predict.