Hiring guide

How to Brief a Recruitment Agency on a Technical Role

Hiring for this role? We’ll benchmark it for your stage and send you the detail, free. Get a benchmark →

Most poor shortlists are decided in the first conversation. A hiring manager forwards a job description, the agency searches against its keywords, and two weeks later everyone is disappointed by candidates who match the document and not the job. A good brief takes under an hour and changes everything that follows. This is what to put in it, from the side of the table that receives hundreds of them.

Start with the problem, not the job description

The most useful sentence in any brief is why the role exists now. “Our payments service cannot keep up with transaction volume and nobody on the team has scaled one before” tells a recruiter more than a page of duties. It points to the companies where the right people have done that work, the questions to ask them, and the story that will make them interested.

Follow it with what the person will actually be doing in their first six months. Concrete work, such as owning a migration, building the first data platform or taking over a team, lets the recruiter test candidates against real situations rather than a list of technologies. If the job description still needs work, our guide to writing a job description engineers respond to and the free job description checker are a good place to start before the call.

Separate the must-haves from the wish list

Most technical job descriptions list ten requirements. Usually three or four genuinely rule someone out; the rest are preferences. Say which is which. “Production experience with a distributed system at scale” is a must-have; “Kafka” may only be the tool you happen to use, and an engineer who has run a different event-streaming platform will learn it quickly.

This matters more than any other part of the brief, because a recruiter working to a ten-item list filters out the strongest passive candidates, who rarely tick every box and have no reason to apply for a role that looks as though it wants someone else.

Give the real pay range

Share the range you will actually approve, including any flexibility for an exceptional candidate, and say how equity and bonus work. A recruiter who has to guess the budget either wastes your interview slots on people you cannot afford or screens out people who would have accepted. If you are not sure the range is competitive, check it against our salary benchmarks or the UK tech salary statistics before the search starts, not halfway through it.

Explain why someone good would move

Strong engineers are usually employed and comfortable. The recruiter’s first message has to give them a reason to reply, and only you can supply it: the technical problem, the team they would join, the funding position, the flexibility on working pattern, the person they would report to. Be honest about the drawbacks as well. A recruiter who knows the role involves on-call duty or a difficult legacy codebase can find people who are energised by that, instead of losing candidates at final stage when it comes out.

Fix the process before the first CV arrives

Agree the interview stages, who runs each one, and the dates those people are free. Commit to feedback within a day or two of each interview. Most technical hires that fail late fail on process, not on candidate quality: a strong engineer with two other offers will not wait a fortnight for a second-round slot. Our article on an engineering hiring process that wins offers sets out a process that holds up under competition.

Agree the terms in writing

The commercial terms belong in the briefing stage, not after the first interview. In Great Britain, the Conduct of Employment Agencies and Employment Businesses Regulations 2003 already require an agency to agree its terms with a hirer before it first provides services, including how its fee is calculated. Read them: the fee basis, the rebate period if a hire leaves early, and whether the search is exclusive. If you are deciding between models, our guide to recruitment models compares contingent, retained and embedded recruitment.

The brief is also where to settle the wording of any advert. The Equality and Human Rights Commission’s guidance on discriminatory adverts applies to employers and agencies alike, and phrases such as “young, dynamic team” create risk for both.

Brief one or two agencies, properly

It is tempting to send a role to every agency that calls. On contingent terms that usually produces the opposite of what you want: each agency works the role less hard, the same candidates arrive from several directions, and the market concludes the role is hard to fill. One or two agencies you have briefed properly, and who know you will give them feedback, will cover the market better. Our guide on how to choose a tech recruitment agency covers what to look for.

How we take a brief

At OpenSource the founders take the brief themselves, and one of us was a software developer, so the conversation goes into the technical substance of the role rather than stopping at the job title. If you are about to hire for a technical, product or data role, whether in London or remotely, tell us about the role and we will start with the questions above.

FAQ

Frequently asked questions

What should a brief to a recruitment agency include?

The problem the hire is there to solve, the work they will do in their first six months, the three or four requirements that genuinely rule people out, the pay range you will actually approve, the interview process with named interviewers and dates, the reasons a strong candidate would move, and the agreed terms. A job description alone is not a brief.

How long should a recruitment brief take?

A proper briefing call usually takes between half an hour and an hour, ideally with the hiring manager rather than only HR or talent. That hour decides the quality of every shortlist that follows, so it is the cheapest time in the whole hire.

Should I tell the agency the salary budget?

Yes, as a range you would genuinely sign off. A recruiter who does not know the budget will either waste your interview slots on people you cannot afford or screen out strong candidates who would have accepted. If you are unsure what the market pays, benchmark it before the brief rather than during the search.

How many agencies should I brief on one role?

For most technical roles, one or two that you trust. Briefing many agencies on contingent terms usually means each of them works the role less hard, the same candidates reach you more than once, and the market hears that the role is hard to fill.

Ready to build your team?

Tell us what you’re hiring for and we’ll come back with a plan, and usually a technically screened shortlist faster than you’d expect.