Maybe it is time for a set of unions or guilds to do that certification for you.

This. Just as doctors or lawyers or civil engineers can't do their jobs before being vetted by their own professional bodies it's time we do the same for software engineering.

If all you did was an entry level "bar exam, it'd be pretty much useless. A newly graduated CompSci student, is really just an apprentice, who may then (if they continue to work hard, and are given challenging work) go on to become a master craftsman/journeyman over the next 5/10/20 years.

The same is true of those other fields too really - I certainly wouldn't want a newly qualified doctor operating on me, or lawyer defending me, or civil engineer designing a bridge I'm driving over. It's nice to know that someone has been professionally educated and passed some entry level exam, but to be useful in a field it's experience that counts.

Doctors go through residency after passing their exams, we should have the same for engineers. Civil engineers have layers of seniority and designs of junior engineers have to be reviewed and approved by senior engineers, we should have the same.

I don't assume it "wasn't looked at", but I absolutely do think that a lot of the time it "wasn't understood" because the recruiters reading it only have very simply "keyword lookup" ability, instead of actually reading the resume.

I don't fill my my resume with a bunch of spam buzzwords for every adjacent technology I've ever used, because certain things are kind of implied by other things. If I put "set up multiple clusters across different Linux systems", I don't also cram in "systemd, bash, upstart, scripting, ls, cp, du, nohup", despite the fact that I know how to use all of those things, because I think they're implied by "me setting up Linux clusters".

A software engineer reading my resume would come away with a decent understanding of what skills I have, but a recruiter who doesn't know anything outside of keyword-matching and hitting the `fwd` button in Outlook (which appears to be most recruiters) will see "HE DOESN'T KNOW BASH, SEE HE DIDN'T PUT IT ON HIS RESUME."

Now, of course, most of this is on me, it's up to me to learn how to play the game, whether or not I like the system doesn't really change anything, but as far as I can tell, the "solution" to this is to turn my resume into a low-quality SEO-spam piece of shit so as to try and satisfy the most incompetent person who might read it.

> but as far as I can tell, the "solution" to this is to turn my resume into a low-quality SEO-spam piece of shit so as to try and satisfy the most incompetent person who might read it.

If a posting gets 500 applications (which is about how many apps the last 4 roles I’ve listed got before we closed them) and we have an engineer spend 5 minutes per resume reading through each resume, that’s a full week of engineer time spent on screening alone. That’s not a good use of time when most of the resumes are a straight no.

I’m assuming your writing style is different in professional environments, but if it’s not, and I saw even like 10% of the snark you’ve put here, I’d instantly dismiss you unless we were hiring for a principal into fellowship IC role and you were a 100% match.

If you’re writing your resume to be read by software engineers or sysadmins, you’re writing for the wrong audience. That’s not their fault for being “incompetent”, it’s yours.

I don’t really put any snark into my resume, so I can’t tell you how successful that would be.

I don’t write it to be “read by software engineers” per se. I describe my skillset and things I have worked on. I don’t load it with a million buzzwords of every single noun that I am aware of.

I acknowledge that I probably play the game “wrong”, insofar that there’s any “right” way of doing it, but I don’t have to like the game, and I certainly am allowed to think that it’s very frustrating that I have to fill my resume with SEO spam of synonyms because most recruiters are unwilling to learn anything more than basic keyword matching.