Technical Writer (Part-Time)

amt; Valencia; On-site; VES 5,323,000 - 8,871,000; Part time

Job summary

amt is seeking a part-time Technical Writer to create and maintain clear, actionable documentation for our Reqcore product. You will craft setup guides, API docs, and troubleshooting playbooks to help recruiters, admins, and developers adopt features quickly.

You will improve onboarding for first-time teams and self-hosted deployments, standardize tone and structure, and document new releases and migrations with engineering and product teams. Attention to clarity and user intent is essential.

Qualifications

• 2+ years writing technical documentation for software products.
• Explain complex systems in simple, practical language.
• Strong Markdown/docs-as-code workflow habits.
• Attention to clarity, consistency, and user intent.
• Experience editing developer-facing and operations-focused content.

Responsibilities

• Create and maintain setup guides, API docs, and troubleshooting playbooks.
• Improve onboarding flows for first-time teams and self-hosted deployments.
• Standardize tone, structure, and quality across product documentation.
• Document new releases and migrations with engineering and product teams.
• Identify knowledge gaps from support and feedback loops.

Skills

Technical writing

API documentation

Markdown

Docs-as-code

Job description

We're hiring a part-time Technical Writer to make Reqcore documentation clear, actionable, and enterprise-ready. Your work will directly improve product adoption by helping recruiters, admins, and developers succeed quickly.

What you'll do

• Create and maintain setup guides, API docs, and troubleshooting playbooks
• Improve onboarding flows for first‑time teams and self‑hosted deployments
• Standardize tone, structure, and quality across product documentation
• Work with engineering and product to document new releases and migrations
• Identify knowledge gaps from support and feedback loops

What we're looking for

• 2+ years writing technical documentation for software products
• Ability to explain complex systems in simple, practical language
• Strong Markdown/docs-as-code workflow habits
• Attention to clarity, consistency, and user intent
• Experience editing developer-facing and operations-focused content
• Nice to have

Nice to have

• Open‑source documentation contributions
• Familiarity with hiring/recruiting software terminology