Role design: how to hire for alignment, not just "evaluation"

Step 1Start with a clear role design

A role is not a line on the org chart. It's a function that appears when the business changes shape or takes on something new — and the first job is to name the problem you're solving and the gap you're closing with this hire. Skip that and you spend the whole search playing catch-up: something is always slightly off, and you don't know why.

Role design is an internal document — a hiring strategy, not a job advert. But it's also where the advert, the interview questions and the first-90-days plan all come from, so it pays for itself several times over. Before you write a single interview question, answer four things with the hiring manager:

• What problems should this person solve?
• How will you know they're moving in the right direction?
• What experience is actually needed to handle those challenges?
• What soft skills are required for this team — and this stage of the company?

A clear, well-thought-through role design is the single biggest lever: it reduces bias and improves decisions, because you're measuring against a defined target instead of a gut feeling — and feelings are the least reliable partner you can have in a business decision.

One detail people underestimate: strong candidates still read job descriptions, and they compare yours against the others in their inbox. When they spot generic, templated, obviously-AI-generated copy, the best specialists quietly move you to the bottom of the pile and answer the roles where they could actually hear the hiring manager's voice. A designed role is what gives the advert that voice.

Four parts of a designed role

In our hiring-managers course I break role design into four parts. Together they turn a generic job description into a real internal brief — the difference between hoping the right person shows up and going to find them on purpose.

1. The business task. Define the role by the measurable result it must produce — for example, "bring turnover down from 40% to 15% in six months" — not a list of duties. There's a real difference between a function (what someone does every day) and a task (why they do it): "call clients" is a function; "deliver a steady flow of qualified leads" is the task. Every important task can be stated as a measurable outcome, and if you find yourself writing words like support or participate in, you've drifted back into process. If you haven't framed the task as a result, you've hired someone for a process — and a process can't be measured, which means it can't be managed. A quick discipline that helps: for each task, answer four questions — what must they create, fix or improve; by when; with what resources; and what can they actually influence (where does their authority start and stop). The simplest test of all is the honest one: "what am I really paying this person for?"

One more habit worth building here: treat every new opening as a mini internal audit rather than a copy-paste of the last person's job. The market a role was written for a year ago may not exist now; sometimes the audit shows the work can be redistributed and you don't need the hire at all. And while you're at it, draw the boundaries of responsibility clearly — it's the cheapest way to avoid the turf wars and "grey-zone" tasks that nobody owns.

2. The missing link. Look at the team you already have and hire the complement it lacks — not another copy of what's already there. There's a persistent myth that you want a team of stars; but if you already have five brilliant idea-generators, the sixth doesn't help — you need the operator who can turn those ideas into shipped work. A team is a jigsaw, not a box of identical pieces: it needs a strategist and someone who runs the day-to-day. Designing around the gap is what keeps a team balanced instead of lopsided, and it's where most "great CV, wrong hire" decisions go wrong.

3. The context. A candidate never succeeds in a vacuum — the real question is which "aquarium" you're putting them in. The same person, in the same function, can be excellent at company A and fail completely at company B if the environment doesn't fit. So spell out the real conditions and check the fit honestly on three axes:

• Stage and tempo. Are you a startup where priorities shift weekly and there are fires to put out, or a well-run machine where the processes are written down and you mainly need hands? A corporate high-achiever used to an army of resources behind them often struggles in early-stage chaos — and a lifelong startup operator may chafe against a regulated, by-the-book environment.
• Leadership style. There are no right answers here, only honest ones. If you're a daily-standup, close-contact manager, someone who needs full autonomy will grind against you; if you only want to be approached with a problem and a proposed solution, someone who checks in constantly will frustrate you. Match the role to how you actually lead, not how you wish you led.
• Autonomy. Autonomy is an expensive commodity on the market, so decide what the role genuinely needs. Roughly three levels: hands (clear instructions, follow them), process (you say what, they decide how and by when), and strategy (they tell you what needs doing to hit the result). Everyone says they want an autonomous strategist — be honest about whether you need one and whether you're set up to support one.

