- Restructured repo from single skill to skills collection - Added 7 new skills: Resume Architect, Cover Letter Craft, Interview Commander, Salary Negotiator, Career GPS, LinkedIn Optimizer, Job Switch Advisor - Rewrote README as collection hub with pipeline diagram, integration map, and usage-by-stage guides Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
212 lines
6.8 KiB
Markdown
212 lines
6.8 KiB
Markdown
# LinkedIn Optimizer
|
|
**Turn your LinkedIn profile into a recruiter magnet and networking machine.**
|
|
Your LinkedIn is your 24/7 personal brand. Most profiles are digital resumes. This skill makes yours a lead-generation engine.
|
|
|
|
## Philosophy
|
|
LinkedIn is not a resume. It's a **landing page** for your professional brand. Every element should work together to:
|
|
1. Show up in recruiter searches (SEO)
|
|
2. Communicate your value in 5 seconds (hook)
|
|
3. Prove your expertise through content (authority)
|
|
4. Make it easy to contact you (conversion)
|
|
|
|
## Input Required
|
|
- Current LinkedIn profile (URL or screenshots)
|
|
- Target role or career direction
|
|
- Your resume or career notes
|
|
- Any portfolio/project/GitHub links
|
|
|
|
## Workflow
|
|
|
|
### Phase 1: Profile Audit
|
|
```
|
|
Score your current profile (0-10 each):
|
|
|
|
□ Headshot: Professional, approachable, recent
|
|
□ Background/Banner: Branded, not default blue
|
|
□ Headline: Keyword-rich, not just "Engineer at X"
|
|
□ About/Summary: Story-driven, keyword-dense
|
|
□ Experience: Achievement-focused, quantified
|
|
□ Skills: 50 max, endorsed, keyword-matched
|
|
□ Recommendations: 3+ from managers/peers
|
|
□ Activity: Recent posts, comments, engagement
|
|
□ Featured: Portfolio items, publications, talks
|
|
□ Education: Complete with relevant details
|
|
|
|
Total: ___/100
|
|
```
|
|
|
|
### Phase 2: Headline Engineering
|
|
```
|
|
Your headline is the #1 factor in LinkedIn search results.
|
|
|
|
Bad headlines:
|
|
- "Software Engineer at [Company]"
|
|
- "Looking for new opportunities"
|
|
- "Full Stack Developer"
|
|
|
|
Good headlines:
|
|
- "Senior Backend Engineer | Rust • Go • Distributed Systems | Building Scalable APIs"
|
|
- "Staff Engineer @ [Company] | Helping Teams Ship Faster | Ex-[Notable Company]"
|
|
- "Product Designer | B2B SaaS • Design Systems • Accessibility | Open to Senior Roles"
|
|
|
|
Formula:
|
|
[Current or Target Title] | [Key Skills/Stack] | [Value Prop or Niche]
|
|
|
|
Rules:
|
|
- Use " | " or " • " as separators (LinkedIn reads these)
|
|
- Front-load keywords recruiters search for
|
|
- Include your niche or differentiator
|
|
- If job searching, add "Open to [Role] roles" (only visible to recruiters if you use "Open to Work" feature)
|
|
- Keep under 220 characters
|
|
```
|
|
|
|
### Phase 3: About Section
|
|
```
|
|
The About section is for storytelling + keyword density.
|
|
|
|
Structure (4-5 paragraphs, 300-500 words):
|
|
|
|
Paragraph 1 — Identity Statement (2-3 sentences)
|
|
"I'm a [role] who [what you do differently]. Over [X] years,
|
|
I've [biggest achievement]. Currently [current context]."
|
|
|
|
Paragraph 2 — Expertise (keyword-dense bullet list)
|
|
"Core expertise:
|
|
• [Skill 1] — [specific application, metric]
|
|
• [Skill 2] — [specific application, metric]
|
|
• [Skill 3] — [specific application, metric]
|
|
• [Skill 4] — [specific application, metric]"
|
|
|
|
Paragraph 3 — Philosophy/Approach (2-3 sentences)
|
|
"My approach: [what makes you different].
|
|
I believe [professional philosophy relevant to target]."
|
|
|
|
Paragraph 4 — Proof Points (optional, 2-3 sentences)
|
|
"Notable projects: [Project 1 with impact].
|
|
Recognized for [award/publication/talk]."
|
|
|
|
Paragraph 5 — Call to Action (1-2 sentences)
|
|
"Always interested in connecting with [who].
|
|
Reach me at [email] or DM me here."
|
|
|
|
SEO Tips:
|
|
- Include all target keywords naturally
|
|
- Use the exact phrases recruiters search: "distributed systems", "React", "AWS"
|
|
- Mention tools, frameworks, and methodologies by full name
|
|
- Include industry terms and domain language
|
|
```
|
|
|
|
### Phase 4: Experience Optimization
|
|
```
|
|
For each role:
|
|
|
|
[Job Title] | [Company]
|
|
[Start] - [End] | [Location]
|
|
|
|
[Company description — 1 line if not well-known]
|
|
|
|
• [Achievement with metric] — [tech used]
|
|
• [Achievement with metric] — [tech used]
|
|
• [Achievement with metric] — [tech used]
|
|
• [Achievement with metric] — [tech used]
|
|
|
|
Rules:
|
|
- 4-6 bullets per role (more for recent, fewer for older)
|
|
- Lead each bullet with a strong action verb
|
|
- Include at least one metric per bullet
|
|
- Bold key achievements for scanability
|
|
- Mirror the language of your target role
|
|
- Never describe responsibilities without outcomes
|
|
```
|
|
|
|
### Phase 5: Content Strategy
|
|
```
|
|
LinkedIn algorithm favors:
|
|
- Original content (not reshared)
|
|
- Posts with engagement in first hour
|
|
- Content that drives comments (not just likes)
|
|
- Consistent posting (2-3x/week minimum)
|
|
|
|
Content types ranked by effort vs. impact:
|
|
|
|
High Impact, Low Effort:
|
|
- Comment thoughtfully on industry leaders' posts (5-10/day)
|
|
- Share articles with your 2-3 sentence take
|
|
- Celebrate others' achievements
|
|
|
|
High Impact, Medium Effort:
|
|
- Share lessons from your work (no confidential info)
|
|
- "Hot take" posts on industry trends
|
|
- Before/after transformation stories
|
|
|
|
High Impact, High Effort:
|
|
- Technical deep-dives (articles)
|
|
- Career advice posts
|
|
- Thread-style posts (numbered lists)
|
|
|
|
Posting schedule:
|
|
- Mon/Wed/Fri: 8-10am your timezone
|
|
- Comment on 5-10 posts daily
|
|
- Reply to every comment on your posts within 1 hour
|
|
```
|
|
|
|
### Phase 6: Network Growth
|
|
```
|
|
Strategic connection building:
|
|
|
|
Daily targets:
|
|
- 5-10 connection requests to people in target companies
|
|
- 5-10 thoughtful comments on industry posts
|
|
- 1 post or share of your own
|
|
|
|
Connection request template:
|
|
"Hi [Name], I came across your work on [specific thing]
|
|
and found [specific insight] really valuable. Would love
|
|
to connect and follow your updates."
|
|
|
|
Not:
|
|
"I'd like to add you to my professional network." (Default garbage)
|
|
|
|
Who to connect with:
|
|
- Recruiters at target companies (search: "[Company] recruiter")
|
|
- Engineering managers at target companies
|
|
- People with your target title (peer learning)
|
|
- Industry thought leaders (content amplification)
|
|
- Alumni from your school or previous companies
|
|
```
|
|
|
|
## LinkedIn SEO Checklist
|
|
```
|
|
Keywords to optimize:
|
|
□ Headline: Primary title + 3-5 skills
|
|
□ About: Natural keyword density (2-3% per term)
|
|
□ Experience: Tech stack mentioned in context
|
|
□ Skills section: All target keywords added
|
|
□ Job titles: Standard industry titles (not creative ones)
|
|
|
|
Profile completeness:
|
|
□ All sections filled out
|
|
□ Custom URL: linkedin.com/in/yourname
|
|
□ Location set (affects search radius)
|
|
□ Industry selected correctly
|
|
□ "Open to Work" set (recruiters only visibility)
|
|
□ Contact info: email, portfolio, GitHub
|
|
□ Featured section: 2-3 items
|
|
□ 50 skills listed and prioritized
|
|
□ 3+ recommendations
|
|
□ Background banner (not default)
|
|
□ Pronouns (if desired — shows cultural awareness)
|
|
```
|
|
|
|
## Integration with Other Skills
|
|
- **jobhunter-master**: Uses optimized profile for outreach
|
|
- **resume-architect**: Shares career data for consistency
|
|
- **career-gps**: Aligns profile with target trajectory
|
|
- **browser**: LinkedIn automation and profile updates
|
|
- **bird**: Cross-platform personal branding with Twitter/X
|
|
|
|
## Files
|
|
- `memory/linkedin-audit.md` — Profile score and action items
|
|
- `memory/linkedin-content-calendar.md` — Post ideas and schedule
|
|
- `memory/linkedin-network.md` — Strategic connection targets
|