One word, two professions: the architect problem in job data

Search any major job board for architect and count what comes back: solutions architect, cloud architect, data architect, security architect, enterprise architect. Somewhere in the pile, a person who designs buildings. The software industry borrowed the word decades ago and now dominates its search results. For a career data system, this is not a naming quirk. It is a contamination problem that silently ruins every statistic downstream.

If you average the salaries of building architects and cloud architects, you get a number that describes nobody. If you compute which skills architects need and a third of your sample is AWS postings, you will tell a licensed building designer to learn Kubernetes. Career sites do this constantly. It is one reason their numbers feel plausible and useless at the same time.

How we split the word

Our pipeline treats the bare word architect as claimable only by an exact match. A posting titled just Architect maps to the building profession. Anything in the pattern of something architect, where the something is a technology word, routes to the technology occupation or, when we cannot tell, gets excluded rather than guessed. Every excluded title goes to a review log, and the dictionary grows from that log weekly.

The same discipline applies across the taxonomy. Designer is claimed by six different professions in our data. Engineer by more than ten. Analyst is a suffix on half the business world. Each of the 145 occupations we track carries its own list of exact titles and qualified phrases, currently about 600 synonyms, and the matcher takes the longest specific phrase before it ever considers a generic word.

The scale of the collision is visible in our own counts: the building profession holds 1,178 postings in the corpus while solutions architect alone holds 736, and the tech variants together outnumber the people who design buildings. An unsplit average over that pile would miss every number that matters by double digits.

Why you should care even if you are not an architect

Because whatever your title is, some other profession is probably squatting on part of it. Producers exist in film, in music, and in software. Consultants exist everywhere and mean nothing. When a career tool shows you a salary band or a skill list, the first question worth asking is: whose postings are actually in this average? If the tool cannot answer, its numbers are weather, not measurement.

Ours answers. Type architect into the instrument and you get two entries, clearly labeled by field, with separate data underneath. The building one currently reads 1,090 postings. The pile it was rescued from was several times larger.