Industry · IT & tech

Recruiting software for IT and tech: how AI sourcing works in tech hiring

For IT and tech, AIcruiters is recruiting software that starts from what the team really needs: a language or platform, the scale of systems someone worked on and the context of the work. It searches broadly across titles and synonyms, ranks every profile against the full vacancy and writes to developers about the actual technical problem, within your approval rules.

A single keyboard key in white and black with an orange edge.

How tight is the Dutch IT market?

51
vacancies per 1,000 jobs in information and communication (Q2 2026)
CBS StatLine 80567ned, provisional
42
vacancies per 1,000 jobs across all sectors (Q2 2026)
CBS StatLine 80567ned, provisional

Where do IT candidates actually leave a trace?

Most IT professionals have a LinkedIn profile, but it is often the least informative place to judge them. The profile says "Software Engineer at a scale-up"; the real signal lives elsewhere. Combine several sources and know what each can and cannot tell you.

LinkedIn: reach, not depth

LinkedIn is where you can contact people and see career paths: employers, tenure, promotions, the move from agency to product company. Skills sections are self-reported and frequently outdated. Treat them as hints to verify.

GitHub, Stack Overflow and technical communities

Public repositories, contributions to open-source projects, answers on Stack Overflow, conference talks and meetup organiser pages show what someone builds and how they reason. Most working developers have little public code because their work sits in private repositories, so an empty GitHub is not a negative signal. Use these sources to strengthen a match, never to exclude someone. Public does not mean free to use for any purpose: the GDPR rules for sourcing still apply.

Which requirements in an IT vacancy are really hard?

Hiring managers tend to list every tool in the current stack. A sourcing strategy needs to know which items rule someone out and which can be learned in weeks.

Requirement
Usually hard
Usually soft
How to handle it
Programming language
Core language of the codebase at senior level
Second language, or a close relative (Kotlin for Java, TypeScript for JavaScript)
Search the language family, rank exact experience higher
Frameworks and libraries
Rarely
Most frameworks within a known language
Treat as ranking signal, not as filter
Cloud and infrastructure
Deep platform work for an SRE or platform role
AWS versus Azure versus GCP for a developer
Ask the manager explicitly; note the answer in the vacancy
Scale and domain
High-traffic or regulated systems when that is the job
Specific industry experience
Look for comparable complexity, not the same sector
Language and location
Dutch for client-facing consultancy; right to work
On-site days, when the team is hybrid
Confirm before outreach, mention it in the message

Where do IT searches typically go wrong?

Tech searches fail less on volume than on vocabulary. The same work carries different names, and the same name covers very different work.

  • Synonyms. Developer, engineer, programmer, ontwikkelaar and consultant can all describe identical work. A search on one title misses most of the market; a Boolean string that covers them all quickly becomes unmanageable.
  • Title inflation. "Senior" after three years at a start-up, "Lead" for a team of two, "Architect" at a consultancy that uses it as a pay grade. Read tenure, scope and system size instead of the title.
  • Keyword stuffing. Profiles that list twenty technologies usually used three of them seriously. Ranking against the full vacancy, with reasons, filters this better than a keyword count.
  • Framework tunnel vision. Rejecting a strong Vue developer for a React vacancy costs you candidates a manager would happily hire.

How AIcruiters' five steps play out for an IT vacancy

Illustrative example (fictional): a mid-level backend developer with Go for a Utrecht-based logistics platform, hybrid, Dutch not required.

Step 01 · Vacancy analysis

The vacancy becomes a search strategy

Hard: production backend experience, Go or a strong background in a comparable compiled language, right to work in the Netherlands. Soft: Kubernetes, logistics domain, event-driven architecture. Titles to map: backend developer, software engineer, Go developer, platform engineer.

A flat lay of paper, black and orange blocks with a magnifying glass: a vacancy broken into search signals.

Step 02 · Market search

Several routes, one deduplicated list

Searches run per title cluster and per language family, including Java and C# developers who moved to Go. Duplicates and profiles outside the region or without backend work are removed.

A black magnifying glass over a stack of cards, one orange card under the lens: searching the market.

Step 03 · Fit ranking

Every profile scored against the full vacancy

A candidate with four years of Go in a high-volume API ranks above a "Senior Go Lead" with one year of Go. Each score shows matching experience, missing requirements and risks such as very short tenures.

Many white spheres narrowing into a single line that ends in one orange sphere: ranking candidates.

Step 04 · Personal outreach

A message about the problem, not the perks

The message names the concrete challenge (for instance, a routing service under peak load) and the stack, and is honest about hybrid days. Your team decides whether messages go out automatically or after approval.

Three white paper planes with an orange one in front: outreach.

Step 05 · Follow-up and handover

Interested developers go to the recruiter

Positive replies arrive with profile, match rationale and the conversation so far, so the recruiter can pick up the technical questions the candidate asked.

A black and an orange cylinder touching end to end: the handover from agent to recruiter.

How do developers want to be approached?

Developers receive a lot of recruiter messages and filter hard. The ones that get answered share a few traits.

  • Specific about the work

    Stack, team size, the problem to solve and what is legacy. "Exciting opportunity" says nothing.

  • Clear on the non-negotiables

    Salary range where you can share it, remote or on-site days, language, contract type. Hiding them wastes both sides' time.

  • Proof you read the profile

    Refer to a real project, repository or career step, not only the current title.

  • Short and easy to decline

    A few sentences and a low-effort next step. Follow up once or twice, then stop.

Read more on writing LinkedIn outreach messages or see how LinkedIn outreach automation keeps this personal at scale.

Questions about tech sourcing with AIcruiters

Does AIcruiters search GitHub or Stack Overflow?

AIcruiters searches the talent sources available in your setup through several search routes. Which sources are used, and under which conditions, is agreed per implementation and covered in the technical and privacy review. Public technical activity is best used to strengthen a match, not to exclude candidates.

Can it tell a real senior developer from an inflated title?

It ranks against tenure, scope and experience described in the profile, and shows the reasoning, including risk factors. A recruiter still judges the edge cases; uncertain profiles can be routed to a person.

Is this useful for IT staffing and secondment, not only permanent hiring?

Yes. The workflow is the same; the criteria include availability, rate expectations and contract type. See AIcruiters for staffing agencies.

Last updated:

Run it on one of your IT vacancies

Bring a real developer or IT vacancy to a 30-minute demo and see the search strategy, ranking and draft outreach AIcruiters produces.

Book a demo on your own vacancy30 minutes · your vacancy · your numbersCalculate the business case