Product and release documentation: Release notes, upgrade guides, compatibility information, and operational content that customers and integrators depend on. The current state is a starting point, not the bar.
Copilot knowledge architecture: Structure and maintain the source of truth that feeds AI-generated answers. Own accuracy. Catch errors before users do.
In-product guidance: Contextual help, onboarding flows, and error states written to resolve questions without escalation.
Developer and integrator surface: API docs, hardware integration guides, and SDK references are clear enough that a new integrator reaches first success without opening a support ticket.
Content-as-signal: Track what users search for, escalate, and struggle with. Feed that back into content priorities and product decisions.
Voice and editorial standards: Define how FORT communicates technically and apply that standard consistently across every surface.

A portfolio that shows range: Docs, in-product copy, API references, video scripts, interactive guides. Something that shows you treat format as a deliberate choice.
Experience with technical platforms: Hardware, developer tools, industrial automation, or safety-critical systems. An understanding of what it means to get it wrong.
AI in your daily workflow: Not as an experiment. As a core part of how you work. You can describe your process.
Strong editorial instincts: You have pushed back on engineers who wanted to ship a spec dump instead of a clear explanation. You have examples.

Technical Product Content Lead

Key skills