Hiring guide

What a Technical Recruiter Actually Does

Most recruiters who call themselves technical are not. They work technical roles, which is a different thing. The test is simple: can the person running your search assess an engineer without you in the room? If not, you are buying a sourcing service with a technical label on it. This is what the job involves when the label is earned.

Taking a brief that describes the engineering

A generalist takes a job title and a list of keywords. A technical recruiter takes the problem: what the team is building, what is slow or broken, which decisions the new hire will own, and where the current engineers run out of depth. From that they can tell you whether the role is really senior or staff level, whether the stack you have written down is the stack that matters, and whether the salary band buys the person you have described. That conversation often changes the role before the search starts, which is where most of the value sits.

Reaching people who are not applying

The strongest engineers are passive candidates. They are employed, not on job boards, and they ignore messages that read like a template. A technical recruiter can describe your work in the engineer’s own terms, which is the only approach that gets a reply from someone who has plenty of options. It also means the search covers the market, not the applicants.

The screen, which is the whole point

Technical screening is the job that separates the two kinds of recruiter. Done properly it is a conversation with someone who has done the work: the systems the candidate built and owned, the trade-offs they made and why, how they debug under pressure, how they work with product and with other engineers. The output is a written summary that arrives with the CV, so your first interview starts from evidence rather than from a keyword match. Our guide to assessing senior engineers in interviews covers what the conversation looks like from the hiring side.

At OpenSource that screen is run by a founder who was a software developer, which is the reason the business exists. It is also why we turn down roles outside technology, product and data: we cannot screen them to the same standard, and a screen we cannot stand behind is worse than none.

Reading the market for you

Because a technical recruiter speaks to engineers every day, they know what a senior backend engineer in London is accepting this month, which companies are counter-offering hard, and which stacks have a thin pool. That knowledge is what turns a salary band into an offer that lands. Our published salary benchmarks are the written-down version; the recruiter’s job is to apply them to your specific role.

Closing, which is where most searches fail

Offer accepted is not the end. The counter-offer arrives in the days after a resignation, and a candidate who has not been kept close through their notice period is lost at that point. A technical recruiter manages the offer, the resignation, the counter-offer conversation and the weeks until the start date, because they understand what the candidate is weighing and can speak to it honestly.

Five questions that show whether yours is one

  1. Who interviews my candidates before I see them, and what do they ask?
  2. Can I see a sample of the written screen that comes with a CV?
  3. In my stack, what separates a senior engineer from a staff engineer?
  4. Which three roles like mine have you filled this year, and how long did each take?
  5. Which briefs have you turned down, and why?

A technical recruiter answers all five in specifics. A generalist reaches for adjectives by the second.

Agency, employment business or recruiter

The words get mixed up, and the distinction matters for your contract. Under the UK rules an employment agency introduces people for direct employment with you, while an employment business supplies contractors it employs and pays itself. A technical recruiter is the person inside either who does the work. When you are choosing a tech recruitment agency, the question is not which category it falls into but who, specifically, will run your search.

Where we fit

OpenSource is a founder-led tech recruitment agency in London. The founders take the brief, run the search and screen every candidate themselves; there is no handover to a junior consultant. If you are hiring software engineers and want the first technical judgement made before your team spends an hour on an interview, tell us the role.

The agency and employment business definitions summarise the UK government’s published guidance; they are not legal advice.

FAQ

Frequently asked questions

What does a technical recruiter do?

A technical recruiter finds, assesses and closes engineers, product and data people for a company, and the word technical means they can assess the work, not only match words on a CV. In practice that is four jobs: taking a brief that describes the actual engineering problem, reaching the engineers who are not applying anywhere, screening them on what they have built and how they think, and managing the offer and notice period through to the start date.

What is the difference between a technical recruiter and a generalist recruiter?

A generalist recruiter matches CVs to a job specification and relies on the hiring manager for every technical judgement. A technical recruiter makes the first technical judgement themselves, so the hiring manager interviews fewer, better candidates. The difference shows up in the shortlist: a generalist sends ten CVs with keywords, a technical recruiter sends three people with a written note on what each has actually done.

How can I tell whether a recruiter is genuinely technical?

Ask who interviews the candidate before you see them and what they ask. Ask for a sample of the written screen that arrives with a CV. Ask them to describe the difference between a senior and a staff engineer in your stack, or why a Node.js shop might struggle to hire from a Java background. A technical recruiter answers in specifics; a generalist answers in adjectives.

Is a technical recruiter the same as a recruitment agency?

No. An agency is the business; a technical recruiter is the person doing the work, and many agencies employ none. Under UK law an employment agency introduces people for direct employment with you, while an employment business supplies contractors it employs itself. Either can be technical or not. What matters is who runs your search and whether they can assess an engineer.

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.