Professional Technical Content Writer Needed

I’m looking for a seasoned technical writer who can turn complex engineering knowledge into concise, developer-friendly documentation. The immediate need is to produce product documentation and user manuals aimed squarely at technical users—think software developers, DevOps engineers, and IT staff who dig straight into configuration files, logs, and code.

Scope
Our current gap is in the troubleshooting layer of the docs set. I need pages that walk readers through common error scenarios, surface root-cause analysis steps, and finish with clear, copy-pasteable fixes. Accuracy and clarity matter more than marketing polish; every paragraph should help an engineer resolve an issue in minutes, not hours.

Workflow & Tools
You’ll work from existing engineering notes, ticket histories, and source comments in Git. Markdown will be the primary format, pushed through our Docs-as-Code pipeline (GitHub + MkDocs). If you’re comfortable spinning up a local build to preview formatting, all the better.

Deliverables
• A structured troubleshooting guide for each major component (initial batch: 5 components)
• Inline code blocks, command examples, and log excerpts where relevant
• Cross-links to our existing setup and API reference pages
• A brief changelog entry for every pull request so our internal support team can track updates

Acceptance Criteria
• Steps reproduce the issue exactly on our staging environment
• Proposed fixes resolve the issue without introducing regressions (verified by CI)
• Writing style matches the current style guide (plain English, active voice, terse headings)

If you’ve shipped developer-oriented docs before and enjoy demystifying errors, I’d love to see a sample or two of similar troubleshooting content you’ve created.