Technical writing services
Technical writing services for software companies: API references, developer guides, user documentation, runbooks and release notes, written as code beside the product and kept current with every release.
What our technical writers do
API documentation
Reference generated from your OpenAPI or GraphQL schema, with getting-started guides, authentication walkthroughs and runnable examples written around it, so the reference is never edited by hand.
Docs as code
Documentation in Markdown in your repository, reviewed in pull requests like code and published with Docusaurus, Starlight or a similar generator by the same pipeline as the product.
User guides and help centres
Task-based guides and help-centre articles organised by what the reader is trying to do, split into tutorials, how-to guides, reference and explanation along the Diátaxis framework.
Runbooks and operations guides
Step-by-step procedures for deployments, restores, incident response and on-call, tested by someone who did not write them.
Release notes and changelogs
Release notes that tell users what changed for them, and changelogs for integrators, drafted from merged pull requests and checked against the release.
Style and quality checks
A style guide and terminology list enforced by Vale in the pipeline, with broken-link checks on every build, so consistency does not depend on one reviewer.
Hire technical writers
Full time in your team
Technical writers who work your hours in your tools and meetings and report to your lead, with the Ukrainian contract, payroll and leave on our side.
Part time or fractional
Technical writers for a set number of days a week, when the work is real but not yet a full-time role.
For a project or a launch
Technical writers for a defined stretch of work, from the first week to the handover, with the end date agreed up front.
The dedicated team page explains how specialists join your team, and the outsourcing page covers project delivery, take-overs and how we charge.
Who our technical writers work with
Engineers and technical leads
Interviews, reviews and technical accuracy
Product managers
Features, audiences and release scope
Support engineers
The questions users actually ask
UI and UX designers
Interface text and diagrams
How our technical writers work
Documentation lives where the code lives: in the repository, reviewed in the same pull request as the change it describes, and built and published by the pipeline. A feature is done when its documentation has merged, which keeps the documentation as current as the code.
Writing starts from the reader: who they are, what they are trying to do and what they already know. Support tickets and search terms show where the current documentation fails, and those pages are fixed first.
Other roles we staff
Project managers
Project management for software delivery: IT project and delivery managers who own plans, scope, risks, budgets and weekly reporting, full time in your team, part time or for a single project.
Business analysts
Business analysis for software projects: discovery, requirements, user stories, BPMN process maps and acceptance criteria, from business analysts full time in your team, part time or for a project.
Product managers
Product management for software products: product managers and product owners for discovery, roadmaps, backlogs and product metrics, full time in your team, a few days a week or for a launch.
Scrum masters
Scrum masters and agile coaching for software teams: Scrum and Kanban, flow metrics, impediments removed and retrospectives that change something, full time in your team, part time or for a set period.
Technical support
Technical support services for software products: first and second line support engineers in your help desk, under your brand and in your customers' hours, full time, part time or for a launch.
IT recruitment
IT recruitment services for companies building their own teams: role briefs, sourcing, screening and technical interviews by working engineers, from IT recruiters in your team or for a hiring push.
Customer success
Customer success management for SaaS and subscription products: customer success managers for onboarding, adoption, health scores, QBRs and renewals, full time in your team, part time or for a launch.
Questions about hiring technical writers
Can a technical writer document a system nobody has documented?
Yes. The writer reads the code and the configuration, interviews the engineers, and produces an architecture overview, runbooks and a glossary, reviewed by the people who run the system. It is the same read-only first step our take-overs of inherited systems start with.
How do you keep API documentation in step with the API?
The reference is generated from the OpenAPI or GraphQL schema in the build, so it cannot drift from the API. The writer adds what a generator cannot: the getting-started guide, the authentication walkthrough and the examples a developer needs before the reference is useful.
How quickly can technical writers start?
When the right technical writer is available, the start is gated only by your interview and the NDA and IP assignment. Otherwise we run a search, which typically produces candidate profiles within two to three weeks, and nobody starts until you have said yes.
How do we hire technical writers through BigTree108?
Tell us the work, the seniority and the hours you need. We propose one or two people with their profiles, you interview them the way you would interview your own hire, and you sign one agreement with BIG TREE 108 LLC and receive one invoice a month.
Who owns the work they produce?
You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.
Is your documentation behind the product?
Tell us the product, its readers and where the documentation lives now. You get an answer within one business day: candidate profiles or a documentation plan.