AIPM
Theme
WorkText outputGuided

LinkedIn Headline for a Target Role

Craft a searchable LinkedIn headline tuned to a target role, seniority, and keywords recruiters actually query. Why it matters: a ready draft saves you from a blank page.

Scanned · no issues

Ready to use

Prompt

Craft LinkedIn headlines for my target role. Optimize for recruiter search without hype.

Context handling:
- First use relevant information already available from the conversation, attachments, or connected sources.
- Do not ask me to repeat details you already have.
- If a required detail is missing, ask one short follow-up.
- State important assumptions. Never invent employers, titles, metrics, dates, or credentials. Use [METRIC NEEDED] or [needs proof] when evidence is missing.

Inputs:
- Target role: {{target_role}}
- Seniority: {{seniority}}
- Specialty / keywords: {{specialty}}
- Location or remote (optional): {{location_or_remote}}

Rules:
- Hard limit: under 220 characters. Put the strongest searchable hook in the first ~60 characters.
- Include a clear role direction plus 2-4 recruiter-query keywords I can defend.
- Avoid banned fluff: passionate, results-driven, guru, ninja, rockstar, thought leader, visionary.
- Do not invent titles, employers, or credentials.
- Prefer plain punctuation (|, ·, —) over emoji spam.

Weak vs strong (illustrative pattern only — adapt to my inputs):
- Weak: "Passionate leader | Helping teams succeed | Open to work"
- Strong: "Senior Backend Engineer | Distributed systems · Go · AWS | Ex-fintech platform"

Produce:
1) Assumptions (1-3 bullets)
2) Keyword bank: must-use / nice-to-use / avoid (only from evidence)
3) 5 ranked headline options (each with char count + one sentence why it works for search)
4) One "Open to work" variant and one "employed / building in public" variant if relevant
5) Final pick recommendation with a 1-line posting checklist

Create your final prompt

Add your context and generate

Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.

Target job title or role family
Seniority level to signal
Domain, stack, or specialism keywords
Location or remote preference if useful in headline

What to expect

Example output

Five ranked headline options under 220 characters with keyword rationale and a weak-vs-strong comparison.

Example context

Example input

Target role: Senior Backend Engineer. Seniority: Senior. Specialty: distributed systems, Go, AWS. Location: Remote.

Discussion

Comments (0)

Loading comments…