Who’s Allowed to Build Your Bank’s Software that manages Billions of Dollars? Anyone.

Doctors, lawyers, and accountants all need a license to practice. But the people writing the code running your bank, your hospital, and your AI assistant need none — here’s the surprisingly good reason why.

Doctors have medical councils. Touch a patient without a degree? It’s a crime.

Lawyers have bar councils. Argue in court without clearing the exam? Illegal.

Chartered Accountants have the ICAI. Sign an audit report without qualifying? Impossible.

Now ask yourself: what’s stopping the person writing the code behind your bank’s payment system, your hospital’s patient records, or the AI agent quietly reading your inbox?

Nothing. No degree required. No license to revoke. No central board to certify you’re fit to practice.

And here’s the part that should unsettle you more: the industry is proud of it.

We Don’t Care About Your Degree

Software engineering is probably the only high-stakes profession on Earth where its own leaders boast about having no gate at all. Crack the technical interview, prove you can solve the problem, and you get the keys to the castle — no questions asked about where, or whether, you studied.

A self-taught programmer with a laptop and a Claude Code subscription can be handed the responsibility of writing code for systems that move billions of dollars or keep hospitals running. There’s no professional body standing between them and production.

Software is the only high-stakes industry where its leaders proudly say: “We don’t care about your degree.”

It sounds like a terrifying paradox — critical infrastructure, run by anyone who can pass a whiteboard test. But look closer, and there’s a very deliberate logic for why a single, central gatekeeper has never existed in tech — and probably never will.

1. The Industry Is Too Broad for One Stamp of Approval

A front-end engineer building a checkout flow, an embedded engineer writing firmware for a pacemaker, a cloud architect designing core banking infrastructure, and an AI engineer orchestrating autonomous agents are not in the same profession by any meaningful definition. They share a job title and almost nothing else.

A single universal license covering all of that would have to be so generic it would mean nothing — the equivalent of certifying every doctor on Earth, from dermatologists to neurosurgeons, with one shared exam.

2. Tech Regulates the Work, Not the Worker

This is the real twist: software is regulated — just not the way medicine or law is. Instead of licensing the individual, the industry attaches accountability directly to the system being built.

• Writing avionics software? DO-178C has to sign off, not you.

• Handling patient data? HIPAA and a stack of compliance controls govern what your code can and can’t do.

• Processing a credit card transaction? PCI-DSS and banking regulators are the real gatekeepers.

Tech doesn’t license the worker. It regulates the work.

The accountability sits with the outcome, not the diploma on the wall. Nobody asks for your certificate before a payment goes through — they ask whether the system passed its compliance audit.

3. The Field Moves Faster Than Any Certificate Can Track

Even if a universal license existed, it would expire the moment it was printed. Technology doesn’t evolve in decades, the way the foundations of medicine or contract law do. It evolves in product cycles.

A certification earned ten years ago says almost nothing about whether you can design a secure distributed system, build a reliable AI workflow, or architect a resilient cloud platform today.

A board exam written in 2016 has no opinion on Kubernetes, LLM agents, or zero-trust architecture, because none of it existed yet. Trying to centrally certify software engineers would be like trying to license meteorologists for a climate that changes every eighteen months.

So What Actually Keeps the Lights On?

Not a license. Not a diploma. Something more distributed, and arguably more rigorous:

Architecture reviews. Automated testing. Peer review. Observability. Compliance audits. Continuous validation, every single day, on every system, indefinitely.

It’s not a single gate you pass through once at age twenty-five. It’s a thousand smaller gates you pass through every week, for your entire career.

Software safety doesn’t come from a license. It comes from the relentless, boring discipline of checking the work — every day, forever.

That’s the part that doesn’t fit on a framed certificate. But it’s also, quietly, why a system with no bar exam still manages to run the world.

So no, there’s no bar exam for software engineers. There probably never will be one. The test isn’t given once, in a room, by a board — it’s running right now, in production, on every system you’ve ever touched, and it never stops grading.

The real credential in software isn’t a piece of paper. It’s the system still standing the morning after. No board can issue that one. You earn it again, every single day, whether anyone’s watching or not.

So the next time someone asks who’s qualified to build the systems the world runs on — maybe the better question is: qualified by whose test?

---