Here's a version of a hire I'd bet plenty of agency owners have lived through. A mid-sized marketing agency has twelve working days to fix a client's tracking before a product launch. Conversions are double-counting across three ad platforms, and nobody on the team has built a server-side tagging setup before. They're good people. They're also generalists, and this isn't a general problem.
So they post a role called Digital Marketing Expert. A pile of applications arrives by the weekend. A handful mention Google Tag Manager. Almost none have debugged a server container under deadline. The team loses four days reading CVs for a job they never actually described.
I don't think that agency needed a bigger pool. It needed a sharper question. When generalists aren't enough, the fix usually isn't a better job board or a faster recruiter. It's a brief that names the problem so precisely that the right specialist recognises it, and the wrong ones rule themselves out.
To hire specialized experts, define the exact problem before you define the person. Separate the one or two skills the work can't happen without from the ones that would merely be nice. Write a scoped brief with deliverables, timeline and budget, source through referrals and targeted search, and check ability with paid, real work.
Where a good generalist runs out of road
Generalists are the reason most small teams function. The person who can write a landing page, fix a spreadsheet formula and calm down an anxious client on the same afternoon is worth a lot. I'd never argue against hiring them.
But there's a point where breadth stops helping. You've probably reached it when the cost of getting the work wrong is high, the knowledge takes years to build, and nobody on your team can tell a good answer from a confident one.
That last one is the tell. If nobody in the room can check the work, you're not hiring an extra pair of hands. You're hiring judgment, and judgment is exactly what a specialist sells.
Define the problem before you define the person
Most hiring briefs I read start with a job title and work backwards. I'd flip that. Start with the thing that's broken, stuck or missing, and write it in plain language someone outside your company would understand.
For the agency above, that sentence is something like: our conversion data double-counts across Meta, Google Ads and TikTok, and we need a working server-side setup plus handover notes before the launch on the 14th. That one line does more screening than a page of requirements. A tracking specialist reads it and knows in ten seconds whether it's their kind of problem.
Essential skills versus preferred skills
Once the problem is written down, split the skills into two columns. Essential means the work fails without it. Preferred means it would help, but a strong specialist could pick it up or work around it. Be strict. Every preferred skill you sneak into the essential column shrinks your pool without improving the match.
| Brief field | Vague version | Scoped version |
|---|---|---|
| Title | Digital marketing expert | Server-side tracking specialist, contract |
| Problem | Improve our analytics | Conversions double-count across three ad platforms |
| Deliverable | Better data | Working server container, test log, handover notes |
| Timeline | ASAP | 12 working days, launch on the 14th |
| Budget | Competitive | Fixed project fee, agreed before work starts |
| Success | Client is happy | Platform totals match backend orders within an agreed margin |
An expert in what, exactly?
Legal work provides a useful example of why “expert” is not a single category. Johnny Gardner Law's current public materials describe using or working with specialists in areas including breath-testing technology, Standardized Field Sobriety Tests, toxicology, chemical analysis, accident reconstruction and medical questions in DUI matters.
Someone researching a Grand Strand DUI lawyer is looking for legal representation, but the underlying case may involve technical questions that call for expertise outside the lawyer's own discipline. A toxicologist and an accident reconstructionist are both experts. Hand one the other's question and you'd get a careful, credentialed and useless answer.
I like this example because lawyers are already specialists, and they still bring in outside expertise when a question sits beyond their own field. That isn't a gap in the firm. It's the firm defining the problem properly. The broader hiring lesson is simple:
Do not hire a generic expert. Define the problem first, then identify the expertise that actually matches it.
It holds just as well for a startup that needs a fractional finance lead for a funding round, or a creative agency that needs a motion designer who has actually worked in 3D. Our specialist recruitment section goes further into writing briefs like these.
Where specialists actually come from
Broad job ads are built for volume. That's fine for roles with a large, well-understood talent pool. For narrow expertise they mostly produce noise, and the people you want often aren't reading job boards at all.
The headline of a recent RecruitingDaily piece, Recruiter Intentions vs. Job Seeker Realities, names a gap that shows up constantly in specialist hiring: what the hiring side assumes people want isn't always what those people say. With specialists the gap is wider, because good ones usually have options.
What tends to work better:
- Referrals from people who've seen the work. Ask peers who hired for a similar problem, not a similar title.
- Targeted headhunting. A short, specific message to ten people who've done this exact work beats a post seen by ten thousand who haven't.
- Professional communities. Specialists gather where their craft is discussed: industry associations, conference speaker lists, open-source projects and portfolio platforms.
- Previous collaborators. The contractor who did good work for you two years ago often knows two or three people who'd be right for this one.
If the work has phases, it's worth planning who comes in when. Our project staffing guides cover that side.
How to check expertise without wasting anyone's time
Specialists interview you as much as you interview them. A four-round process with a long take-home task tells a senior expert that you don't know what you're looking for. A tighter approach:
- Walk through past work. Ask them to talk you through one project that looks like yours: what went wrong, what they'd change and how they knew it was finished.
- Ask how they'd scope your problem. A real specialist will ask questions you didn't think of. That conversation is often the best assessment you'll get.
- Pay for any test. If you want to see them do real work, make it a small, paid piece with a clear end point. An unpaid trial on live client work isn't a hiring test. It's free labor.
- Check references on the problem, not the personality. “Were they easy to work with?” matters less than “Did the thing they built still work six months later?”
Put scope, communication and pay in the first message
The fastest way to lose a good specialist is to stay vague about the parts they care about most. Tell them the deliverable, the timeline, who they'll report to, how often you'll check in and what the budget is. If the budget isn't fixed yet, say so honestly and give a range.
Contract and freelance specialists also need clear terms, and the rules on who counts as an employee differ by country, sometimes by state. In the US, the Department of Labor publishes guidance on employee or contractor classification. In the UK, the off-payroll working rules, often called IR35, apply to many contractor engagements. That's general context, not legal advice, so check the rules where you and the specialist are based. Our contract work section covers the practical side.
And treat the person as a partner on the project, not a part you're slotting in. Specialists talk to each other. How you run one engagement quietly becomes how you're known.