The Job Profile: How to Define It With Data, Not a Template

Almost every search starts with a job description copied from the last one. Two lines changed. Then the team interviews against that description. And in the end decides against something else that was never written down.

That gap between what was published and what was used is where most searches get lost.

Two documents, not one

The job description faces outward. It attracts candidates, explains the role, and sells the company. It can be aspirational, and usually is.

The job profile faces inward. It is what each finalist gets compared against, and it should not contain a single word you cannot evaluate.

When only the first exists, every interviewer builds the second in their head. Five interviewers, five different profiles. And a meeting that argues about people when it is really arguing about criteria.

What a usable profile contains

The three or four things this person has to solve in year one. Not the ten responsibilities. The concrete problems. A role is defined by what needs fixing, not by what needs administering.

The competencies, with a level and an anchor. Not “teamwork.” That cannot be evaluated. What behavior you expect to see, and what weak looks like next to good.

The traits the context demands. An ambiguous role asks for something different than a structured one. That difference is personality, not experience. It is the part almost never written down and almost always decisive.

What this seat demands at this company. The same title means different things at two companies. An operations manager with three reports and their own budget looks nothing like one with twenty and no signing authority.

What does not matter. The requirements dragged along from the template that nobody will evaluate. Removing them widens the pool and shortens the search.

How to fill in the context part

One question organizes the exercise. It belongs to the manager who will receive the person.

“Who was the last person who did really well in a similar seat, and what did they have?” Then the inverse. “Who did not work out, and what was missing?”

The answers are almost never about technical experience. They are about how the person moved through ambiguity, how hard they pushed, how much they asked. That is the real profile. It was in the manager’s head, unwritten.

The mistake of anchoring on the resume

Years of experience and the previous employer’s name are the two most used filters. Also two of the weakest. They filter on what the person had the opportunity to do. That depends on where they happened to be, not only on what they can do.

It is not that they say nothing. They say less than they get asked to say. Set as hard requirements, they screen out profiles that would solve the problem.

How we do it

Talen.to builds the role profile as a measurable object, not a piece of text. Each role carries an expected range across the OCEAN+ dimensions and competencies with levels. Every candidate gets compared against that.

The reference profiles are open in the roles guide, with variants by company size. Size tends to change more than the title does. A startup product manager and an enterprise product manager share a name and not much else.

That reference profile is a starting point, not a truth. The version that works is the one your team adjusts against its own context and its own values.

A one-hour exercise

If you are opening a search this week, sit down for an hour with the manager and pull out four things.

The three problems of year one. The four competencies needed to solve them, with written anchors. What the context looks like in terms of ambiguity, pressure, and autonomy. And which requirements from the old template you are going to ignore.

With that you have a profile to compare against. Without it, you compare against the impression of whoever speaks loudest in the room.