Skip to main content
SubZeroDev

Professional uncertainty since 2026.

Well… Why not?


Head Code Wrangler: My Résumé Has Returned to Its Natural State

· 6 min read

I found my favorite YouTuber.

This man was talking about a résumé he had apparently weaponized against another human being.

Not lied on.

Not embellished.

Weaponized.

There is a difference.

The résumé contained the kind of material that makes an interviewer stop processing language normally.

At one point there was a joke about having outstanding warrants.

The obvious problem, according to the interviewer, was that perhaps outstanding warrants should not be on a résumé.

The obvious response was:

Why not?

They're outstanding.

Excellent warrants.

Top-tier warrants.

Possibly award-winning warrants.

That was when I knew I had found one of my people.

Then the man got asked the traditional interview question:

Tell me something about yourself.

This is normally where a candidate says something like:

"I'm passionate about solving complex problems in collaborative environments."

Which is corporate for:

"Please give me money. I have memorized the ritual."

This man did not do that.

The interview continued descending into complete nonsense until eventually the reveal came:

The whole thing was a prank.

He went back to his real office.

His boss asked which competitor they should prank next.

Beautiful.

Absolutely beautiful.

There was only one problem.

I had been watching the whole thing thinking:

Wait. I could use some of this.

This Was Already Happening​

Years ago, when I was actually responsible for software and therefore theoretically a serious professional adult, I had business cards printed.

The title on them was:

Head Code Wrangler

Not as a joke card.

Not for Halloween.

Not because I had lost a bet.

Those were my actual business cards.

I would meet another professional human being, shake their hand, and hand them a small professionally printed rectangle informing them that I was the Head Code Wrangler.

Apparently I had already started this experiment decades ago and then somehow wandered into respectable résumé formatting.

Tragic.

The Standard Résumé Is a Crime Against Language​

Every résumé eventually starts sounding like it was generated by the same malfunctioning committee.

Results-driven.

Strategic leader.

Cross-functional collaboration.

Proven track record.

Dynamic environment.

Stakeholder alignment.

Please stop.

I have spent more than twenty years building software.

I have written code.

I have deleted code.

I have inherited code that should have been sealed inside concrete and dropped into the ocean.

I have built systems.

I have led teams.

I have sat in meetings where eighteen people discussed a problem that three lines of code had already solved.

I have deployed things.

I have broken things.

I have fixed things.

I have explained things.

I have occasionally explained the same thing again because apparently the first explanation was merely ceremonial.

There is a story in there.

And somehow the accepted format is to compress all of it into:

Led cross-functional engineering initiatives to deliver scalable enterprise solutions.

No.

Fuck that.

The New Plan​

I was already planning two résumés.

One normal.

Professional.

Respectable.

The kind of document that can pass through an applicant-tracking system without causing a small electrical fire.

And then there is the other one.

The one that still contains real qualifications.

Real projects.

Real technologies.

Real accomplishments.

But presented in a way that forces the reader to answer a more important question:

What the fuck did I just read?

I don't want to fabricate anything.

That ruins the game.

The facts stay true.

The language becomes increasingly unreasonable.

Maybe one job title stays normal.

The next one becomes Head Code Wrangler.

Then somewhere later:

Sorcerer Supreme

Perhaps:

Lord Commander of Sales

Commodore of Digital Sales

Keeper of the Sacred Build Pipeline

By the time the reader reaches the bottom, they should have learned what I can actually do while also developing mild concern about who exactly submitted the document.

Perfect.

A Résumé Should Have a Plot​

Then I realized something worse.

Why does the résumé have to be a database dump at all?

Company.

Title.

Dates.

Bullets.

Company.

Title.

Dates.

Bullets.

Human life presented as a SQL result set.

What if it reads like a story?

I started here.

Then this happened.

Then somebody made the catastrophic decision to give me responsibility.

Then I discovered architecture.

Then distributed systems.

Then leadership.

Then cloud infrastructure.

Then apparently I became a Sorcerer Supreme.

Then, after decades of doing perfectly normal software work, I did what any reasonable engineer would do.

I built a fucking game engine.

There.

That's a résumé I might actually want to read.

The Important Part​

This only works if the ridiculous résumé is sitting on top of legitimate experience.

Otherwise it's just a man wearing a wizard hat asking for employment.

The joke is the contrast.

Under Sorcerer Supreme there needs to be actual architecture.

Under Head Code Wrangler there needs to be actual engineering leadership.

Under whatever deranged title I assign to myself next, there needs to be something real enough that removing the joke leaves a perfectly defensible professional history.

That's what makes it fun.

The reader laughs.

Then keeps reading.

Then realizes:

Oh.

He actually did all this shit.

Marketing​

Some people will hate it.

Excellent.

Some recruiter will look at it for twelve seconds and decide I am an unacceptable risk to organizational stability.

Also excellent.

Someone else will see Head Code Wrangler, keep reading, discover the experience underneath it, and think:

"Who the fuck is this guy?"

Now we're getting somewhere.

Because that is marketing.

Not everybody has to like the thing.

They have to notice the thing.

And if I already have the respectable version available, this one does not need to behave.

It can walk into the room wearing a cape.

It can introduce itself as Sorcerer Supreme.

It can place twenty-plus years of engineering experience on the table.

Then it can stare directly into the recruiter's soul.

At some point I stopped needing permission to do stupid things with my own résumé.

Apparently I only needed to remember that I used to hand people business cards that said:

Head Code Wrangler.

The résumé is not becoming unprofessional.

It's returning to its natural state.


Well... why not?