At Lightning AI, docs aren't just a support function—they're a product surface. They're often the first real experience a developer has with our platform, and in a PLG motion, that means they directly drive activation, retention, and revenue.

We're looking for a Senior Technical Writer, Developer Experience who treats documentation that way: with product instincts, editorial craft, and the drive to own it end-to-end. 

This role is based in one of our U.S. office hubs (Seattle, NYC, or San Fran), with a minimum of 2 in-office days per week and occasional team and company offsites. We are not able to provide visa sponsorship for this position at this time.

What You'll Do

The docs product. Audit what exists, cut what doesn't serve developers, and build a roadmap for what's missing. You'll own information architecture, structure, and coverage across Lightning Studios (AI Dev Platform) and Lightning Deploy (Inference Platform) — each with a UI, SDK, and CLI.

The getting-started experience. Our PLG flywheel runs through docs. You'll own the entry point where developers go from zero to value, and you'll treat time-to-first-success as a metric worth optimizing.

Voice and editorial standards. You'll uphold the bar for how we write — across docs, landing pages, and technical blog posts — and work directly with Product and Marketing leadership to expand our presence.

Cross-functional execution. You'll sit close enough to code to be accurate and far enough out to write for humans. Engineers, product managers, designers — you'll extract what needs to be written and make it good.

Community content strategy. You'll build an approach to docs that scales beyond what we ship internally.

What We're Looking For

Required

• 5+ years of technical writing experience at a company where docs were treated as a product, not an afterthought
• Demonstrated experience owning developer documentation end-to-end — SDK references, CLI guides, API docs, getting started flows
• Comfortable reading code; you don't need to ship it, but you need to understand it well enough to explain it accurately
• Strong information architecture instincts — you have opinions on structure, progressive disclosure, and example density, and you can defend them
• Experience collaborating directly with engineering and product teams to extract, shape, and ship content on release timelines
• Proficiency with modern docs tooling (Mintlify, Docusaurus, ReadMe, or similar)
• Actively uses AI tools (Claude, Cursor, or similar) to accelerate writing, research, and content production — this isn't optional; it's how we expect this role to scale

Nice-to-Have

• Experience at a developer-led or PLG company where docs were a measurable part of the growth motion
• Familiarity with ML/AI tooling, inference platforms, or developer infrastructure
• Experience building or selecting docs tooling, not just using it
• Background in technical blogging, developer education, or community content
• Experience growing or mentoring a writing team

Compensation