Technical Writer

Description

TL;DR: Most companies treat documentation as a help centre. At Lovable it's part of the product. Millions of people learn to build software from our docs, and so do the AI agents working for them: the Lovable agent suggests pages, coding tools read them, and our assistants answer from them. You'll be our second technical writer, with product areas of your own from the start and a seat at every launch, and you'll help work out something nobody has fully worked out yet: what documentation should be when its readers are people and agents, and the product changes every day.

Why Lovable?

Lovable is the software creation platform that gives people the power to act on the problems closest to them. For decades, turning an idea into software required so much capital, technical fluency, and time that many ideas never came to life. Lovable is the counterargument: a platform for all people with ideas, ambition, and problems worth solving. From solopreneurs to small business owners to teams at companies like Adidas and Zendesk, people have built over 60 million projects on Lovable since its launch in November 2024. And we're just getting started.

We're building a generational company from Stockholm, with growing teams in London, Boston, New York, and San Francisco. Our team is small, talent-dense, and moving quickly, with a culture rooted in extreme ownership, high velocity, and low-ego collaboration. We look for people who care deeply, ship fast, and are eager to make a dent in the world.

Lovable is one of TIME's 100 Most Influential Companies and has been recognized on the Forbes AI 50 and CNBC Disruptor 50, reflecting our momentum as one of Europe's fastest-growing AI companies and one of the most ambitious places to build in this next era of software.

Responsibilities

• Drive, don't wait. Features land every day, and bigger launches several times a month. You find out what's shipping before anyone tells you, and the docs are ready the day it ships.
• Own it end to end. Work a feature out from the code and the product, write the page, verify it in Lovable, ship it, and keep it true as the product moves.
• Care about the reader more than the feature. Our docs come with data: what people can't find, what the assistant couldn't answer, what support hears. You use it to decide what to write next.
• Make the product better, not just explain it. Documenting a feature means using it end to end. You'll find the confusing label or the broken step and get it fixed before launch.
• Write for three readers on one page. The non-technical builder, the developer, and the AI agent working on their behalf.
• Build something that outlasts the week. AI drafts a lot of our pages. The human work is judgement: what a feature needs, what the engineer didn't mention, and the checks that keep hundreds of pages correct.
• Where you'll start:
• Enterprise. Identity and access, governance, audit, data residency: the pages a security team reads before they sign.
• The developer surface. Take our API and MCP references from correct to complete.
• Your first launch. Own the docs for one in your first weeks, from working group to launch day.
• Your first automation. Pick one check we still do by hand and make it run on its own.
• About your application
• Please submit your application and your writing samples in English using the form below. It's our company language, so you'll be speaking lots of it if you join.
• We treat all candidates equally - if you're interested, please apply through our careers portal.

Requirements

• You've spent 3+ years documenting software products, and you can show us pages that get a reader to the outcome without re-reading.
• You already write with AI: for research, drafting and checking, not just polish. You know what it gets wrong and you catch it.
• You test what you document. You'd rather try the feature and read the source than take someone's word for it, and when something's broken or confusing, you say so.
• You're at home in docs-as-code: Git, Markdown and pull requests.
• You ask engineers and PMs specific questions, and when documenting a feature shows it won't make sense to users, you raise it early, with reasons.
• Preferred:
• You've shipped docs weekly at a startup or scale-up, finding out what changed yourself.
• You've written for AI readers, or you're curious about it.
• You have UX writing or content design experience, or an interest in it.
• You can read code well enough to check how a feature actually behaves; writing code is not required.