Most slow searches are slow because the brief was vague.

Before you advertise or call an agency, half an hour spent scoping the role properly saves weeks later. Here's what that half hour should cover.

Why it matters

A job title is not a brief.

“Senior cloud engineer” describes a dozen different people. One of them migrates on-premises workloads to Azure with Terraform. Another runs a Kubernetes platform for internal teams. Another is really a network engineer who learned AWS. All three can legitimately hold the title, and only one of them is the person you need.

When a brief stays at the title level, the vagueness doesn’t disappear — it gets pushed into your interview loop, where it costs your senior engineers their time instead.

The half hour

Four questions worth answering before you search

  1. What must this person deliver in their first 90 days?

    Write the outcome, not the duties. “Migrate the remaining on-premises workloads to Azure” tells a recruiter far more than “manage cloud infrastructure”, and it gives candidates something real to react to.

  2. Which skills does that outcome actually require?

    Split them into must-have and nice-to-have, and be ruthless. If everything is a must-have, nothing is, and your shortlist shrinks to people who look good on paper rather than people who can do the work. Name the stack and the versions.

  3. What are the real constraints?

    Budget range, on-site days, start date, notice periods you can absorb, clearance or right-to-work requirements. These decide who is reachable. Leaving them vague doesn’t widen the field — it just moves the disappointment later.

  4. Who decides, and how fast can they meet?

    Agree the interview panel and the decision-maker before the search starts. The most common reason a good candidate is lost is not money — it is a second-round slot three weeks out.

What good looks like

A brief we can act on immediately

You don’t need a document. A few sentences covering the outcome, the three skills that genuinely matter, the budget range, the on-site expectation and who interviews is enough for a consultant to start searching the same day — and enough for us to tell you honestly if the role as written is going to be hard to fill at that budget.

That last part matters more than it sounds. Being told in week one that a salary is under-market is useful. Finding out in week six, when a candidate declines, is expensive.

Scoping a role, answered

How long should a brief take to put together?
A focused half hour with the hiring manager is usually enough. The point is not length — it is deciding the few things that are genuinely non-negotiable, and being honest that the rest are not.
What if we are not sure what we need yet?
Say so. A brief that admits uncertainty is far more useful than one that lists twelve must-haves nobody has prioritised. We will work through the scope with you before the search starts.
What happens after we send a brief?
Your consultant replies within 1 business day (Mon–Fri, AEST), and we aim to have a brief call within 2 business days. First shortlist targets are 5 business days for contract and 10 for permanent.

Tell us the role.

Your consultant replies within 1 business day.

  • No cost to briefNothing to brief us or to receive a shortlist.
  • Reply within 1 business dayMonday to Friday, AEST, from the consultant who runs your search.
  • Pay only when someone startsPlacement fee payable only when the candidate starts. Terms and fee confirmed in writing before the search begins.

Step 1 of 2

The role
Permanent, contract, or contract-to-hire?