A visa-sponsorable role live for three weeks, forty applications in the inbox, and not one applicant who has done production work with the single skill the job actually turns on. You are a recognised sponsor (erkend referent), the salary sits above the highly skilled migrant threshold, the ad says relocation support in plain English. None of that is what is holding the hire up. This is usually the point where a hiring team starts asking whether to search candidates by skill rather than buy more ad reach.

It is a reasonable question, and the answer is a trade-off rather than a swap. A job post filters passively: it reaches people who are actively looking, in the right week, on the right board, who then read your requirements generously enough to apply. A skill search filters actively, selecting on what a published profile says someone has done, whether or not they are scanning job boards today. Those two populations overlap less than most hiring teams expect.

Most employer-side advice stops at registration. Getting onto the IND register is a defined process with a defined outcome, and the employer guide to getting on the recognised sponsor list covers what the application needs. Writing an ad that international candidates can act on is also solvable, and the job ad fixes that change who applies handle most of it.

Neither of those fixes a thin applicant pool for a narrow skill. If you need someone who has run FPGA timing closure on a shipped product, there may be a few hundred such people in Europe who would consider moving to Eindhoven. Of those, perhaps a handful are reading job boards in any given month. Your ad budget determines how many of that handful see your post. It does not change the size of the handful.

This is where ad spend and sourcing diverge. Doubling impressions on a generalist role genuinely helps, because the qualified population is large and you are mainly competing for attention. Doubling impressions on a specialist role often just buys more unqualified applications, since the people you need were never in the audience being served the ad.

The sponsor list problem employers actually hit next

Count the cost properly before deciding it is cheap.

- Screening time. Forty applications at ten minutes each, including the ones you reject in two minutes and the three you read carefully, is close to a full working day. Repeat that monthly while the role stays open.

- The eligibility re-check. A share of applicants to any sponsorship-flagged role will not qualify under the highly skilled migrant scheme at the salary you have budgeted, and you only discover that after reading the CV. The time-to-hire breakdown for international candidates shows how those weeks accumulate.

- Team cost of the vacancy. The work is being absorbed by someone. That is the number your budget holder understands, and it is usually larger than any sourcing fee.

- Compounding delay. A non-EU hire needs an IND application and a relocation runway after you sign. A month lost in sourcing becomes a month added at the end of the process, not a month quietly absorbed in the middle.

What posting and waiting really costs you is time, measured in the weeks it takes to discover that the right person was never in the audience your ad reached.

Four reasons, none of them about your employer brand.

They are not looking yet. Someone two years into a Dutch contract with a renewal coming up, or an engineer in Bangalore who has started thinking about Europe but has not touched a CV in a year, is reachable without being in any sense a job seeker. Reach out and a conversation is plausible. A job post simply never enters their week.

They filtered you out on sponsorship uncertainty. Candidates have been trained by experience to treat the sponsorship line as aspirational. Many skip anything that does not say it unambiguously, and some skip it even when you do say it, because telling real sponsorship ads from fake ones is genuinely hard from the outside.

They used different words. Your ad says "observability", their profile says "Prometheus, Grafana, OpenTelemetry". Your ad says "data engineering", they call themselves an analytics engineer. Keyword mismatch runs in both directions, which is why the candidate-side guide on the skills recruiters actually search for exists at all.

They never saw it. Boards rank by recency and spend, so a specialist role from a mid-size sponsor with no promoted budget surfaces briefly in the "new" sort and then sinks. How fast sponsorship listings disappear covers that decay in detail.

Why the right candidate often never applies

Searching published candidate profiles inverts the sequence. Instead of writing requirements and hoping the right reader self-identifies, you query the skill and read who comes back.

Three practical differences show up immediately.

You see the population, not only the responders. Suppose a query for your must-have skill returns eleven profiles in the Netherlands and forty across the EU. You now know something your inbox could never tell you: whether the role is hard to fill or merely hard to advertise. Eleven profiles points at rethinking the requirement or widening the location. Forty points at your post being the bottleneck.

You read evidence before you write a message. A profile that lists the skill with context, years, and the kind of product it was used on tells you more than a cover letter written against your ad. You can calibrate the first message to what the person has actually built, which is why targeted outreach converts better than broadcast even at low volume.

Rejection becomes cheap and specific. Skimming thirty profiles against one hard requirement takes a fraction of the time thirty applications take, because you are reading for a single thing and the irrelevant material is not there to wade through.

