Remote Job Content Strategy for Alexis

April 1, 2026

I'm abandoning entrepreneurship. The goal now is to find a great remote job in software engineering, marketing, or DevRel. This is the content strategy to get there: what to build, write, record, and post, in what order, and why.

Unfair advantages:

• Bilingual (French/English): opens European remote roles
• Real Go expertise, not tutorial-level
• 1+ year of actual product building with genuine failure stories
• AI-native workflow that's actually useful to write about
• Good writer who doesn't sound corporate
• Has opinions and taste (rare)

The gap: GitHub looks like research, not craft. No YouTube presence. LinkedIn is dormant. A lot of thinking, not enough showing.

---

1. 10 YouTube Videos

8-15 minutes each. No intro music. Screen + terminal, maybe face-cam. Raw is fine.

1. "I built a custom email CLI in Go. Here's how it works."
   The real code from ~/.local/bin/mail: STARTTLS, IMAP, threading, confirmation prompts. Actually impressive. DevRel engineers notice real tools.
2. "How I analyzed 300 YC startups with Claude in 3 days"
   Show the actual workflow: frontmatter, content/ai/, the analysis scripts. DevRel and developer marketing people will share this.
3. "Building a CI engine from scratch in Go"
   CI engines came up multiple times as something genuinely exciting. Zero to "runs a test suite from a YAML file." Strong signal for infra/DevTools companies (Buildkite, Depot, Dagger).
4. "Go HTTP error handling: what the stdlib doesn't tell you"
   Expand the existing blog post. Already thought through. Add a real before/after refactor. Clean Go content performs forever on YouTube.
5. "I quit indie hacking. Here's what I learned."
   Story format: Valyent, Palmframe, the reviews, the pivot. Honest numbers ($50 from Bulgaria). Gets shared by indie hackers AND recruiters. Shows maturity.
6. "Vibe-coding in 2026: my actual AI-assisted development workflow"
   Not hype. Show Claude for code, analysis, boilerplate generation. Show the friction too. Differentiates from "AI will replace developers" hot takes.
7. "Building a GitHub PR bot in Go"
   Auto-open pull requests on repos. Inspired by the Dependabot/Renovate research. Concrete, small project, highly relevant to DevTools companies.
8. "What gwern.net gets right about personal knowledge on the internet"
   Analytical, opinionated video essay. Shows taste. DevRel roles value people who can explain ideas, not just code.
9. "Linux tools I actually use every day (and why)"
   Real setup. Not a "top 10 tools" listicle. What gets used and the decision behind each. Authenticity beats completeness.
10. "How Dependabot gets 50M GitHub installs with zero ads"
    Analysis of GitHub-as-distribution. Already deeply researched. High signal for DevRel/marketing at any DevTools company.

---

2. 10 Blog Articles

Target: technical depth + personal voice. Lives on alexisbouchez.com/blog.

1. "The Go HTTP handler patterns I actually use"
   Expand the post already written. Add real examples from the email client. Show evolution from bad to good. 2000+ words with real code.
2. "Building a custom IMAP email client in Go: the full walkthrough"
   Step by step. Real code. This alone can get interviews at companies that appreciate craftspeople.
3. "How I used 15 parallel Claude agents to analyze the YC pipeline"
   One of the genuinely "alive" moments from the journal. Write it. Highly shareable in AI developer circles.
4. "What 1 year of building Valyent taught me about systems engineering"
   CloudHypervisor, microVMs, the decision to shut down. Technical post + honest reflection. Perfect for DevRel at infra companies.
5. "Goroutines and channels: the patterns I reach for every time"
   Not a tutorial. A personal pattern library. What actually gets used, when, and why the naive version gets dropped.
6. "The GitHub PR strategy that gets developer tools 10M users"
   Turn the Dependabot research into a proper article. Marketing/DevRel teams at DevTools companies will share this internally.
7. "Writing CLI tools that feel good to use"
   UX for the command line: flags, help text, error messages, colors. Taste applied to CLI design. Relevant to any engineering role.
8. "AI-native development: my actual workflow in 2026"
   Not "I use Copilot". Show how Claude gets used to draft, analyze, generate boilerplate, and where it breaks. Concrete, skeptical, useful.
9. "Why I'm betting my next 5 years on DevTools"
   Honest career reasoning. Why DevTools vs. SaaS vs. consumer. What to build next. This gets inbound from the right companies.
10. "The internet history nobody's writing down"
    Expand the internet-history section into one deep-dive: how a specific thing (IRC, early blogging, Craigslist) shaped everything built today. Shows range beyond code.

---

3. 10 Open Source Projects (One Day Each)

Small, sharp, actually useful. Each one is a talking point in an interview.

