# LinkedIn section recipes

## Headline recipe

Default pattern:

```text
Role | Stack | Impact
```

Rules:

- lead with the clearest current or target role
- include only the top two or three technologies
- finish with a specialization, problem space, or outcome
- use clean delimiters such as `|`
- avoid fluff such as `passionate`, `guru`, `ninja`, or `results-driven`

Good shape:

```text
Senior Backend Engineer | Go, Kubernetes, PostgreSQL | Building low-latency distributed systems
```

## About section recipe

Use first person and short paragraphs.

Recommended flow:

1. strongest positioning claim in the opening lines
2. what problems the person solves
3. what stack, methods, or domains they use
4. one or two proof-backed outcomes
5. target role or collaboration focus
6. optional CTA if natural

Rules:

- convert keyword lists into evidence-rich sentences
- explicitly name target role or audience if that is part of the user's goal
- use bullets only when they improve scanning
- do not write in third person

## Experience entry recipe

For each role:

- keep title, company, and dates aligned with the user's other sources
- add a short positioning line or opener when useful
- prefer concise bullets over generic paragraphs
- make scope, ownership, stack, and results explicit
- add proof links when public artifacts strengthen the claim

Bullet pattern:

```text
Action + domain or scope + tool or method + measurable outcome
```

Example shape:

```text
Built internal observability tooling in Go and Prometheus for a multi-service platform, reducing mean time to detect production issues by 32%.
```

## Skills recipe

- use standard recognizable skill names
- reorder the top skills to match current positioning
- prefer a shorter credible list over a bloated weak one
- make sure the top skills also appear in Experience, Education, Featured, or credentials
- do not rely on discontinued Skill Assessments

## Featured section recipe

Prioritize proof of work:

- live demos
- GitHub repositories
- technical articles
- talks
- architecture diagrams
- strong niche-aligned LinkedIn posts

Rules:

- link to the specific artifact, not a generic homepage
- prefer strong thumbnails or visual assets over plain preview cards
- rotate stale content out when it no longer reflects current positioning

## Section rewrite posture

- preserve facts and upgrade structure
- if a section lacks enough evidence, say what is missing instead of fabricating stronger claims
- keep section-level language consistent with the same target role across the whole profile
