Technical Writer
Posted 18 Sep 2026
Advertised as “Associate Technical Writer”
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 0–2 yrs
- Management level
- Individual contributor
- Employment
- On-Site
- Contract
- Full-time
No salary listed for this role.
About Hevo:
Hevo is a no-code Data Pipeline platform trusted by 1,000+ companies globally, including Postman, Shopify, Doordash and Gartner. Backed by $42M from Peak XV Partners and Chiratae Ventures, we power the data infrastructure of companies that move fast.
We are consistently rated #1 on G2 in the ETL and Data Integration category (4.5+ rating) and are a Snowflake Premier Partner. Our product is in the market, loved by customers, and now entering its next growth phase.
With 600+ US customers already on the platform and a product that has matured significantly over the last two years, this is the ground-floor moment. Before the team scales, before the brand becomes obvious. The upside is real and uncapped.
About the Role:
We're looking for an Associate Technical Writer who's comfortable working in a docs-as-code environment and can partner with AI tools (e.g., Claude) for all aspects of the work — not just writing, but operating within an automated documentation pipeline.
This is an opportunity to own documentation end-to-end within a modern, AI-assisted workflow, working closely with engineering, product, and support stakeholders to keep a shared source of truth accurate and consistent.
What You'll Do:
-
Create and maintain user documentation using a docs-as-code workflow — Markdown/YAML source files, Git-based version control, and CI-driven publishing (e.g., Jekyll).
-
Independently own small documentation tickets and projects end-to-end, from research through PR merge.
-
Use AI-assisted tools (Claude or equivalent) to draft, summarize, restructure, or QA content, while critically reviewing and editing AI output rather than publishing it as-is.
-
Conduct research and gather technical information from product specs, engineering discussions, and existing docs to fill knowledge gaps.
-
Follow and help enforce documentation standards, style guides, and metadata conventions (e.g., structured fields for error messages, FHS-style rule sets) across a shared source of truth.
-
Work in Git-based workflows: branching, raising PRs, responding to review comments, and triggering automation for doc builds/publishing.
-
Collaborate with engineering, product, and support stakeholders to validate technical accuracy before publishing.
-
Flag ambiguous, unverified, or inferred content rather than publishing unconfirmed information.
What We're Looking For: