Picture two people sitting across from a hiring manager. One has a Computer Science degree from a state university, $60,000 in student loans, and can recite the OSI model like a bedtime prayer. The other has a homelab running Proxmox, a GitHub repo with actual projects, three certifications, and scars from the kind of 2 AM production problems that no classroom simulates.
In my experience, the second person gets the job more often than the first. Not always. But often enough that it matters.
The IT industry has a peculiar relationship with credentials. It talks about degrees while quietly hiring people who can actually fix things. That tension is your opening.
The Credential Game: Play It Smart or Skip It Entirely
Here’s the thing about certifications: they’re not proof of competence. They’re proof you can pass a test on a specific topic on a specific day. That’s a lower bar than it sounds—and also a completely valid door to kick open.
The CompTIA A+ gets you past the first resume filter. Network+ tells a hiring manager you understand how packets move. Security+ opens government contracting. These aren’t magic—they’re just keys. Don’t worship them. Use them.
“The cert gets you the interview. What you built in your lab gets you the job.”
Here’s how I’d sequence it if I were starting from zero in 2026:
- CompTIA A+ — Gets you through the first filter. Tier 1 entry point.
- CompTIA Network+ — Networking is the foundation of everything. Don’t skip this.
- CompTIA Security+ — Unlocks federal and contractor roles. Worth every hour of study.
- Cloud certification (AWS, Azure, or GCP) — Pick one ecosystem and go deep. The associate level is attainable in 3-6 months of focused study.
- Linux Professional Institute (LPIC-1 or CompTIA Linux+) — Because almost everything worth running runs on Linux.
That’s roughly 18-24 months of focused part-time study. You’ll spend maybe $2,000-3,000 total on exams and materials. Compare that to four years and $60,000 for a degree that may or may not teach you anything deployable.
The Homelab: Your Real University
A homelab is where theory dies and understanding is born. You can read about subnetting for weeks, or you can misconfigure a VLAN at midnight and spend two hours figuring out why your traffic disappeared. You will never forget what you learned in those two hours.
You don’t need expensive hardware to start. Honestly, a salvaged Dell desktop from an eBay auction can run Proxmox and host three or four virtual machines simultaneously. That’s enough to build a domain controller, a Linux web server, a firewall, and a client machine to practice on.
What should you actually build? Start simple, then layer complexity:
- A virtualized network with at least two subnets and a firewall between them
- Active Directory (or a Linux equivalent like FreeIPA) for identity and access management
- A web server you can break and rebuild
- A monitoring stack — Prometheus and Grafana are free and used in production everywhere
- Eventually: a Kubernetes cluster, even a small one. The pain is the point.
The homelab is also where you build the GitHub portfolio that replaces the degree on your resume. Document what you built. Write up what broke and how you fixed it. Hiring managers who actually know what they’re looking for will notice a repo full of real projects over a diploma every time.
If you want a deeper look at building out a capable machine without breaking the bank, I wrote about building serious hardware on a budget — the same principles apply to homelab gear.
Getting the First Job: The Part Nobody Talks About Honestly
The first job is the hardest. Not because you aren’t qualified — you might be more capable than the candidates with degrees. It’s hard because resume filters are blunt instruments operated by people who don’t always understand what they’re filtering for.
Here’s the honest play:
Tier 1 help desk is not a trap — it’s a launch pad. If you haven’t read The Tier 1 Trap, go read it after this. The trap isn’t the job — it’s staying there without a plan to move. Get the job, keep studying, keep building, and be vocal about where you want to go.
Small companies beat large ones for your first role. A 40-person company with one overworked IT generalist will teach you more in a year than a 10,000-person enterprise where you reset passwords in a ticketing queue. You want to be the person who gets called when something breaks — not a cog in a process machine.
Network locally before you network digitally. IT meetups, local user groups, and even Discord communities for specific technologies put you in front of people who hire. Most jobs that don’t require a degree are filled through informal networks before they hit job boards.
The Long Game: How Non-Traditional Candidates Win
Here’s the thing about the tech industry that the credentialing class doesn’t want to say too loudly: the field moves too fast for any four-year degree to stay current. The person who graduated with a CS degree in 2022 has knowledge that’s already partially obsolete. The person who’s been continuously learning, building, and working since 2022 is ahead of them.
Self-education isn’t just a workaround for people who couldn’t afford college. In this field, it’s superior preparation — because it trains you to do the thing you’ll do for the rest of your career. The real job of a senior engineer is to continuously learn new tools, frameworks, and systems that didn’t exist when you started. You’re not hired for what you know. You’re hired for your demonstrated ability to figure things out.
“School taught you to know the answer before the test. The job requires you to find the answer when nobody knows it yet.”
The non-traditional path also builds something the degree path often doesn’t: resilience and resourcefulness. When you’ve had to teach yourself everything, you’re not rattled by unfamiliar problems. You’ve been solving those your whole career.
The highest-earning engineers I’ve known personally were not the ones with the most prestigious degrees. They were the ones who couldn’t stop building things. The curiosity was the credential.
The Honest Part: What Won’t Be Easy
I’d be doing you a disservice if I made this sound frictionless. It isn’t.
Some companies have hard degree requirements that HR enforces without discretion. You’ll apply to some of those and get auto-rejected before a human sees your application. That’s annoying. Move on — those aren’t the companies worth fighting for anyway.
Government roles, especially those requiring security clearances, sometimes have more rigid requirements around education. That said, experience can substitute for education in many cases — it depends heavily on the role and the contracting agency.
The path requires real discipline. Nobody is checking your homework. Nobody will notice if you skip studying for three weeks. The freedom of self-directed learning is also its challenge. You have to want it more consistently than a classroom forces you to want it.
And if you ever hit a wall where a specific target company or role genuinely requires the piece of paper — community college Associate degrees in IT are cheap, fast, and check the box without the four-year price tag. That’s a legitimate tactical option, not a defeat.
The real question worth sitting with isn’t whether you can do this without a degree. Thousands of people are doing it right now. The question is whether you’re willing to build the proof of competence that replaces the credential — a lab environment, a GitHub portfolio, certifications, and the kind of problem-solving track record that speaks louder than a diploma ever could.
The door is open. The question is whether you’re going to walk through it or keep asking permission.
Scrivener.PRO 
Leave a comment