Senior Content Engineer at Lingo.dev

About Lingo.dev

Lingo.dev is the localization engineering platform where teams measure translation quality, translate with LLMs, and proofread with native speakers. Lingo.dev graduated from the world's best tech accelerator (Y Combinator) and raised venture funding to grow into new markets.

The job

You own content production and distribution: write, publish, distribute the same day, measure, and automate the boring parts, aggressively. The founders set the direction, you decide what gets written each day and how what you write reaches its readers.

Concretely: blog posts, research articles backed by original engineering discoveries, essays, the changelog, product update emails, the newsletter, LinkedIn, dev.to, Hacker News, Reddit, Google Ads, SEO, and the occasional example repo or demo project. You write about events, news, research results, and product features through the lens of Lingo.dev's positioning, for a technical audience and for a non-technical one. You interview founders, engineers, and customers, and you write from what they said, quoted. You publish on the site and off it, and contribute to our playbook and the narrative every piece is written from.

Whatever is due this week is published this week. The volume grows, and you keep up by automating: Claude workflows, templated distribution, scheduled publishing.

You own organic and paid: SEO, GEO, AI visibility. You track what gets cited, what ranks, what compounds, and what the spend returns, in Ahrefs, Search Console, and the ad accounts.

Requirements

• You write in plain words, state facts, and cut every superlative and every sentence that carries no intention.

• You have published content that got traction: a newsletter with real subscribers, posts that hit the front page, technical content developers shared. Show it.

• You code enough to automate your own workflow. Vibe coding, scripting, AI-assisted development. A distribution pipeline on a schedule.

• You interview well. You get a person's real opinion on the record, in words you can quote, and you turn it into a story told through the lens of Lingo.dev's positioning.

• You write for engineers. Technical, specific, mechanism-first, and you can explain how a retrieval-augmented system works. You write for a non-technical reader with the same precision.

• Claude/similar is your production method. You use it daily to produce at volume, and you have opinions about prompting, output quality, when to override, when to trust.

• You know what Hacker News rewards, what LinkedIn's algorithm favors, and how to get a piece cited by AI systems.

• You work SEO from the data. Ahrefs or Semrush and Search Console are open every day, and you pull rankings, backlinks, and AI citations from them yourself.

• You care whether the piece drove signups, got cited, ranked, or earned backlinks, and you report it.

Optional skills

• You have marketed to a skeptical audience.

• You have written research or essays that changed how a field thinks about a problem.

• You have recorded and published YouTube videos, or made them with AI video tools such as Higgsfield or Hyperframes.

Benefits

• Original engineering research to write about, from the engineers who did it.

• The whole pipeline is yours, from the first draft to the number the piece moved.

• Claude Code and Claude Cowork in daily production, with the budget to use them at volume.

• Small team working directly with founders.

• Occasional travel to meet the team in person.

• Conference and learning budget.

• Flexible working hours.

• Health insurance.

Interview process

Screening call. Trial project + an interview. Offer. Four-week paid probation.

Do not apply if

• Claude, Claude Cowork, or Claude Code is missing from your daily work.

• Your content strategy is a keyword spreadsheet and a publishing calendar.

• Your work ends at publish, and someone else distributes and measures.

• You have used AI to produce content a handful of times, or never, and plan to keep it that way.

• You need a brief each week to know what to write.

• You call yourself "not technical".

• Your portfolio reads the same with another company's logo on it.

• You want to manage a team in year one.

• You are applying for the accelerator's name or the funding round.