Project	What it does	Why it matters
goerr	Tiny Go library for structured HTTP error handling	Companion to the blog post. Shows taste in API design.
pr-describe	CLI that reads your git diff and auto-writes a PR description via Claude API	Genuinely saves time. Run before gh pr create.
dotenv-check	Compares .env.example vs .env, flags missing keys. Git pre-commit hook.	Solves a real pain. Every team needs it.
clog	Structured logger for Go CLI tools: pretty terminal output, JSON to file	Fills the gap between fmt.Println and full structured logging.
gh-ai-review	GitHub CLI extension: fetches PR diff, sends to Claude, returns a review summary	gh ai-review 123. DevTools companies will notice this.
mdx-validate	CLI that validates markdown frontmatter against a YAML schema	Scratches a real itch: 300+ markdown files to maintain.
cirun	Minimal CI runner in Go: reads .cirun.yml, runs steps, streams stdout	NOT a full CI system. A local task runner with CI semantics. Shows understanding of CI.
portcheck	Checks which ports from a list are open on a host. portcheck 192.168.1.1 < ports.txt	Tiny utility, used constantly in DevOps. Shows comfort at the network layer.
commitlint-go	Validates commit messages against Conventional Commits spec. Pre-commit hook.	Exists in Node.js. The Go version is useful for teams without a Node dependency.
gostarter	Go CLI project template: Cobra, structured logging, config loading, release workflow	Opinionated. Documented. Yours. Shows how you think about project structure.

---

4. 10 LinkedIn Posts

Journalist tone. No hashtags. One emoji at the very top. Short sentences.

1. "I shut down two startups before 25. Here's the one thing they had in common."
   The enthusiasm insight. Not entrepreneurship advice. A technical observation about motivation. Engineers and DevRel leads share this.
2. "How Dependabot gets 50M GitHub installs with zero marketing budget"
   Concrete numbers. Distribution mechanics. Tags a strategy any DevTools company can steal.
3. "I analyzed 300 YC startups with AI in 3 days. Here's what I found."
   Lead with the most surprising data point. Factual. Link to the site in comments.
4. "The Go patterns I reach for in every project"
   Short technical post with code snippets in the body. Engineers follow engineers who share actual code.
5. "Why I'm done building products and starting to build tools"
   Career pivot post. What changed, what's next, what I'm looking for. The "I'm available" post that doesn't sound desperate.
6. "What building a custom email client in Go taught me about the protocol layer"
   Technical + personal. Shows depth. Any infra/DevTools company wants engineers who go this deep.
7. "The GitHub PR as a distribution channel: lessons from Dependabot, Renovate, and Snyk"
   Marketing angle. DevRel and developer marketing teams at these companies will DM.
8. "Why most programming tutorials are useless (and what makes a good one)"
   Opinion piece. Sets up the YouTube/blog brand. DevRel hiring managers look for pedagogical instincts.
9. "Building a CI engine in Go: what I learned in one afternoon"
   From the YouTube video, repackaged. Short. Link to video in comments. Cross-content amplification.
10. "Why I write everything in Go"
    Not a rant. Quiet, reasoned. Shows conviction. Go-first companies (Hashicorp, Fly.io, Tailscale, Dagger) will notice.

---

5. 10 Tweets

1. Code snippet: The Go HTTP error handler pattern. 20 lines max. No explanation beyond "the pattern I use for every Go API." Engages engineers directly.
2. Honest thread: "I built 8 projects in 12 months. Only one made money ($50). Here's what I actually learned." Real numbers. No lessons at the end. Just facts.
3. Observation: "Dependabot has 50M+ GitHub installs. It has never run an ad. It opens a PR on your repo. That's the whole strategy."
4. Announcement: "I built a CLI that auto-writes your pull request descriptions using Claude. It reads your git diff. Here's the repo." For pr-describe.
5. Opinion: "The best DevRel engineers write code their audience actually runs. Not demos. Real tools."
6. Curiosity gap thread: "There's a reason CLI tools built in Go feel different from ones built in Node. It's not performance. It's something else." Thread on binary distribution, no runtime, etc.
7. Personal: "I'm done building startups. Looking for a remote role: software engineering, DevRel, or developer marketing. I write Go, I explain things well, and I've shipped real products. DM open." Once. That's it.
8. Technical thread: "Go channels: 5 patterns I actually use vs. 3 I thought I'd use." Real code. Brief explanation for each. Gets bookmarked.
9. History angle: "The story of how Craigslist accidentally shaped every marketplace that came after it." 3-tweet thread. Shows range.
10. Taste signal: "gwern.net is the best personal website on the internet. Here's what it gets right that everyone else gets wrong." 4 tweets. Links to actual posts.

---

6. Execution Order

Week	Ship	Why first
Week 1	goerr library + email client blog post	Both already mostly done in your head. Push both, tweet the library.
Week 2	"I quit indie hacking" YouTube video	Most shareable thing you can make right now. Requires zero new research. Just be honest.
Week 3	pr-describe + "Go patterns" blog post + LinkedIn post targeting DevRel	Builds the technical credibility layer. Cross-promotes the OSS work.
Week 4	The "I'm looking for remote work" tweet	By then: 3 OSS projects, 2 real blog posts, 1 YouTube video. Enough to show.

---

7. Target Companies

Don't cold apply. Get seen first. These companies would love exactly this profile:

• Dagger: CI/CD as code, Go-native, DevRel-heavy
• Depot: Faster Docker builds, small team, technical culture
• Fly.io: Go everywhere, great engineering blog, strong DevRel
• Tailscale: Go, network tools, excellent writer culture
• Mintlify: Developer docs, DevRel-forward
• Resend: Email infrastructure, great DX culture
• Railway: Deploy anything, developer-first
• Turso: SQLite at the edge, technical marketing
• Buf: Protobuf tooling, Go, strong DevRel
• Clerk: Auth infrastructure, developer marketing