Jobs I’ve Already Had (Unofficially)

Or: Why Titles Are Bad at Describing Actual Work

I’ve been on the job hunt lately, which means I’ve read more job descriptions than any human should.

If there’s one thing I’ve noticed, it’s that recruiters and hiring folks really, really love their neat little job titles.

But real life? It’s way messier than any job title out there.

I can’t even count how many job descriptions I’ve read and thought, “Hang on, I’ve done all of this—just never with that particular title.”

Somewhere Between “Other Duties as Assigned” and Reality

Titles are just a shortcut. The real work? That’s a whole different story.

To be fair, if we tried to cram everything we actually do into a job title, those titles would be a mile long.

Just because you never had the official title doesn’t mean you weren’t already doing the job.

Job Experience, But Make It Chaotic

I’ve done entire jobs without ever getting the title to match. I’m willing to bet a lot of you have, too.

So, just for fun, here are a few of the unofficial jobs I’ve somehow collected along the way. Each of these roles came with its own set of challenges, unexpected lessons, and more than a few moments where I wondered if anyone else had ever worn this many hats at once:

Chief Cat Herder
(Yes, they were adults. No, it didn’t matter.)

• Coordinated people who all had their own priorities, and not a single shared calendar in sight
• Somehow kept timelines moving, even though I had zero actual authority
• Reminded everyone (more than once) what we’d already agreed to
• And, against all odds, still managed to get things shipped

(No actual cats were harmed, but several egos were gently redirected.)

Human API
(Bridging systems that were never meant to talk to each other.)

• Played translator between customers, support, product, and engineering
• Took vague requests and turned them into something people could actually use
• Explained the same thing five different ways until it finally clicked
• Prevented at least a couple of totally avoidable disasters

(No documentation, just vibes and experience.)

Mediator
(Unpaid. Uncertified. Constantly in demand.)

• Navigated conflict without letting it blow up
• Helped people hear each other
• Kept things moving without anyone losing their cool

(Surprisingly effective for something that was “not my job.”)

Project Manager
(No, really.)

• Coordinated people who didn’t actually report to me
• Kept track of timelines, blockers, and all the moving parts
• Herded cats across teams, time zones, and priorities. Sometimes all at once.
• Got things done without ever having the official PM title

(But sure, my title said “Support Manager.”)

Product Manager (Adjacent)

(Close enough to feel the impact, far enough to avoid the roadmap meetings.)

• Collected feedback, spotted patterns
• Spoke up for customers when priorities shifted
• Turned pain points into real requirements

(Heavily involved. Lightly credited.)

Change Manager

(Because “we’ll just roll it out” is never the whole plan.)

• Helped teams get used to new tools and processes
• Explained what was changing and why it mattered
• Took on the frustration so others didn’t have to

(Absorbed resistance. Delivered calm.)

Trainer / Educator

(Turns out explaining things is a fundamental skill.)

• Built onboarding from the ground up
• Explained complicated things in a way that actually made sense
• Helped people feel like they could handle it, instead of just being overwhelmed

(Confidence-building included at no extra charge.)

Why This Gets Weird When You’re Job Hunting

How do you show this on a resume if you never had the official title?

If you’ve done the work, it counts—don’t undersell yourself.

Don’t be so literal that you erase your own experience.

Turns Out I’ve Been Busy

Looking back, I realize just how many hats I’ve worn over the years, whether or not the titles matched. And those experiences are often what set us apart—far more than any title ever could.

Titles change. Skills don’t.