Why different roles need different hiring journeys

Most recruitment systems are configured once, around the role the organisation hires most often, and then applied to everything. It works acceptably for that role and poorly for the rest, and the cost shows up as time to hire, candidate drop-off, and managers building their own arrangements in a spreadsheet.

The differences are structural, not cosmetic.

A senior professional hire and a bulk operational intake are not the same process with different volumes. One needs a small number of long assessments, several stakeholders and a negotiation at the end. The other needs a high-throughput screen, a compliance check that must not be skipped, and a mobilisation date that everything else is measured against.

Forcing both through one stage model means one of them carries stages that add nothing, and the other is missing stages it needs. People then work around the system, which is where the visibility goes.

Volume roles are governed by the bottleneck, not by the stages.

When a project needs forty people ready on a date, the pipeline is not the interesting part. The bottleneck is documentation, medicals, visas, inductions, or whatever the local equivalent is, and it has a lead time nobody can compress on the day.

A process designed for this starts the compliance clock as early as it legally can, tracks readiness as a first-class state rather than as a note on a record, and reports on the constraint rather than on the funnel. Counting applications is comfortable and beside the point.

Specialist roles are governed by candidate patience.

A scarce candidate with options will not sit through five rounds scheduled a fortnight apart. Every gap between stages is a chance for another offer to arrive first, and the delay is almost never assessment time; it is calendar time waiting for an interviewer.

The fixes are unglamorous: fewer stages with more in each, self-scheduling so the candidate books a slot instead of waiting for an email, panel availability agreed before the vacancy opens, and a decision deadline that is actually enforced.

Internal moves need a different shape again.

The candidate already works here, so there is a manager who will lose them, a colleague who will hear about it, and a record of performance that may or may not be appropriate to use. Rejection has consequences that an external rejection does not, because the person is still there on Monday.

That argues for explicit consent rules about when a current manager is told, a documented basis for the decision, and feedback that is genuinely usable. It also argues for measuring internal mobility as a fairness question rather than only as a filling-vacancies one.

Agency-sourced hiring is a supplier process wearing recruitment clothes.

When candidates arrive through agencies, the important mechanics are submission rules, duplicate ownership, response times, fee terms and performance over time. None of those are stages in a candidate pipeline, and trying to model them as such is why so many organisations run their agency relationship in email.

Give it its own surface: what each agency has been invited to, what they submitted, what happened, and how they compare. Then the conversation at renewal is about evidence.

Different does not mean bespoke.

The argument for role-specific journeys is often resisted because it sounds like a maintenance problem, and it would be if each were coded. It is not a maintenance problem when a stage model is configuration and the workflow behind it is drawn rather than written.

The practical shape is a small number of journeys, four or five, each matched to a hiring pattern the organisation genuinely repeats, with the same underlying records and reporting beneath all of them. That is enough variation to fit reality and few enough to keep in your head.

What to measure.

Time to hire is a poor single number because it averages across patterns that should not be averaged. Measure per journey, and measure the wait rather than the work: time between stages, time waiting for an interviewer, time waiting for an approval. Those are the numbers somebody can act on this week.