Skip to content
Dropzone AI

Senior Technical Writer

Remote - US; United States - RemoteRemote · United States
Senior · Product
POSTED 28 SEPT
Apply Ask
Role
42 days opentrue age
Posted 28 Sept
Payats field
$140k–155kposted
▲ +9% vs market median $135k
$105k$170k
Market p25–p75
$105k–$170k
United States · n=3081 · 365d to 6 Nov
CompanyDropzone AI →
9open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
28,557open · Senior Other
Opened · 7d
+1,5355% of open
All other
623,739open
All tracked boards · live 10 Nov · n=28,557

About Dropzone AI

Dropzone’s mission is to scale cybersecurity beyond human limits, and augment every single human security engineer/analyst with an army of AI security specialists. Humans alone cannot sufficiently protect our digital future, and AI augmentation is the only way for defenders to reclaim the high ground. We are an award winning company disrupting the $200B+ cybersecurity market.

Powered by Gen AI advancements, our technology offloads repetitive day-to-day work and frees human analysts to focus on real threats and higher-value projects. We are venture-backed, and our team has a rare blend of deep experience across cybersecurity, AI/ML, and SaaS product development. Join us if you want to be on the ground floor of using Gen AI to transform cyber defense. Learn more at www.dropzone.ai.

About the role

We're looking for a Senior Technical Writer to own how Dropzone explains itself to the people who run it.

Dropzone's customers are security teams connecting dozens of signal sources, configuring investigation and hunting strategies, administering multi-tenant deployments, and deciding which response actions the AI SOC Team is authorized to take. Every one of those steps needs documentation a SOC analyst or platform admin can follow without opening a ticket. Your job is to move it into product documentation that customers trust and use.

You'll own the documentation system end to end: integration guides, admin and configuration docs, API reference, release notes, and the reference material that explains how Dropzone reasons, what evidence it presents, and where its limits are. You'll work directly with product, engineering, customer success, and sales engineering, and you'll report to the Head of Product.

This is not a role where you receive finished specs and format them. You'll sit with the trios as features are being built, pull the details out of engineers before they forget them, and be accountable for whether a customer can succeed on their own.

What you'll do

  • Own the customer documentation platform: information architecture, authoring workflow, review process, publishing, and search. Make it easy to find, easy to maintain, and accurate on the day a release ships.
  • Write and maintain integration guides for every supported data source and alert source, in a repeatable template that a new integration can fill in a day.
  • Write admin and governance documentation for enterprise and MSSP customers: tenant management, access control, API keys, audit trail, and response action authorization.
  • Own the API reference and developer-facing docs, working with engineering to keep them generated from source where possible and hand-written where it matters.
  • Write release notes that tell customers what changed, why, who benefits, and what the known limitations are. Every customer-visible release ships with documentation, not after it.
  • Write the explanatory material that helps customers understand and govern AI-completed work: how investigations are structured, how evidence and uncertainty are presented, what the system does and does not do.
  • Partner with customer success and support to find where documentation gaps generate tickets, and close them.
  • Establish a style guide and docs-as-code workflow that engineers and PMs can contribute to without you as a bottleneck.

Requirements

  • 5+ years of technical writing experience for software products with a technical buyer, with at least 2 years documenting APIs, integrations, or infrastructure-adjacent products.
  • Docs-as-code fluency: Git, Markdown, and at least one static documentation framework such as Docusaurus, MkDocs, Mintlify, or equivalent.
  • Ability to read code and API specifications well enough to document them accurately and to notice when the implementation disagrees with the spec.
  • A portfolio that shows you can explain a complex system to a practitioner under time pressure, with structure and precision rather than volume.
  • Comfort interviewing engineers and product managers to extract what actually happened, and the persistence to keep asking until the answer is complete.
Source · Dropzone AIFirst seen 7 NovOriginal ↗