The limit is equally real. Any international candidate database in the Netherlands contains only the people who chose to publish a profile. That group is self-selected, smaller than the full labour market, and skewed towards people already oriented towards working internationally. For a Dutch-language customer-facing role in Zwolle, a posting on the right channel will probably beat a skill search. For a specialist technical role where the job title varies from company to company, the search usually wins.

If you have sourced before, you know the failure mode: scraped lists, cold mail to addresses nobody handed over, candidates irritated before they finish the first line.

A consent-based search behaves differently, and the mechanics are worth understanding before you plan a campaign around them. The candidate decides to publish a profile, decides which skills and experience appear on it, and decides whether to respond. Name and contact details do not appear in the search results. You see the skills and the shape of the experience, you send an approach, and the identifying details reach you only once the person accepts.

That has consequences for how you write the first message. You cannot address someone by name, so the approach has to persuade on the role alone: the actual work, the salary range, the sponsorship situation stated plainly, the city. Vague outreach gets ignored at a far higher rate when the recipient has given up nothing and loses nothing by declining.

Your pipeline also ends up smaller and warmer. Everyone who accepts has read what you offer and opted in, which is a very different conversation from screening someone who applied to thirty roles that week.

Framing this as posting against sourcing misses the real decision, which is which of the two carries the role while the other supports it.

A visible listing still does work a search cannot. It catches the candidate who is actively looking this week and would have found you anyway. It gives the person you approached somewhere to verify the role is real, which matters a great deal when the first message arrived from a company they have never heard of. In some organisations it also satisfies internal or procedural expectations about advertising a vacancy.

What a sponsored candidate search in the Netherlands adds is a route to the people posting structurally misses. The split most teams land on: keep the listing live for the whole search as the thing people can check and apply to, and treat the skill search as the activity you review weekly. If you are also weighing how much reach to buy, the trade-offs in advertising a job to international candidates sit alongside this rather than against it.

Where the extra budget goes depends on the shape of the gap. Broad skill with many qualified people competing for attention: buy reach. Narrow skill with few qualified people: hire international talent by skill, and put the writing effort into outreach instead of the ad.

A profile that matches your requirement perfectly can still belong to someone you cannot hire at the budget you have.

The highly skilled migrant route has a salary criterion that depends on age bracket, is indexed, and changes on 1 January. If your band sits close to the line, brilliant search results will not rescue it, and the 2027 threshold changes and what they cost employers are worth reading before you commit to a salary band for a 2027 start. Check the current figures on the IND page rather than any number you remember from last year.

Recognition status, the fee structure, the reporting duties that come with sponsorship, and the diploma or regulated-profession questions attached to certain roles all sit outside anything a skill search touches. So does the start-date arithmetic: permit decision time, relocation, notice periods in the candidate's current country, BSN, housing. Sourcing shortens the "find the person" phase and leaves the rest of the timeline where it was.

Being honest about the ordering saves disappointment later. Settle the salary band and your sponsorship capacity before you spend effort hunting for the skill.

Run it as an experiment with a number at the end, not as a vendor evaluation.

- Week 1: define the one requirement you will not compromise on. One skill, stated the way practitioners state it rather than the way your job description states it. Write down the acceptable adjacent skills separately.

- Week 1: baseline your current funnel. Applications received, how many passed the hard requirement, how many passed the salary check. If the first number is forty and the second is two, you have your comparison point.

- Weeks 2 and 3: search and approach, at a volume you can actually follow up. Twenty well-written approaches beat eighty templated ones, especially when the recipient is anonymous and judging you entirely on the role description.

- Week 4: compare on accepted conversations, not on sends. What matters is how many people with the hard requirement agreed to talk, measured against the two who came through the posting.

- Throughout: keep the listing live. The people you approach will look you up, and a clear, current vacancy is what you want them to find.

If the search produces three qualified conversations in a month where the posting produced two in three weeks, you have learned something real about which channel this role needs. If it produces none, the requirement is rarer than you thought, and the next decision is about the requirement rather than the channel.

Talent Search (launching) is built for the moment described here: coming soon, you will be able to search the profiles candidates choose to publish, by skills, with name and contact details shared only when the candidate accepts, and the pricing page is where it will appear once it is live. Until then, a clear and honest vacancy on visa-sponsored jobs is still the first thing anyone you approach will check before replying.