> Markdown version of [/jobs/ext/4671938-technical-enablement-lead](https://www.wearedevelopers.com/jobs/ext/4671938-technical-enablement-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Technical Enablement Lead - **Company:** Zeromatter Technologies Inc. - **Location:** Mountain View, CA, United States - **Experience:** Expert - **Salary:** $100,000 - $200,000 - **Contract:** Permanent contract - **Skills:** Markdown, Software Engineering, Agentic-AI - **Published:** November 11, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=e7fe126af24bd762 ## About the Role * 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. ## Description * 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.