Technical writer for public GraphQL API documentation

Developers integrating with our e-commerce inventory API currently rely on an auto-generated schema reference and a README, and our support inbox pays the price for it - roughly a third of tickets are questions the docs should answer. We are a 20-person company and nobody internally has time to fix this properly. The work: write a docs site's worth of content including a getting-started guide, authentication walkthrough, six task-based tutorials (syncing stock levels, handling webhooks, pagination patterns, error handling, rate limits, sandbox testing), and rewritten descriptions for our 40-odd GraphQL queries and mutations. You will have direct access to two backend engineers on Slack and a sandbox account to test every example you write - and we do expect every code example to be tested, not adapted from the schema. We estimate 10-15 hours a week over about two months. Writing samples of developer documentation you personally produced are required with your proposal; a portfolio site full of marketing blog posts will not be considered.