Job titles industry conventions are the reason two people doing identical work can hold titles that share no words at all — and the reason a job board that treats titles as a controlled vocabulary ends up losing candidates it should have found.
This article looks at where titles come from, why seniority and role are two separate facts that are constantly crammed into one field, what goes wrong when titles are translated, and how to store a title so that it survives all of it.
Why do titles differ so much between industries?
Because a title is a label an organisation invents for its own convenience, not a classification that anybody governs. It has to do three jobs at once — tell an outsider roughly what the person does, signal their position in an internal hierarchy, and sometimes satisfy a payroll or regulatory category — and each organisation resolves that tension differently.
Industry shapes the vocabulary heavily. Engineering and technology organisations lean on functional nouns that describe a domain. Finance and accounting functions lean on titles that are tied to authorisation and review responsibility. Healthcare uses titles that are entangled with licensure, because in that world the title is often a legal category rather than a courtesy. Education and research use ranks that are tied to appointments. Sales and marketing invent titles freely because the title is frequently part of the offer. Manufacturing and logistics use titles that describe a station or a function on a line.
The practical result is that a title which is precise inside one organisation is close to meaningless outside it, and the longer the organisation has existed, the more internal history its titles carry.
Is seniority the same thing as a title?
No, and conflating them is the single most common modelling mistake in hiring systems.
Seniority describes a band of experience and expectation: entry, mid and senior are the three bands a career record usually carries. A title describes what the work actually is. The two move independently. A senior individual contributor and a mid-level manager can share the same seniority band and hold titles that look nothing alike, and the same title in two companies can sit in different bands — one organisation’s lead is another’s entry point.
The failure mode is concrete. When a form asks for a title and a ranking feature parses the word senior out of it, candidates in organisations that do not use that word are ranked down for reasons that have nothing to do with their experience. The fix is structural rather than linguistic: keep seniority as its own field, supplied explicitly, and treat the title as free text that describes the work.
| Industry | Titles tend to carry | Titles tend to omit |
|---|---|---|
| Software and engineering | The technical domain and the level of ownership | Anything about the customer or the business line |
| Finance and accounting | Review and authorisation responsibility | The specific product area |
| Healthcare and nursing | Licence category and care setting | Administrative or teaching responsibilities |
| Education and research | Rank and appointment type | Departmental or clinical duties |
| Sales and marketing | Territory, segment and quota ownership | The underlying craft |
| Manufacturing and logistics | Station, shift and process step | Supervisory scope |
Read down the middle column and the pattern is clear: each industry names the thing it is accountable for, and leaves everything else unsaid.
What goes wrong when titles are translated?
The meaning drifts, often in the direction of inflation or deflation. A title that sounds like a leadership position in one language can read as a junior clerk’s label in another, and the drift is not a translation error in the narrow sense — the words may be perfectly accurate while the impression they create is entirely different.
Three sources of drift recur. Titles carry an implicit hierarchy that does not transfer: a word that ranks high in one market ranks differently in the next. Titles are built from idioms that have no equivalent, so the translator reaches for a near-synonym that belongs to a different profession. And some titles are protected in one jurisdiction and generic in another, so the same words carry a regulatory weight in one place and none in the other.
The safe handling is to keep the title exactly as the person wrote it, in the original language, and to add a machine-readable classification alongside it rather than instead of it. Rewriting the title into a tidy English phrase destroys the only piece of evidence about what the employer actually called the role.
How do you map a title to a classification system?
By treating published occupational classifications as a reference for grouping, not as a replacement for the title a person gave. These systems exist precisely because titles are unreliable, and they reduce the whole messy space to a manageable set of groups so that reporting and comparison become possible at all.
Three cautions apply when using one. A classification describes the work, so it will happily place two very differently titled roles in the same group — which is correct and should not be treated as an error. It will also place two similarly titled roles in different groups, because the industry differs, which is equally correct and equally surprising the first time it happens. And it changes between versions, so a mapping is only meaningful with the version recorded next to it.
A mapping should therefore always be an addition to the record, with a note of which system and which version produced it, and never a silent overwrite of what the employer wrote.
For developers: how to store a title field
Store the title as the person’s own text, in its original language, and keep every classification decision in a separate field beside it.
Four habits cover most of the ground. Keep the original string unmodified, including the punctuation and unusual capitalisation, because those are free signals for a parser to learn from. Store the language of the title explicitly rather than guessing from the characters, since a title can be written in one language while the rest of the record is in another. Keep the seniority band as its own enumerated value supplied from the source rather than parsed out of the title text. And when a title is matched to a classification, record the mapping as a separate association with its own provenance, so a bad mapping can be corrected without touching what the person wrote.
For test data, the lesson is that variety is the point. A set of titles drawn from one industry and one country will pass every test and demonstrate nothing, because it never exercises the branches that only appear when a title is in a second language, contains an ampersand, is written entirely in lower case, or runs to eleven words. The profiles described here are the place those variants should come from, and the skill vocabulary sitting beside them has the same synonym problem in a different form.
The illustrations in this article use job titles that are common in their industries as examples only. They name no employer and describe no person holding such a role, and the sample data they come from is fabricated for software testing and form demonstration.
Next steps
Pick the title field in your own system and ask two questions of it. First, can it hold a title in a second language without any conversion step? Second, does anything downstream parse the word senior out of the text and assign a band from it? If the answer to either is no, the title is already being treated as a taxonomy it was never designed to be, and a generated set of multi-language titles is the fastest way to see the damage. The career profile tool can produce records across several countries and industries at once.