Stylo is an AI support platform used by over 750 companies, helping customer support agents resolve issues faster through real-time assistance and automation. We’re a small, high-performing team at an early stage with strong customer traction.

The Role

We're looking for a part-time technical writer to own and improve documentation across the Stylo platform. As we scale, the challenge isn't just shipping features, it's making them learnable. You'll work on problems like how admins onboard to a visual workflow builder, how developers integrate against our APIs, and how new product capabilities get explained without losing the nuance that makes them useful.

This is a high-ownership role on a small team. You'll work directly with the CEO and engineering, write docs end-to-end from outline to publish, and have meaningful influence over how Stylo is taught and adopted. The product moves fast, so the right person is comfortable shipping clear writing in tight loops with engineering and customer success.

What You'll Work On

Product documentation. Setup guides, feature walkthroughs, integration docs, and admin reference material for the Stylo platform.
API and developer docs. Reference documentation, code examples, and developer guides for Stylo Studio, our embeddable widget, and our integration ecosystem.
Release notes and changelogs. Translating engineering work into clear customer value as features ship.
Onboarding content. In-app help text, tooltips, email sequences, and getting-started guides for new admins and agents.
Documentation hygiene. Auditing and improving existing docs for accuracy, voice, and findability. Retiring or rewriting content that no longer reflects how the product works.
Thought leadership support. Occasional contributions to blog posts, knowledge base best practices, and customer-facing explainers about AI in support workflows.

What We're Looking For

3+ years of technical writing experience, ideally in B2B SaaS, developer tools, or customer support software
Strong portfolio of public-facing documentation, especially for products with both admin and developer audiences
Comfort working independently. You can watch a Loom, read a PR, and turn it into a clear doc without needing a kickoff meeting
Clear, direct prose. You know when to use a screenshot, when to use a code block, and when to cut the paragraph entirely
Working knowledge of REST APIs, webhooks, and JSON. You don't need to be an engineer, but you should be able to read a code sample and understand what it does
Familiarity with documentation tooling and a point of view on what works

Bonus Points

Experience writing for the Zendesk, Freshdesk, Intercom, or Salesforce Service Cloud ecosystems
Background in customer support operations or CX
Familiarity with LLMs, prompt engineering, or AI product documentation
Light design sensibility for diagrams, flowcharts, and screenshot annotations
Experience contributing to developer-focused docs (OpenAPI specs, SDK references, integration guides)

Tooling

Docs platform: open to recommendations, currently a mix of Notion and a hosted docs site
Product surfaces you'll document: Next.js admin app, Hono APIs, Zendesk app, embeddable widget, workflow engine
Collaboration: Slack, Linear, Loom, GitHub

Compensation

Competitive hourly rate or monthly retainer, based on experience. Approximately 20 hours per week with flexibility on schedule. Possible path to full-time as the team grows.

Location

Remote-friendly. Based in Michigan with a distributed team. US time zones preferred.