Technical Writer

Write and update knowledge base articles for the product areas you own, including admin guides, how-tos, and troubleshooting content

Work with the support team to spot common customer issues, close gaps in the KB, and decide what to update next

Partner with PMs and engineers as new features get built, drafting release notes, in-app help text, and UX microcopy along the way

Own one or two product areas as your main focus, and pitch in on shared areas when needed

Create your own screenshots and short screen recordings to go with your writing

Explain AI features clearly, including what they can and cannot do, and how the guardrails work

Write content that reads well for people and also works for the AI assistants pulling from the KB

Review and edit content from other writers against our style and voice guidelines

Help keep the KB healthy, including style guide upkeep, consistent terminology, and review workflows

Refresh older docs as the product changes, and clean up what's outdated

3 to 6 years of technical writing or product content experience, ideally at a B2B SaaS company

A good understanding of how enterprise software works, including permissions, roles, integrations, admin versus end-user experiences, and multi-step workflows

Clear, concise writing with strong editorial judgment and the ability to edit your own work well

Familiarity with common style guides such as the Microsoft Writing Style Guide or the Google Developer Documentation Style Guide

Product thinking: you connect features to the real problems users are trying to solve, and you see content as part of the product experience

Comfort looking at support data like ticket trends and common failure points to guide your work

A sense of how the KB feeds into support tools, whether that's agent assist, chatbots, or AI assistants

Comfort working in agile cycles with shifting scope and tight turnarounds

A portfolio with published KB articles, release notes, or product UX copy

Hands-on experience with a content management system (CMS) for knowledge base or help center content, including publishing and review workflows, versioning, tagging or taxonomy setup, and managing content across draft, review, and published states

Hands-on experience writing API documentation, including endpoint references, request and response examples, authentication flows, error handling, and code snippets

Basic understanding of information architecture and how to structure content well

Writing experience in intranet, employee experience, collaboration, or productivity products

Exposure to Knowledge-Centered Service (KCS) or a similar way of running support content

Experience writing for or about AI and LLM features, including prompt guidance and content that AI can retrieve from cleanly

Comfort using AI tools responsibly in your own writing workflow, from drafting to editing

Some background in content design systems or terminology governance

Meaningful ownership from day one, with room to grow into content strategy and IA work

Mentorship from a senior IC on UX writing, content design, and information architecture

Direct partnership with support, product, and design teams

A predictable release cadence and clear delivery expectations

Visibility into how your work moves the metrics Support cares about

We value the real you. To ensure a fair and authentic experience for everyone, we ask that you do not use AI tools (such as real-time answer generators, transcription apps, or note-taking bots) during your interview

Our process is designed to hear your unique story, thought process, and lived experience in real-time. Use of unauthorized AI tools may result in disqualification, as we want to ensure every candidate is evaluated on their own individual merits. We’re excited to meet the person behind the resume!

If you need assistive technology or AI tools for accessibility (e.g., live captioning), please notify your recruiter in advance. We are committed to providing an inclusive interview experience.

At Simpplr we believe that when work is good, life is better and that belief guides all we do. Including how we approach our flexible work model. Simpplr operates with a Hub-Hybrid-Remote model. This model is role-based with exceptions and provides employees with the flexibility that many have told us they want.

Hub - 100% work from Simpplr office. Role requires Simpplifier to be in the office full-time.

Hybrid - Hybrid work from home and office. Role dictates the ability to work from home, plus benefit from in-person collaboration on a regular basis.

Remote - 100% remote. Role can be done anywhere within your country of hire, as long as the requirements of the role are met.