Help turn complex information into documentation people can actually use.

About the Role

We’re hiring a Documentation Specialist to help us organize information and turn it into clear, useful documents for client projects.

A lot of the information you’ll work with won’t arrive neatly organized. It may come from meeting notes, recorded calls, screenshots, existing files, internal workflows, or conversations with subject-matter experts.

Your job is to understand what is there, work out what is missing, and put the information together in a way that makes sense to the people who will use it.

What You’ll Be Doing

• Speak with clients and subject-matter experts to understand how their processes work.
• Review meeting notes, recordings, screenshots, files, and existing documentation.
• Create outlines before drafting larger documents.
• Write clear step-by-step procedures and instructions.
• Identify missing information, gaps, and unclear processes.
• Ask follow-up questions instead of making assumptions.
• Organize information so readers can find what they need quickly.
• Revise documents after internal or client feedback.
• Keep terminology, formatting, file names, and document versions consistent.
• Work with QA specialists, project managers, designers, and other documentation team members.

Documents You May Work On

• Standard Operating Procedures
• Process documentation
• Work instructions
• Policies and procedures
• Operations manuals
• Training documentation
• Employee guides
• Internal knowledge bases
• Business documentation

What We’re Looking For

Strong writing matters, but this job involves more than writing.

You should be comfortable looking at an unfamiliar process, learning how it works, and asking questions when the information you receive is incomplete.

• Excellent written English.
• Strong attention to detail.
• Ability to explain complicated information simply.
• Good interviewing and information-gathering skills.
• Strong organization skills.
• Ability to spot missing steps and inconsistencies.
• Comfortable managing several documents and deadlines.
• Ability to work independently and accept feedback.

Preferred Experience

Experience in technical writing, SOP development, process documentation, business documentation, knowledge management, or similar work is preferred.

Experience with tools such as Google Docs, Microsoft Word, Notion, Confluence, Lucidchart, Miro, or similar documentation platforms is useful.

About the Role

We’re looking for a Technical Documentation Specialist who can work comfortably with software products, APIs, developers, and technical teams.

You don’t need to be a full-time software developer, but you should be able to follow technical conversations, understand how systems work, and ask developers the right questions when something is unclear.

The goal is to create documentation that developers, customers, and internal teams can actually rely on.

What You’ll Work On

• API documentation
• Developer documentation
• Software documentation
• System documentation
• Integration guides
• Installation and configuration instructions
• User and administrator guides
• Troubleshooting documentation
• Technical SOPs
• Release notes
• Knowledge base content
• Internal engineering documentation

What You’ll Be Doing

• Work directly with developers, engineers, product teams, and technical SMEs.
• Understand how a feature, API, integration, or system works.
• Review existing documentation for outdated or missing information.
• Create clear documentation structures before drafting.
• Turn technical specifications into readable instructions.
• Review examples and procedures for accuracy.
• Keep terminology and formatting consistent.
• Update documentation as products and APIs change.
• Flag unclear technical information instead of guessing.

API Documentation Experience

For API-related projects, you should be comfortable reading and documenting:

• Endpoints
• HTTP methods
• Request parameters
• Headers
• Authentication
• Request and response bodies
• JSON examples
• Status codes
• Error responses
• Pagination
• Rate limits
• Webhooks
• Integration flows

Technical Background

You don’t need experience with everything below, but familiarity with several of these is a strong advantage:

• REST APIs
• HTTP
• JSON and XML
• OAuth and API keys
• Webhooks
• Git and GitHub
• Markdown
• YAML
• OpenAPI / Swagger
• Postman
• Databases
• SaaS platforms
• Basic command-line tools

Experience with GitBook, ReadMe, Docusaurus, MkDocs, Confluence, Notion, Jira, GitHub, or GitLab is also useful.

Sample Assessment

Shortlisted applicants may receive an API endpoint, JSON response, software workflow, or developer notes and be asked to create a short technical document.

We’ll look at technical understanding, accuracy, organization, clarity, completeness, and usability.

About the Role

We’re hiring a Documentation QA Specialist to review documentation before it is delivered to clients.

This is not a traditional software testing role. The focus is on the quality of the documentation itself.

You’ll review work produced by documentation specialists, technical writers, and subject-matter experts and check whether the final document is accurate, complete, consistent, and easy to use.

What You’ll Review

• Technical documentation
• API documentation
• Software documentation
• User guides
• Standard Operating Procedures
• Process documentation
• Policies and procedures
• Work instructions
• Operations manuals
• Training documentation
• Knowledge base articles
• Compliance and specialized documentation

What You’ll Be Responsible For

• Check whether instructions are complete.
• Identify missing steps and missing information.
• Find contradictions between sections.
• Review grammar, punctuation, spelling, and readability.
• Check headings, numbering, tables, labels, and formatting.
• Make sure terminology is consistent throughout the document.
• Compare documentation against available source materials.
• Check screenshots, diagrams, examples, links, and references.
• Review technical examples where applicable.
• Provide clear comments and revision requests to writers.
• Review revised versions before final approval.

What Good Documentation QA Looks Like

A document can be grammatically correct and still fail the person trying to use it.

That’s the type of issue we expect a Documentation QA Specialist to notice.

On technical projects, you may also catch issues such as an API parameter being described as required while the request example leaves it out.

What We Look For During QA

• Accuracy: Does the document match the actual process or source information?
• Completeness: Is important information missing?
• Clarity: Can the intended reader understand what to do?
• Consistency: Are terminology, formatting, and labels consistent?
• Structure: Is the information arranged logically?
• Usability: Can someone actually complete the task using the document?
• Presentation: Does the document look polished and professional?

What We’re Looking For

• Excellent written English.
• Exceptional attention to detail.
• Strong critical-thinking skills.
• Experience in documentation, editing, technical writing, proofreading, QA, or knowledge management.
• Ability to notice inconsistencies and missing information.
• Ability to give specific, useful feedback.
• Comfortable reviewing unfamiliar subjects.
• Ability to work across business and technical documentation.

Technical Experience

For software and API documentation projects, familiarity with the following is helpful:

• REST APIs
• JSON
• HTTP
• Swagger / OpenAPI
• Postman
• GitHub
• Markdown
• Confluence
• Notion
• Jira
• GitBook