Skip to main content

I Saved My Boss's Derrière by Googling. Then I Wrote Down That I Still Don't Have a Real Job.

**Same week: "I am good, very good at finding things." Two days later: "Why am I not having a proper job in the IT field already?" I keep rereading those two lines like they belong to different people.**

Updated 5 min readMarkdown
Part of seriesFrom Hacker to Creative Director and back
I Saved My Boss's Derrière by Googling. Then I Wrote Down That I Still Don't Have a Real Job.

Part 18 of an ongoing series. [Start from Part 1.]


Here's the accomplishment, exactly as I wrote it that night: saved my boss's derrière, just by googling. No details, no drama, just the flat fact of it, filed next to "I am way more dedicated than the other interns" like it was nothing. Someone had a problem, I ran a search, I had the answer before anyone else did. Not a zero-day. Not a clever exploit chain. Googling. And it still counted — it still mattered enough that a colleague was covered and I was the reason.

Two days earlier, deeper into the structured pentesting, cross-referencing findings back and forth between two versions of the same product, I wrote something that stopped me longer: I find things that should have already been fixed long before my arrival. Basic functionality. Not exotic vulnerabilities buried in some clever edge case — basic stuff. Broken in a way that had clearly been broken for a while, that everyone closer to the product had stopped seeing. And the day after that, the line that named the whole feeling: the product is way more fragile than I think. It is really not ready to ship.

I know this move. I spent thirty years making a living off exactly this move.

Every agency I ever worked at hired outsiders for this reason whether they said it out loud or not. You bring in a new Creative Director, a new team, a fresh set of eyes on an account that's been running the same way for three years, and within a week they find the thing everyone stopped seeing. Not because the incumbent team was bad — because staring at the same brand deck for three years trains your eyes to skip past the parts that don't work anymore. Fresh eyes aren't smarter. They just haven't gone blind to the account yet. That was worth real money in advertising. Clients paid for it specifically. "Bring in someone who hasn't drunk the Kool-Aid" was a pitch I made more than once, and I made it because it was true.

So when I write down that I'm finding basic, ignored problems that predate me, and that the product isn't ready to ship, I recognize exactly what's happening. It's the same skill, pointed at a different kind of fragility. In advertising it was a headline that didn't land or a campaign built on an assumption nobody had checked in years. Here it's functionality that's been quietly broken since before I had a badge. Same eyes. Same instinct to say the uncomfortable thing out loud instead of nodding along because that's how it's always been.

Here's where it gets complicated, and where I'm not going to pretend I've resolved it: that same week, unprompted, I wrote why am I not having a proper job in the IT field already?

Not "why am I still learning." Not "why is this hard." A flatter, more frustrated question — I am demonstrably doing the thing. I found the bugs nobody else caught. I saved someone's afternoon with a plain Google search while everyone else was overthinking it — running the same problem through Claude, through ChatGPT, hunting for a clever answer, instead of just doing the dumbest, fastest thing: Google this shit. I wrote, the very same day, "I am good, very good at finding things" and "I am a maker and good thinker," which is not false modesty, that's a guy stating a fact about himself the way you'd state a fact about anyone else. And underneath all of that competence, still: intern. Still: candidate. Still: no title that matches the work.

In advertising, when you were the one catching what everyone else missed, the reward showed up fast — you got the account, you got the credit line, you got asked back into the room. The feedback loop was tight because the whole industry ran on being seen as good in real time. Cybersecurity doesn't work that way, and I knew that going in, intellectually. Knowing it and sitting with the gap between "I am clearly delivering" and "I still don't have the job" are two different things. One's a fact you accept. The other is a Tuesday night with a journal and a question you don't have an answer for yet.

I don't think the honest answer is that the field is broken or that I'm being overlooked. I think the honest answer is less satisfying than that: competence and credentialing move at different speeds, and I'm someone who spent three decades in an industry where they moved at almost the same speed, so the lag feels like an injustice when it's actually just... the shape of a career change. Certs take the time they take. Reps take the time they take. Nobody hands you a SOC Analyst title because you saved your boss's afternoon with a search engine, even though, on the actual day, that was the more useful skill.

What I'm keeping from this week isn't the frustration, even though I felt it and I'm not editing it out. It's the pairing. The same week I proved — again — that I can walk into a broken system I didn't build and find what's wrong with it faster than the people who've been staring at it longer, I also had to sit with not having the paper that says so yet. Both things are true at once. I'm good at this. I'm not done yet. Thirty years ago I'd have wanted those two facts resolved into one clean story by Friday. This week I just wrote them both down and let them sit next to each other, unresolved, which might be the actual skill I'm still building — not the googling, not the fresh eyes. Sitting with "not yet" without needing it to mean "not good enough."

About the author

  • 30 years in creative leadership (in the ad industry as a Creative Director) taught me one core skill: dissecting complex systems and finding the flaw before someone else does. My tech roots run back to 8-bit machine code on a C64 (yeah – 80s, baby!) Today, I’m combining that legacy hacker curiosity with modern threat detection and offensive security. BATTLE-TESTED LOGIC: Decades of high-pressure problem solving and systems analysis. HACKER MINDSET: I don't just follow playbooks; I reverse-engineer how the attack path actually works. CONTINOUS SKILL-UP: CompTIA Security+ certified (among other certs), building home labs, and constantly training for L1 ops to future Pentesting.

No comments yet. Be the first to comment.