[Hiring] Senior Content Engineer @Lingo.dev

Role Description

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.

• 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.
• 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.
• Interview founders, engineers, and customers, and write from what they said, quoted.
• 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.
• Automate workflows, templated distribution, scheduled publishing.
• Own organic and paid: SEO, GEO, AI visibility.
• Track citations, rankings, and spend returns in Ahrefs, Search Console, and ad accounts.

Qualifications

• Write in plain words, state facts, and cut every superlative and every sentence that carries no intention.
• Published content that got traction: a newsletter with real subscribers, posts that hit the front page, technical content developers shared.
• Code enough to automate your own workflow: vibe coding, scripting, AI-assisted development.
• Interview well to get a person's real opinion on the record, in words you can quote.
• Write for engineers: technical, specific, mechanism-first, and explain complex systems clearly.
• Use Claude/similar as your production method daily to produce at volume.
• Understand Hacker News rewards, LinkedIn's algorithm, and how to get cited by AI systems.
• Work SEO from the data using Ahrefs or Semrush and Search Console.
• Care about the piece's performance: signups, citations, rankings, backlinks, and report it.

Requirements

• Optional skills include marketing to a skeptical audience.
• Writing research or essays that changed how a field thinks about a problem.
• Recording and publishing YouTube videos, or making 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.