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

Use LinkedIn When

Use Twitter When

Understanding LinkedIn's Audience

Who's Actually Active

What LinkedIn Values

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.

What's your biggest database migration war story?

#engineering #databases #postgresql

The "Unpopular Opinion" Post:

Unpopular opinion: Most engineering teams don't need Kubernetes.

I've seen 3-person startups running K8s because "Netflix uses it."

The reality:
• Single container on Railway/Render: $20/month
• Managed K8s: $300/month minimum
• Self-hosted K8s: 1 FTE just for maintenance

Kubernetes is amazing for:
→ Multi-region deployments
→ Complex orchestration needs
→ 99.99% SLA requirements

But most apps? Docker Compose on a VM is fine.

What's the smallest team you've seen running Kubernetes?

#devops #kubernetes #startups

The "Behind the Scenes" Post:

We just hit 10,000 API calls per second.

Here's the unsexy truth about scaling:

6 months ago we could barely handle 1,000 req/s.

What changed:
→ Moved hot paths to Redis
→ Implemented connection pooling (finally)
→ Added CDN for static assets
→ Profiled and found 3 N+1 queries

No fancy architecture. No rewrite.
Just fixing obvious stuff we'd ignored.

The lesson: Optimize boring things first.

What's the simplest optimization that made your biggest impact?

Content Mix for LinkedIn

Formatting Best Practices

Post Structure

What Gets Hidden

LinkedIn truncates after ~210 characters. Your first 2-3 lines are critical.

Bad hook (no curiosity gap):

I wanted to share some thoughts about microservices.

Good hook (creates curiosity):

We ripped out our microservices architecture.

Here's why going back to a monolith was the right call:

Visual Content

Carousel tips:

• 5-10 slides optimal
• First slide = thumbnail (make it count)
• Large text, minimal per slide
• Upload as PDF for carousel effect

Company Page vs Personal

When to Use Each

The Reality

Strategy: Post from company page, have team members share with personal commentary.

Reaching Engineering Managers

What Engineering Managers Care About

Content Angles for EM Audience

Hashtags

Technical Hashtags That Work

Hashtag Rules

• 3-5 hashtags maximum
• Put at the end of post
• Mix broad (#engineering) and specific (#kubernetes)
• Skip if post is personal/narrative

Platform-Specific Do's and Don'ts

Do's

1. Do write posts, not status updates
2. Do use line breaks liberally
3. Do start with a hook
4. Do share personal experiences
5. Do engage in comments (first hour matters)
6. Do cross-post from company page personally
7. Do use carousels for educational content
8. Do mention people and companies when relevant

Don'ts

1. Don't post just links (algorithm kills them)
2. Don't use LinkedIn like Twitter
3. Don't over-hashtag (looks spammy)
4. Don't be too promotional
5. Don't ignore comments
6. Don't post walls of text without breaks
7. Don't share memes (different culture than Twitter)
8. Don't buy engagement pods

Profile Optimization

Technical Professional Profile

Headline examples:

Staff Engineer at Stripe | Building payments infrastructure

VP Engineering at Startup | Scaling teams from 5 to 50

DevRel at Supabase | Making databases accessible

LinkedIn Articles vs Posts

When to Use Articles

Article Best Practices

• Front-load value (assume people don't finish)
• Use headers and formatting
• Include visuals
• End with CTA
• Share as post after publishing

Tools

Content Calendar

Weekly Template

Measuring Success

Metrics That Matter

Good Benchmarks

Related Skills

• developer-audience-context — Know who you're reaching
• x-devs — Cross-post adapted content
• github-presence — Link from LinkedIn to GitHub
• youtube-devrel — Share video content on LinkedIn