Writes tailored recruiter outreach messages for LinkedIn, email, and job application follow-ups. Apply when asked to write a message to a recruiter, follow up on an application, or reach out about a job posting. Produces short, human, specific messages that avoid AI-sounding phrases.
Writes short, specific outreach messages to recruiters on LinkedIn, email, or any professional platform. Applies to:
A recruiter message is not a mini cover letter. It answers one question: "Is this person worth a conversation?"
The goal is a reply, not a sale. Short, specific, and human beats long, comprehensive, and impressive every time.
| Type | Platform | Max Length |
|---|---|---|
| Follow-up after applying | 4-5 sentences | |
| Cold outreach about posting | 4-5 sentences | |
| Response to recruiter question | LinkedIn/Email | 3-4 sentences per question |
| Email follow-up | 3 short paragraphs |
Never exceed these lengths. If it doesn't fit, cut — don't expand.
Sentence 1: State what you applied for (role name, company)
Sentence 2: One specific technical angle relevant to their stack
Sentence 3: One GitHub link with one-sentence description
Sentence 4: Invite reply without pressure
Example:
I just applied for the Golang Engineer position and wanted
to reach out directly.
My most relevant project is a Go REST API achieving
77K-92K req/sec with atomic zero-downtime deployments:
github.com/Giygas/medicaments-api
Happy to discuss if it looks like a fit.
Sentence 1: Reference the specific posting by title
Sentence 2: Why this company/role specifically — one concrete reason
Sentence 3: One technical anchor (project or metric)
Sentence 4: Call to action
Answer each question directly and concisely. One sentence per answer where possible. Add context only where it helps the recruiter make a decision.
Salary questions:
Availability/relocation questions:
When writing for Gustavo Rossich, always draw from these anchors:
Primary technical anchor: Go REST API — 77K-92K req/sec, atomic zero-downtime deployments, 78.5% test coverage, complete Prometheus/Grafana/Loki observability → github.com/Giygas/medicaments-api
Secondary technical anchors:
Background anchor (use sparingly, one sentence max): 7 years French Foreign Legion — shapes reliability and production systems mindset. Never elaborate beyond one sentence unless the recruiter asks.
Salary ranges (adjust based on role seniority and location):
Availability:
Always provide a range — single numbers invite lowballing.
Acknowledge experience level honestly if entry-level:
Considerando que es mi primer puesto profesional como
desarrollador, busco un rango de 40.000–44.000€ brutos
anuales, dependiendo del paquete y las responsabilidades.
Never apologize for the range — state it factually.
Never say "I'm flexible" — it signals you don't know your worth.
After giving the range, move forward:
Quedo disponible para una llamada cuando te venga bien.
Be specific about timeline — "4-6 weeks" not "soon" or "ASAP".
Mention EU citizenship proactively — removes a common friction point recruiters face with candidates from other countries.
Don't over-explain — one sentence covers it:
Soy ciudadano de la UE, por lo que la mudanza sería
sencilla — podría estar disponible en 4–6 semanas.
LinkedIn informal (emoji in their message): → Match informal tone, short sentences, skip formal closing formula
LinkedIn professional (no emoji, formal language): → Match professional tone, slightly longer sentences acceptable
Email formal: → Use proper opening (Madame/Monsieur or equivalent) → Use proper closing formula for the language:
Never use formal closing formulas on LinkedIn — they read as copy-pasted from a letter template.
Before delivering any recruiter message: