---
id: ins_resume-headline-as-recruiter-handle
operator: Roshni Chellani
operator_role: Staff MST, MediaTek
source_url: https://www.linkedin.com/feed/update/urn:li:activity:7310323349337870336
source_date: 2026-04-10
captured_date: 2026-05-02
source_type: thread
source_title: Recruiters at Amazon, Meta, and Google reject resumes like this in 5 seconds
domain: [hiring]
lifecycle: [hiring-team-design]
maturity: applied
artifact_class: playbook
score: { originality: 1, specificity: 4, evidence: 2, transferability: 4, source: 3 }
tier: C
related: []
raw_ref: raw/linkedin/pmm-mining/linkedin-saved-posts-2026-04-10.md
---

# A role-targeted headline below the name is the first ATS+human filter

## Claim
A resume without a role-targeted headline (e.g. "Data Analyst | Power BI | SQL | Business Insights") fails the recruiter-skim test in seconds because the reviewer can't infer the target role from the name alone. The fix is one line of role and tooling keywords directly under the name.

## Mechanism
ATS systems weight keyword density near the top; human recruiters skim top-down for 5-10 seconds. Both want a fast handle on "what role does this person want?". A headline collapses that decision into one parse.

## Conditions
Holds when:
- Applying to roles where ATS pre-filters resumes.
- Background is multi-disciplinary and the target role is ambiguous from job titles alone.

Fails when:
- The candidate has the exact target title in their most recent role and the resume already opens with it.

## Evidence
> "Without a clear title like 'Data Analyst' or 'Business Intelligence Specialist', you're just another generic profile. Fix: Add a headline below your name."

· Roshni Chellani, LinkedIn, 2026-04-10 (scrape date)

## Signals
- Resume A/B tests show callback rate lifts when headline is added.
- ATS keyword scans rank the resume higher for target role.

## Counter-evidence
No opposing view in current corpus.

## Cross-references
- (none in current corpus)