Technical Writer
About Us
Flagsmith is on a mission to empower engineering teams to ship faster and continuously improve their products and our timing is perfect to make an impact. As the landscape for software development evolves, more and more companies are leveraging tools like Flagsmith to safely release AI generated code into production. The future of code production will be even faster, but getting safe and impactful features into production will remain the challenge.
Our team spans multiple continents and is 100% remote, with deep roots in engineering and a strong focus on product quality, focus, and community. We are filled with team members who have been searching to have impact, and larger scope as opposed to being a cog at a large organisation!
What We're Looking For
We're looking for someone who writes clearly about technical things and actually enjoys getting into the details. You'll be happy reading code in a few different languages, pulling down an SDK to see how it really behaves, and asking our engineers awkward questions until the answer makes sense. Feature flagging touches most of the stack, so there's plenty to get stuck into.
This isn't a role where someone hands you a ticket and tells you what to write. You'll work out what needs documenting, decide what good looks like, and get on with it. Our docs are open source and public, so your work ships fast and people notice it.
What You’ll Do
- Own the READMEs and docs across our open-source repositories, where most people meet Flagsmith for the first time
- Run our user-facing technical documentation at docs.flagsmith.com, including self-hosting and deployment
- Work with engineering so the docs ship with the feature rather than a month later
- Take ownership of our internal documentation in Notion, both technical and organisational
- Contribute to and write our technical marketing content: blog articles, landing pages, comparison pages
- Create educational content on the product: video demos, walkthroughs, worked examples
What You'll Bring
- At least one year writing technical content for a developer audience. We'd like to see examples, whether that's docs, tutorials, READMEs or blog posts.
- A solid technical grounding. A CS degree or similar is great, but hands-on time as a developer counts just as much.
- The ability to read code in a few languages and work out what it does, even if you don't write it every day.
- Comfort with a docs-as-code setup: Git, markdown, pull requests and static site generators.
- A knack for taking something messy and half explained and turning it into a page a developer can follow.
- Strong written communication skills, and opinions about what makes writing good.
- A keen curiosity for all things technical.
- A love of open-source technologies, and ideally some contributions of your own.
Nice to Haves
- You've worked with Docusaurus, or something similar.
- Experience making video content: e.g. product demos, and walkthroughs.
- You know your way around feature flags, CI/CD or other developer tooling.
- You can write marketing content that doesn't read like marketing content, and you have some idea of how SEO works.
- Experience working in a fully remote, distributed team.