Technical Product Content Lead

Job Description

Job Description

In today's dynamic worksites, seamless collaboration between people and machines is essential. FORT's platform ensures safe, secure, and dynamic control that surpasses legacy systems and next-generation AI capabilities.

While autonomous machines offer significant advantages, they also introduce new safety challenges. FORT addresses these concerns by providing solutions such as the Wireless E-Stop, which allows operators to instantly stop any machine from a safe distance, enhancing safety during emergencies.

Additionally, FORT's Safe Remote Control enables operators to manage heavy machinery remotely, reducing the risk of accidents and improving visibility.

By ensuring communications integrity across any network, FORT empowers customers to protect their most valuable assets—people, data, and machines—ensuring they remain safe and secure.

FORT is building a physical AI safety platform used by operators, integrators, and developers in real-world environments. The platform is growing fast, and the content layer has not kept pace. This role fixes that and then builds well ahead of it.

You will own everything from the foundational documentation that customers rely on today to the knowledge architecture that powers our AI Copilot as it ships. You will use AI heavily to work at speed and apply strong editorial judgment to make sure every output is accurate, clear, and useful.

What You Will Own

• 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.

Who You Are

• Obsessively clear: You write one sentence where others write three paragraphs. You know when to cut.
• Creative before compliant: You reach for the format that works — a decision tree, a short video, an interactive guide — before defaulting to a numbered list.
• AI-native: You use LLMs daily to draft, restructure, and pressure-test content. You know when to trust the output and when to rewrite it. Editorial judgment is the skill; prompting is just how you get there.
• Technically grounded: You can sit with hardware and firmware engineers, understand what they are shipping, and translate it accurately. You do not need to be an engineer, but you cannot be allergic to the details.
• Safety-conscious by instinct: FORT operates in physical environments where a wrong answer has consequences. You carry that standard without being reminded.

What Good Looks Like in Year One

• Documentation is no longer a liability: Customers and integrators can find accurate, current information without opening a support ticket.
• Copilot answers technical questions correctly: The AI Copilot handles common technical queries accurately. Support volume reflects it.
• Content ships with the feature: In-product guidance and Copilot context are ready on launch day, not weeks after.
• Content informs product decisions: You are in early design conversations, flagging where the experience will break down and where content will carry the load.

What You Bring

• 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.