The job in two lines
This role involves creating and maintaining user documentation in a docs-as-code environment, using AI tools for drafting, summarizing, and QA, and collaborating with various stakeholders to ensure technical accuracy.
Summary by Rezifi's AI, from Hevo Data’s posting. Years and pay appear only when the posting states them.
What you'd do
- Create and maintain user documentation using a docs-as-code workflow
- Own small documentation tickets and projects end-to-end
- Use AI-assisted tools to draft, summarize, restructure, or QA content
- Conduct research and gather technical information from product specs, engineering discussions, and existing docs
- Follow and enforce documentation standards, style guides, and metadata conventions
- 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
Skills it is built around
- markdown
- Git
- Docs as Code
- AI-assisted tools
Required
- YAML
- JSON
- Claude
- CI-driven publishing
- Jekyll
- AI writing/review tools
- product UI
- API Documentation
Nice to have
- JIRA
- Atlassian Confluence
- Slack
The facts
- Last checked
- Still listed on Hevo Data’s careers site.
- Posted
- 18 Sept 2026
- Hevo Data’s own date, never changed.
- Open to freshers
- Yes
- An entry-level role that names no years of experience.
- Experience
- Not stated
- The posting names no number of years.
- Pay
- Not stated
- The posting states no pay.
- Where you work
- Bengaluru (Bangalore), Karnataka
- Not listed as remote or hybrid.
- Level
- Not stated
- Field
- Technical writing
Questions about this job
When did you last check this job?
On 17 Nov 2026, 7:19 pm IST, when it was still listed on Hevo Data’s careers site. If we don't see it for 3 days, this page says so.
Can a fresher apply?
Yes. It is an entry-level role, and the posting names no years of experience.
Does it state the pay?
No. Hevo Data’s posting gives no figure, so we show none.
Is it remote?
The posting lists Bengaluru (Bangalore), Karnataka and does not say remote or hybrid.
What skills does it ask for?
markdown, Git, Docs as Code and AI-assisted tools.
The full posting
From Hevo Data’s careers site
As Hevo Data posted it. See the original
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:
-
Strong written English and ability to simplify technical concepts for end users.
-
Basic familiarity with Markdown, Git (clone/branch/commit/PR), and a willingness to use docs-as-code tooling.
-
Comfort using AI writing/review tools as part of a daily workflow (prompting, verifying, editing output), including the ability to create and manage Claude skills.
-
Ability to read and interpret product UI, API docs, or basic YAML/JSON structures well enough to document them.
-
Detail-oriented, especially around consistency (terminology, tone, formatting) across a large, distributed content set.
-
0-2 years of experience in technical writing, content, or a related field; internships or academic writing experience acceptable.
Bonus Points:
-
Exposure to a ticketing/PM tool (Jira, Confluence) and Slack-based collaboration.
-
Intermediate AI skills creation.