The 'Systems Programmer' Identity Is Maladaptive for Career Planning

I've come to believe that calling yourself a "systems programmer" or "systems hacker" is maladaptive for career planning.

With rare exceptions, people in industry who write "systems code" are really specialists: avionics, automotive, audio, CUDA, Linux kernel, Windows drivers, games, CNO, endpoint, etc. Your economic value isn't in knowing C, Rust, tooling, or "system empathy." It's in the mental context you've built in your subdomain.

The "Real Programmer" Myth

But many systems folks still cling to the "Real Programmer" myth—the Ken Thompson archetype, or the legendary "Story of Mel." The idea that a real systems hacker can do anything.

Reality check: a lot of that energy goes into rebuilding old systems and rehashing solved problems. Great hobbies, but hobbies won't pay your mortgage.

If you want a career, you have to be honest: are you working in a problem domain with actual market demand? We don't need another UNIX. We don't need more "90% problems" that could be solved in Go, Java, Python, or JS.

Ignore Thompson. Ignore Mel. Niche down.

Geography Matters in the RTO Era

And in 2025, don't ignore geography. The remote work euphoria is gone; we're in the RTO era. Systems specialists are mission-critical, which makes them more likely to be pulled back into offices.

Translation: your location has to line up with where the subspecialty's jobs are. Or you have to move.

• Self-driving cars → SF or Austin
• Windows kernel → Redmond
• Quant work → NYC
• Offensive cyber → Maryland/Virginia (and a clearance + polygraph)

The Bottom Line

Systems hackers need to get real: pick a niche that has demand and geographic affinity. Otherwise, you're facing constant headwinds and opting into a much harder path.