The Degree Question, Settled by Two Contradicting Careers

Two careers, side by side, say more about degrees than any career-advice column manages. The first: someone who has spent years building an IT career on a degree they faked — their word, not mine — and who now, established and competent, wants to quietly complete a real one by distance learning. The second: a graduate with an Ivy League degree, no student debt, savings in the bank… announcing they've given up looking for work entirely.

Hold those two people in your head at once. The person without the real degree built the career. The person with the gold-plated degree can't get one started. If the degree were the thing doing the work, both stories would be impossible.

What a degree actually is, mechanically

Here's the position this piece will defend: a degree is a filter at the front gate and close to irrelevant after you're through it. It exists so that screening software — and screeners acting like software — can cut a giant pile of applications down to a manageable one using a checkbox that requires no judgment. That's not education doing its job. That's logistics.

Which explains both stories at once. The faker got through the gate years ago, and after that nobody ever asked again — because past the gate, all anyone measures is whether the work gets done. The Ivy grad keeps sailing through gates and dying in interviews, because gates were never the hard part for them, and nobody taught them the part that comes after.

The degree opens a door. It has never once carried anyone through a room.

Don't do the thing the first one did

Let's be unambiguous: don't fake a degree. Not because you'll necessarily be caught this year — they weren't, for years — but because verification is cheap now, background checks are increasingly automated, and a faked credential is a landmine that never expires. Every promotion, every acquisition, every new HR system is a fresh chance for it to surface. And unlike a thin resume, which is a solvable presentation problem, a discovered lie ends the conversation permanently. That person has spent years doing competent work while carrying a thing that could still detonate the whole career. That's not a hack. That's a hostage situation.

The honest versions of the same move work nearly as well and cost nothing to carry. Which brings us to tactics.

Writing the education section when there's no degree in it

Do not leave it blank — blank reads as “hiding something” to both software and humans. Do not write anything that implies completion. Between those rails, you have honest options:

• “Coursework toward BSc Computer Science — left to take a full-time support role” is honest, gives the filter something to match on, and pre-answers the why.
• “Self-taught: networking, scripting, systems administration — certs listed below” tells a coherent story.
• Industry certifications go here too — in plenty of IT, security and infrastructure roles they match filters better than a generic degree does, because they name the exact skill the listing asked for.

“Degree required” is a default, not always a decision

Read listings the way they were written: someone copied the last listing. “Bachelor's required” is boilerplate on most postings, a real constraint on some — regulated professions, roles tied to visa sponsorship, government contracts. Learn to tell them apart, because the answer changes your strategy — the same soft-versus-hard reading that applies to every requirement in an “entry-level” posting applies double to the degree line. For the boilerplate majority, the people who get hired anyway all did some version of the same thing: they arrived through a side door. A referral from someone inside — which skips the filter entirely, since referred resumes usually get human eyes regardless of checkboxes. A portfolio that makes the checkbox feel silly. A contract gig that turned permanent before anyone thought to check.

That's your actionable list, and it's ordered by effectiveness: person first, proof second, filter-matching third. And the referral ask is smaller than people fear. Not “can you get me a job” — nobody wants that weight. Just: “I'm applying for the support-engineer opening on your team. The listing wants a degree I don't have, but I've run exactly this stack — could you flag my application so a human reads it?” Specific role, honest gap, tiny favour. Most insiders will do that much for a near-stranger, because it costs them one message. If your whole strategy is submitting applications into portals that ask about degrees, you've chosen to fight the filter on its home turf. Every hour spent getting one insider conversation outperforms an evening of portal submissions — not because the portals never work, but because you, specifically, are the case the portal is built to reject.

The interview moment you're dreading

At some point a human asks: “I noticed you didn't finish your degree — what happened?” This question has ended interviews, and it shouldn't, because the losing move isn't the missing degree. It's the apology spiral. The answer is one sentence, flat, forward-facing:

I left to earn — support desk first, then systems work, and I never needed to go back. Happy to walk through what I've run since.

No justification tour. No “I always meant to finish.” You redirect to the thing you can win: the work. If the interviewer keeps digging on the degree after that, note it — you're learning how this company weighs parchment against evidence, and you're allowed to weigh them back.

The Ivy grad's problem is your problem too

Back to the second case, because it's not really a story about giving up — it's a story about a bet that stopped paying. The market has quietly repriced pedigree. Screening got automated, application volume exploded, and in that flood a strong credential became a mild advantage instead of a decision. What actually converts interviews into offers now is the same for the Ivy grad and the self-taught admin: specific, checkable stories about work, told well, out loud.

And “out loud” is doing real work in that sentence. The front gate isn't just checkboxes anymore — high-volume screening increasingly means automated interviews, where a system fires questions at you and scores the transcript against a rubric nobody shows you. If you're routing around a degree filter, expect to meet an AI interview on the way, and practise for it specifically. The candidates it punishes hardest are the ones whose value needs a little context to land — which, if your resume has no degree on it, is you.

The faker and the Ivy grad are both proof of the same rule from opposite ends: gates are not careers. Get through the gate honestly, cheaply, by any side door you can find — and put your actual effort into the room after it.