linkedin-technical

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# LinkedIn for Technical Audiences

LinkedIn is where B2B developer tools win deals. This skill covers technical content that works on LinkedIn, reaching engineering managers and decision-makers, and knowing when LinkedIn beats Twitter.

---

## Before You Start

1. Read `.agents/developer-audience-context.md` if it exists
2. Assess your LinkedIn presence (profile, connections, content history)
3. Understand: LinkedIn rewards different content than developer Twitter

---

## When LinkedIn Beats Twitter

### LinkedIn's Unique Value

| Factor | LinkedIn advantage |
|--------|-------------------|
| **B2B decisions** | Decision-makers are here |
| **Enterprise reach** | CTOs, VPs, directors active |
| **Company context** | See role, company, team size |
| **Professional network** | Second-degree reach is valuable |
| **Long-form content** | Articles rank in Google |
| **Lead generation** | Built-in company/role targeting |

### Use LinkedIn When

| Scenario | Why |
|----------|-----|
| Selling to enterprises | Buyers are on LinkedIn |
| Reaching engineering managers | More managers here than Twitter |
| Recruiting developer users | Professional context |
| B2B partnerships | Companies > individuals |
| Industry/vertical targeting | Company data available |
| Longer professional content | Newsletters, articles |

### Use Twitter When

| Scenario | Why |
|----------|-----|
| Individual developers | More devs on Twitter |
| Real-time engagement | Faster conversation |
| Open source projects | Community is on Twitter |
| Casual/authentic voice | LinkedIn is more formal |
| Technical hot takes | Twitter thrives on debate |

---

## Understanding LinkedIn's Audience

### Who's Actually Active

| Segment | Engagement level | What they consume |
|---------|------------------|-------------------|
| Engineering managers | High | Leadership, team building |
| CTOs/VPs Engineering | Medium | Strategy, industry trends |
| Tech recruiters | Very high | Talent, employer branding |
| DevRel/Developer advocates | High | Community, content tactics |
| Solution architects | Medium | Technical evaluations |
| Individual developers | Lower | Career, learning |

### What LinkedIn Values

| Content type | Performance | Notes |
|--------------|-------------|-------|
| Personal stories | Very high | LinkedIn loves narrative |
| Career lessons | High | Professional growth content |
| Contrarian opinions | High | "Unpopular opinion:" works |
| Behind-the-scenes | High | Company/team stories |
| Technical deep dives | Medium | More accessible than Twitter |
| Plain announcements | Low | Need personal angle |
| Shared links | Very low | Algorithm deprioritizes |

---

## Content That Works

### The LinkedIn Technical Post Formula

```
[Hook: Personal statement or question]

[Short paragraph: The context or problem]

[Bullet points: 3-5 key insights]

[Personal take: What you learned]

[CTA: Question or action]

---

[Hashtags: 3-5 relevant ones]
```

### Example Formats

**The "Here's What Happened" Post**:
```
Last month we migrated 2TB of data from MongoDB to PostgreSQL.

Here's what we learned (and what we'd do differently):

→ Start with a test migration
   We didn't. Cost us 3 days.

→ Schema mapping is 80% of the work
   The actual migration is easy.

→ Watch for timezone handling
   MongoDB stores UTC, Postgres respects your settings.

→ Have a rollback plan
   Ours worked. Twice.

The migration took 4 days total, not the "weekend project" we planned.

From jonathimer/devmarketing-skills, MIT.

More from jonathimer/devmarketing-skills