Engineers keep questioning whether their credentials matter
A thread about completing a computer science degree on Coursera surfaced the usual split: congratulations from some, skepticism about employer perception from others. One commenter asked bluntly whether the poster had researched how employers view such a diploma before spending time and money on it. The technical counterpoint was that pure CS can be taught on a chalkboard, so the medium matters less than the content.
This sits alongside the 'Software Engineering is not Engineering' thread, which got 429 rate-limited before many people could read it, producing the meta-joke that this was itself proof the field lacks rigor. The underlying debate is real: what credentials signal competence in software, and does it matter?
YC hiring posts are running heavily toward 'founding engineer' and 'applied AI' roles, with less emphasis on formal credentials and more on demonstrated output. The market is moving toward portfolio over pedigree, but slowly and unevenly.
So what?
If you're hiring, the credential debate is a proxy for the harder question of what you actually need to evaluate. Founding-stage companies are increasingly ignoring credentials entirely and asking for work samples or trial projects. If you're still filtering on degree type at the resume stage, you're probably cutting good candidates and keeping mediocre ones who tested well.