🇩🇪 +49 89 62826175 🇦🇹 +43 1 4420022
|
kontakt@indivhr.com

InMail to developers: What really works (and what doesn't)

candidate matching recruiting

1. Warum deine InMail keine Chance hat – auch wenn sie „nett" klingt

„Hi , dein Profil ist mir aufgefallen…" InMail template developer

Almost every recruiter starts like this. And almost every developer recognises that this message has been sent hundreds of times. The real problem here is that you are playing in an oversaturated market on LinkedIn - and advertising a product (your job) that nobody was looking for.

What many underestimate: Gute Entwickler:innen brauchen kein Jobangebot. Sie haben Jobs. Oft mehrere. Und sie kennen die gängigen InMail-Muster bis ins Detail. Sie wissen, wann ihr Name automatisiert eingefügt wurde, wie sich generierte Texte lesen und dass du „gerade auf der Suche" bist.

So if you send standardised texts, you don't come across as friendly - you come across as interchangeable.

Statements such as:

  • „Ich habe dein Profil gelesen…" (wenn du's nicht wirklich hast)

  • „Wir suchen Verstärkung fĂĽr unser agiles Team…" (was soll das heiĂźen?)

  • „Bei Interesse sende mir gern deinen CV" (klassischer Push – null Pull)

Practical problem: Many recruiting teams measure the success of InMails by the number of messages sent - not by the quality of the responses. This leads to mass emails that technically orientated candidates immediately ignore.

2. psychology + context: How developers think about InMails

Developers are analytical. They are used to optimising systems, ignoring irrelevant information - and only reacting when something needs to be done. technically or humanly interesting is.

What many recruiters overlook: InMail template developer
Die Zielgruppe denkt nicht in „Jobs" – sondern in System architectures, Freedom of choice, Tech-Stability, Team quality, Product value.

This means:

  • Wenn du nur „Frontend Developer" schreibst, ist das fĂĽr sie inhaltlich leer.

  • Wenn du aber „React 18, Vite, Storybook, Design Tokens" erwähnst – wird es greifbar.

  • If you explain, why this team has switched to micro front endsyou create relevance.

In addition, the attitude towards InMails is characterised by mistrust:
Many have had bad experiences. Recruiters who didn't understand stack terms. Calls that took time. Promises that were never honoured. So trust is not there - it has to be built up in the text.

What do developers think about recruiting messages on LinkedIn?
In short: critical, selective, data-driven. Developers don't respond to niceness - they respond to relevance. If the first two sentences of your InMail don't make a concrete contribution to their world, it won't be read. And this is not a question of text length, but of Contextual understanding.

3. structure that triggers: the 4-phase tactic for developer InMails

Good InMails are not job adverts. They don't follow advertising logic - but a thought structure. Developers are rational, fast, focussed. A good message must reflect this.

Here the 4-phase modelthat we use in active sourcing at indivHR - with a constant response rate of over 25-30 % for sourced devs:

1. Context trigger InMail template developer

Beginne nicht mit „Ich bin Recruiter" – beginne mit their world:

  • „Ich bin auf dein Profil gestoĂźen, als ich nach Go-Entwicklern mit Kubernetes-Erfahrung gesucht habe."

  • „Deine Migration von AngularJS auf React 18 mit TypeScript fand ich spannend – darum schreibe ich dir."

Goal: Technical relevance and sourcing transparency. No small talk.

2. Value proposition

No job advertisement! But rather: What is there to learn, to build, to decide?

  • „Es geht um ein Team, das gerade seine CI/CD komplett auf GitHub Actions umstellt – ohne klassische QA-Rolle."

  • „Das Produkt läuft bei mehreren Millionen Usern. Performance-Optimierung ist nicht „nice to have", sondern Hauptfokus."

Goal: Address intrinsic motivation - not extrinsic benefits.

3. Serious invitation

Show that you are not writing to the masses - but that you understand what makes decision-makers tick:

  • „Wenn du Lust hast, schauen wir uns gemeinsam an, ob das fachlich fĂĽr dich Sinn macht – kein CV nötig."

  • „Ich bin technisch fit, wir können also auch konkret ĂĽber Stack, Roadmap oder Codearchitektur sprechen."

Objective: To resolve eye level and asymmetry.

4. Human Touch

Short, not slimy:

  • „Falls's fĂĽr dich nicht passt – gar kein Thema. Danke, dass du's gelesen hast."

Goal: Take the pressure off. This makes you look more prono less.

How do I write a good InMail to developers on LinkedIn?
With technical relevance, personal reference, clear structure - and without empty phrases. And: readable in under 100 seconds.

4. Do's & Don'ts: Was du technisch, semantisch und menschlich vermeiden musst

❌ Don'ts – diese Fehler killen deine Response-Rate:

  • đź”» Standardfloskeln („spannende Aufgaben", „dynamisches Team")

  • đź”» 6-line text blocks without paragraphs

  • đź”» Bitten um den Lebenslauf („Bitte schick mir deinen CV" = 2010)

  • đź”» „Wir sind ein international erfolgreiches Unternehmen…" (irrelevant fĂĽr Devs)

  • đź”» Recruiting-Jargon („Hands-on-Mentalität", „Fullstack mit Leidenschaft")

✅ Do's – so erreichst du Tech-Menschen auf Augenhöhe:

  • âś… Name specific tools, technologies, architecture topics

  • âś… Transparency: why you are writing to them and how you have categorised their profile

  • âś… Technische Tiefe anbieten („Wir können auch gern ĂĽber die Codebasis sprechen")

  • âś… „Kein CV nötig", „30-Minuten-Kennenlerngespräch" statt Bewerbungsprozess

➡️ What should I avoid in a LinkedIn message to a developer?
Platitudes, tech insecurity, self-focus. Anyone who doesn't think in the language of the target group remains invisible.

5. bonus: 2 tested InMail templates with over 30 % response rate

Example 1: Senior Backend Developer (Go + Kubernetes)

Hi Alex, 
ich bin beim Suchen nach Go-Profilen mit Kubernetes-Produktionsbetrieb auf dich gestoßen – vor allem wegen deiner Arbeit bei .

We are looking for someone to help us design a new internal dev tool. The focus is on CLI usability, container isolation and resilient deployments.

If that sounds interesting to you, I would be happy to talk to you - without a CV or formal application.

Have a nice day!
Sandra | indivHR

Example 2: Frontend Dev (React + Design System)

Hi Luisa,
deine Arbeit mit Design Tokens & React Hooks (v. a. bei der App X) fand ich spannend – wir bauen ein internes Design System neu auf, mit Fokus auf Accessibility & Bundle Size.

Maybe there is a match - you would work directly with the UX Engineers on the architecture, without PM micromanagement.

Falls's für dich nicht passt, auch okay – danke, dass du's liest!

Daniel | indivHR

With indivHR we do not write generic InMails - but build tech-driven Recruiting processes with real relevance for developers.

👉 Do you want to optimise your LinkedIn approach or double your response rate in sourcing?

Then let's talk - we'll help you fill your IT vacancies.
Book a free initial consultation now 

Share article:

More articles