At a glance
- Experience
- 3+ years experience
- Employment
- Full-time
- Workplace
- Onsite
- Location
- Stockholm
About the role
- Lovable is seeking its second technical writer to own product areas from the start and participate in every launch.
- This role involves figuring out what documentation should be when its readers are both humans and AI agents, while the product changes daily.
Responsibilities
- Drive documentation by finding out what is shipping before anyone tells you and ensuring docs are ready the day features ship.
- Own documentation end to end by working features out from the code and product, writing pages, verifying them in Lovable, shipping them, and keeping them accurate.
- Use data such as what people cannot find, what the assistant could not answer, and what support hears to decide what to write next.
- Test what you document by trying features and reading the source.
- Identify confusing labels or broken steps and get them fixed before launch.
- Write pages for three audiences: the non-technical builder, the developer, and the AI agent.
- Apply human judgment to AI-drafted pages to determine what features need, what engineers missed, and what keeps pages correct.
- Own documentation for enterprise features including identity and access, governance, audit, and data residency.
- Take API and MCP references from correct to complete.
- Automate checks that are currently done by hand.
Requirements
- Spent 3+ years documenting software products with pages that get a reader to the outcome without re-reading.
- Write with AI for research, drafting, and checking, and know how to catch its mistakes.
- Test what you document by trying features and reading the source.
- Comfortable in docs-as-code environments including Git, Markdown, and pull requests.
- Ask engineers and PMs specific questions and raise early concerns when a feature will not make sense to users.
Preferred qualifications
- Shipped docs weekly at a startup or scale-up and figured out what changed yourself.
- Written for AI readers or have curiosity about it.
- UX writing or content design experience, or an interest in it.
- Can read code well enough to check how a feature actually behaves, though writing code is not required.
Skills
- Git
- Markdown
- API
- MCP
