Why Job Titles Tell You Less Than Your Work Samples

A job title is a short label a company attaches to a bundle of duties, and the same label can cover very different work. An analyst at one firm may spend most weeks reconciling spreadsheets, while an analyst at another designs experiments and presents results to the people who set prices. Both can truthfully use the word. A title tells a reader roughly where a person sat in a structure. It rarely shows what they could do on an ordinary Tuesday with no one to ask, and that is the question most hiring decisions are really about.

Why the same title means different things

Titles are set locally. Each company decides them according to its size, its history, its pay structure and sometimes its wish to look larger to people outside. A small team may give someone a senior-sounding title because the business needs a name for their role in conversations with clients. A large organization may use titles mainly to mark pay bands, which says more about budget than about skill. Titles also get renamed when departments are reorganized, so a role may carry a new label while the work stays much the same.

None of this makes titles dishonest. It makes them a compressed summary, written by someone else for their own purposes. The useful response is curiosity rather than suspicion. When a title appears in a shortlist, treat it as the start of a set of questions: what did this person own, who depended on the work, and what would they have to show to prove it?

What a work sample shows that a title cannot

A work sample is something a reviewer can read or run without knowing the employer's ladder. It might be an analysis with a stated question and a clear method, a small tool with honest documentation, a written postmortem, or a model another person can reproduce. The reviewer checks the artifact against their own standard, which is the one thing a title cannot offer. They can see whether the problem was framed sensibly, whether the result was tested before it was trusted, and whether the author was candid about what the analysis could not show.

The trade-off is access. The strongest samples often come from paid work that cannot leave the company, which is why many people build a smaller public sample on open data and write it with the same care. A sample is not a copy of the job. It is evidence of how the author thinks, and another person can inspect it without a phone call. That is what makes it persuasive, and it is also why a sample with a hidden flaw can damage a reputation faster than a modest title ever could.

Building samples that stand on their own

A sample stands on its own when a stranger can understand it without a conversation. The most useful version is short and follows a fixed shape. Include:

• the question the work tries to answer, and why someone would care about the answer
• the data used, where it came from, and its known gaps
• the method, stated plainly enough that a reader could repeat it
• the result, with its uncertainty attached rather than hidden
• what the work does not show, and what to check next

Keep the project small enough to finish. One or two complete samples are worth more than ten that stop at a setup step. If the data is public, include the steps that turn it into the result so a reviewer can rerun them. Write the limitations as carefully as the findings. A reviewer who finds a limitation the author named will trust the rest of the work. A reviewer who finds one the author missed will question all of it.

Explaining a title in an interview

When an interviewer asks about a title, describe the work before defending the label. A useful answer covers the scope, the decisions owned and the people involved. It might sound like this: the title was analyst, the work included owning a forecast used by the finance team, the analyst chose its inputs and reported its errors every month, and an engineer reviewed each change to the data pipeline. The title becomes one fact among several, and the interviewer can see what was actually done.

Two common mistakes are worth avoiding. The first is apologizing for a modest title, which suggests the work was minor. The second is criticizing the employer's titling system, which makes the candidate sound difficult to place. State the level of responsibility as plainly as possible, then let the interviewer ask follow-up questions. A good interviewer wants to know how decisions were made, what happened when the data disagreed with a request, and what would be changed now. Those answers are much harder to fake under follow-up than any label.

Practice: rewrite one CV line so a stranger can check it

Read the CV line by line and ask three questions of each entry: what was decided, what was built, and who used it? Lines that answer none of these are usually duties, such as responsible for reporting. Pick one line that depends on the title rather than the work, and write down what a reviewer could check about it in ten minutes: an artifact, a document, a figure that may be shared, or a person who could confirm the scope. If nothing can be named, the line describes a title rather than evidence, and it should be rewritten.

Then build one small sample that would support it. Set a fixed scope, such as a two-week limit and a public dataset, and write the result in the shape described above. Ask a colleague who knows nothing about the project to read it. Their first question shows where the sample depends on something that was never written down. Fix that gap, then decide whether the sample says what the title was meant to say. If it does, the label has become evidence. If it does not, the title was carrying more than it deserved.