Technical Writer

Job summary

Responsibilities

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.

• 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…
• 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.
• 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.

What they're looking for

• 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.