FORT Robotics - Technical Product Content Lead

• Obsessively clear: You write one sentence where others write three paragraphs. You know when to cut. • Obsessively clear: • 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. • Creative before compliant: • 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. • AI-native: • 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. • Technically grounded: • Safety-conscious by instinct: FORT operates in physical environments where a wrong answer has consequences. You carry that standard without being reminded. • Safety-conscious by instinct: • 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. • 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.