Why No One Agrees What an Architect Is
Open ten architecture job adverts and you will read the same paragraph ten times. Azure. AWS. Kafka. Kubernetes. Terraform. SQL. React. Then, near the bottom, almost as an afterthought: “must have architecture experience.”
Everything above that last line describes knowledge. Nothing above it describes purpose.
Now try the same exercise with a different profession. Imagine hiring a surgeon by listing the scalpel, the sutures, the MRI, the CT scanner — and then adding, quietly, “must have surgery experience.” Nobody writes that advert. Nobody needs to. Everyone already knows what a surgeon is for, so the tools are understood as servants of the objective, not the objective itself.
Architecture has never been handed that clarity. And so we do the only thing left to do when the purpose is unstated: we describe the role by its instruments. Then we act surprised when two architects, two managers, and two candidates walk out of the same conversation with three different ideas of what the job actually is.
The instruments were never the constant. CORBA came and went. SOAP rose and faded. Microservices arrived, then containers, then AI. Through every one of those turns, the profession survived — not because it kept up with the tools, but because it was never really about them. It was about making good decisions in an environment where the tools never stop changing.
That part does not go out of date. It is also the part the job advert cannot bring itself to name.
Here is a test worth running on your own team. Ask five people to define the architect’s role in a single sentence — with no technology allowed in the answer. The silence that follows is the whole problem. Not because nobody knows, but because nobody has ever been asked to separate the purpose from the plumbing.
The good news is that the definition exists. It is simply top-down instead of bottom-up: the role is defined by the decisions it protects, not the technologies it touches. Get that the right way round and a surprising amount of the confusion clears at once.
That inversion — from tools to purpose — is the argument of the manifesto, and the spine of everything in the books.