Technical Writer

About the Role

You'll own the documentation layer of an AI-first procurement platform shipping at pace. Every feature that ships arrives documented, every release goes out with notes people can act on, and implementation consultants can take your documentation to an enterprise customer and use it as-is. You work with module owners, implementation, and support, and you set the standard for how this product explains itself. You report to the Head of Product.

What you'll drive

Documentation Coverage & Freshness

• Every shipped feature arrives documented, within days of release, against the release list.
• Keep existing documentation trustworthy as the product changes. A stale page is a support ticket waiting to happen.
• Own the documentation backlog: know what is missing, what is ageing, and what matters most.

Release Notes & Communication

• Release notes and documentation ready when the release ships, not after.
• Write internal and customer release communication that is clear and complete enough to act on without a follow-up call.
• Translate what engineering built into what a procurement team can do with it.

Working With Implementation & Customers

• Write for the people who use it: implementation consultants taking documentation into an enterprise account.
• Close the loop on where documentation failed them, and fix it at the source.
• Own the quality bar: documentation used as-is, with clarification the exception rather than the routine.

Craft & Standards

• Set the documentation standard for the product: structure, voice, depth, and when a screenshot earns its place.
• Use AI across research, drafting and revision, and build the prompts and patterns the team reuses.

You'll thrive here if

• 6–9 years writing technical documentation for a software product, ideally B2B or enterprise.
• You can read a PRD, try the feature, and write about it without being walked through it.
• You write for the reader's task, not the product's structure.
• You use AI as a core part of how you draft and revise, and know where it needs checking.
• You chase the ambiguity rather than documenting around it.
• Bonus: exposure to procurement, ERP, or complex workflow software.

What's In It For You

• Full ownership of how the product explains itself, with authority over the standard.
• Direct contact with implementation and enterprise customers, so you see where your writing lands.
• A direct line to the Head of Product, with no bureaucracy between your judgment and the decisions that matter.
• A culture where problem solving, ownership, and action are rewarded, and the opposite is called out.

Ready to build Aerchain's future

If reimagining business engines with AI and solving problems at scale excites you, let's talk. Apply now and help us build the most agile enterprise SaaS story in the world.