And above all, be honest in the description itself. The most damaging move is dressing the role up — promising hard problems or a big upcoming project that isn't really there — to land a senior hire. In our experience roughly nine out of ten people hired onto challenges that don't exist leave within three months. You lose the specialist, you lose the time, and you're back at zero.

4. A task-fit profile. Only now do you write the competency profile — and keep it to the hard skills the core task actually needs. Separate the critical skills, without which the person simply can't do the job, from the desired ones — the nice-to-haves you could teach quickly if everything else fits. Over-specifying makes you overpay for knowledge the role will never use and narrows your shortlist for no reason (insisting on a banking background for an engineer when a strong candidate from another demanding domain would do just as well). We don't hire the "ideal" candidate; we hire the one who fits the task.

One trap runs through all four parts: the mirror trap. We subconsciously look for people like ourselves, and that quietly builds an unbalanced team. If you're a "chaos" leader you specifically need a "structure" person — they may irritate you with their precision, and they're exactly the missing piece that makes the team durable. The more diverse the team — in experience, style and background — the more effective it is. You're assembling different parts that fit together, not making clones.

Step 2Decide on the tools

Once the role is designed, the assessment almost writes itself — the interview questions fall straight out of the brief, because you already know which problems you're testing for and which experience is relevant. You're no longer wondering what to ask; you're checking specific things against a defined target. Choose how you'll assess deliberately:

• Interview questions mapped to the task — built from the role design, so each one probes whether the candidate has actually faced these problems and wants to solve them.
• References — used on purpose to verify the few things that matter, not run as a formality.
• Written communication — how someone frames an idea in an email often tells you more than a polished interview answer.

Assessment should be structured, but still human. Structure gives you a consistent bar and lets you model how the candidate would actually work inside your team; the human part is what keeps you from reducing a person to a score. And use the same criteria twice — first to judge the answers in the interview, then as the measurable plan for the new hire's first three months, which takes the pressure off them and tells them they were expected and prepared for.

Step 3Understand motivation

This is the only way to see whether trajectories are aligned: the company strategy → the role itself → and the candidate's ambition. Picture buying a brand-new car and filling the tank with water — it doesn't matter how good the machine is, it won't move. Motivation is the fuel of a role, and the biggest managerial trap is assuming everyone runs on the same fuel: money. Increasingly, for strong candidates, money isn't first or even second — it's something else, and your job is to align that personal deficit with what the role can genuinely offer.

In practice candidates cluster into three motivational types, and the role has to match the type:

• Professional seekers — driven by hard, interesting problems. Give them a real challenge and they'll roll up their sleeves; but once the work turns to routine maintenance, they disengage. Be honest about whether you'll have a next mountain for them, or whether the role ends when the first one is climbed.
• Careerists — driven by advancement, scope and title; the line in the CV matters. They'll commit to a clear step up, but the climb never stops: you need explicit progression ("reach X and you lead the department"), or they'll go find the next rung somewhere else.
• Ideological candidates — the hardest type to satisfy but the longest to stay. They're driven by the product, the mission and the values; they want work that genuinely changes lives. If you're building something that matters, they'll stay for years — so ask honestly whether this role actually offers that.

Motivation has to be synchronous with the role's challenges. Someone looking to "sit out a downturn" dropped into a transformation, or a process-minded operator handed an open-ended build, is a mismatch you'll pay for later — however strong the CV. Get the fuel right and everything you designed in the first two steps finally clicks into one picture: context, hard skills, soft skills and motivation, all pointing at the same business task.

A clear, well-thought-through role design reduces bias and improves decisions. "Evaluating" people comes last — and it's the easy part once you know exactly what alignment looks like.

We're preparing a full course for hiring managers on how to build and scale teams thoughtfully — role design is the first module. A preview is on our Hiring Bootcamp page.