Technical Enablement Lead

As our Technical Enablement Lead, you'll own two adjacent programs end-to-end: customer-facing product documentation and technical enablement for our internal engineering organization and our customers. You'll partner closely with engineering, customer success, and product to make sure our docs and enablement scale with the product.

Responsibilities

• Technical Enablement

  • Own technical enablement as a program, internal and external, making sure great enablement exists, stays current, and scales.

  • Design and maintain onboarding and ramp materials for engineers joining Zeromatter.

  • Build lightweight, just-in-time enablement for engineers as the platform changes.

  • Partner closely with Customer Success to design, build, and maintain external enablement materials as we scale our customer base.

• Product Documentation

  • Own customer-facing documentation as a program, end-to-end.

  • Build deep enough product understanding to write authoritatively, and interview engineering teams to fill the gaps.

  • Get our documentation current and keep it current as the product evolves.

  • Own release notes every release cycle, and fold them back into the broader documentation set so docs don't drift.

  • Set the standards, structure, and review process for anything customer-facing

  • Design documentation that serves both human readers and AI agents, using structured Markdown, clear source-of-truth pages, and reference materials developed with engineering and product.

Qualifications

• Experience with simulation, autonomous vehicles, or an adjacent domain. You can hold your own in technical conversations with simulation, ML, and rendering engineers without needing everything translated.

• Experience designing and running enablement programs for technical audiences (engineers, customer engineers, or both). You know what good looks like, and you have opinions on how to make enablement stick.

• Experience owning or writing product documentation at a tech company. You write clearly and tightly, have strong views on docs structure and tooling, and know how to extract information from busy engineers.