Lingo.dev is a localization engineering platform. Teams create localization engines – stateful translation APIs configured with glossaries, brand voice, model chains, and AI Reviewers. Backed by Y Combinator and Initialized Capital. 200M+ words translated, 5,000 GitHub stars, 7,000 weekly CLI runs.
You own content production and distribution for a developer tools company building localization infrastructure. You produce the content, you distribute it, you measure what worked, you automate what repeats.
The scope of what you could be working on: blog posts, research articles, changelog, product update emails, newsletter, LinkedIn, dev.to, Hacker News, Reddit, Google Ads, SEO, and occasionally building example repos and demo projects. You'll have high autonomy and freedom in a direction defined by the founders.
The expectation: whatever needs to ship this week ships this week. The volume grows. You scale it by building automations – AI workflows, Claude-based production pipelines, templated distribution, scheduled publishing. You are not manually doing in month six what you were manually doing in month one.
Write and produce technical content for an audience of senior engineers and engineering leads – mechanism-dense, fact-backed, no filler
Distribute every piece across owned channels (site, email, newsletter) and external platforms (Hacker News, dev.to, LinkedIn, Reddit) on the same day it publishes
Manage social presence across accounts – draft posts, queue them, keep slots filled
Own SEO/GEO and AI visibility metrics – track what gets cited, what ranks, what compounds
Run Google Ads – set up campaigns, manage budget, measure against pipeline
Book founders on podcasts and external content opportunities
Build example repos and demo projects via vibe coding when a piece needs a working artifact
Build and maintain the production pipeline – automate draft generation, distribution, scheduling, reporting
You've shipped content that got traction. A newsletter with real subscribers. Blog posts that hit the front page. Technical content that developers actually shared. Show us.
You write for engineers. Not "thought leadership" that sounds like a press release. Technical, specific, mechanism-first writing that respects the reader's intelligence. You can explain how a retrieval-augmented system works without dumbing it down or puffing it up.
You code enough to automate your own workflow. Vibe coding, scripting, AI-assisted development – you build tools for yourself. A distribution pipeline that runs on a schedule. A draft generator that pulls from a git log. You treat content ops as infrastructure, not manual labor.
AI workflows are your production method. You use AI tools daily to produce at volume. You have opinions about prompting, output quality, when to override, when to trust. You don't produce everything by hand – you produce at scale with taste.
You think in distribution, not just creation. You know what Hacker News rewards (problem-first, no self-promotion). You know what LinkedIn's algorithm favors. You know how to get a piece cited by AI systems. Publishing without distributing is not shipping.
You own the number. Not "I wrote the thing and someone else measured it." You care whether the piece drove signups, got cited, ranked, earned backlinks. You close the loop.
Experience marketing developer tools or infrastructure products
Familiarity with localization, i18n, or multilingual software
Background in demand generation – you've run content programs where the goal was pipeline, not pageviews
Experience with category-level content – research and essays that shape how an audience thinks about a problem space
You aren't a power user of Claude / Claude Cowork / Claude Code
You think "content strategy" means a spreadsheet of keywords and a publishing calendar
Your workflow is: write brief, wait for approval, publish, move on – no distribution instinct, no ownership of what happens after publish
You've never used AI tools to produce content at speed and don't intend to
You need someone to tell you what to write every week
You describe yourself as "not technical" and see that as fine for this role
Your portfolio is corporate B2B content that could belong to any company with the logo swapped out
Competitive salary and health insurance
Conference and learning budget
Flexible hours with occasional team travel
Direct collaboration with founders
Screening call. Paid trial project. Offer. 4-week paid probation period.
