Technical Writer at Hevodata, Bengaluru

Open. Posted .

Technical documentation for a data platform, spanning feature research, hands-on testing, AI-assisted drafting, and docs-as-code through merged PRs. You’ll work with engineers on a platform used by 2,000+ companies worldwide.

Apply on Hevodata's site for Technical Writer

Applying opens the employer's page. Want jobs like this sent to you each morning? Open Elip.

Key facts
LocationBengaluru, Karnataka
Work modeOn-site
Experience3–5 years
Job typeFull-time
PayNot stated by the employer
RoleWriter & Editor
Skills asked forTechnical Writing, APIs, Data Integration, OAuth, Markdown, YAML, Git, Claude
Posted17 Nov 2026

Elip's summary

Works as a technical writer for a company building data infrastructure for AI. Documents data integration features by testing product behavior, interpreting connector configurations and API references, and publishing docs-as-code with Markdown, YAML, and Git. Applies SQL and Claude to verify and improve documentation.

The job, in the employer's words

The Role

About Hevo

At Hevo Data, we’re building the future of data infrastructure for AI. Over 2,000 companies across 40+ countries trust Hevo to power their analytics. As a deep tech company, our engineering team solves some of the hardest problems in data integration, scale, and reliability.

We’re looking for a Technical Writer who goes beyond polishing prose. We want someone who tests the product hands-on, reads connector configs and API references, and verifies every documented behavior before it ships. You’ll use AI tools like Claude to work faster, and you’ll have the judgment to catch what AI gets wrong.

👉 If you can speak the language of engineers and turn complex data integration behavior into docs people trust, let’s talk.

What you’ll do

Own documentation for new features and Sources end-to-end, from reading connector configuration and specs through testing, review, and PR merge, with minimal supervision.

Test features in the product: create test accounts and data, run Pipelines, and verify the loaded data in the Destination (for example, with SQL), so every documented behavior is confirmed.

Read connector configuration (YAML/JSON), API references, and code, with AI help, to understand authentication, sync modes, delete handling, and rate limits.

Use Claude and Claude skills to draft, restructure, and QA large docs. Critically review the output for invented behavior, wrong links, and unsupported claims.

Review automation-generated drafts and their open flags, and confirm each point with Product or Engineering before publishing.

Automate repetitive content such as object tables, ERDs, link checks, and consistent screenshots instead of producing them by hand.

Raise clear engineering queries and bug reports, with steps to reproduce and expected versus actual results, and track them to closure in Jira and Confluence.

Work in Git: branch, raise PRs, resolve conflicts, run local builds, and respond to review comments.

Help evolve our documentation standards, templates, and style guides. When AI output repeatedly needs the same fixes, improve the prompts and skills behind it.

Review associate writers’ work and share effective research methods and prompts.

What you bring

3–5 years of technical writing experience, preferably for SaaS, API, or data products.

Strong written English and the ability to explain complex technical behavior simply and accurately.

Working knowledge of APIs and data integration concepts: OAuth and API key authentication, incremental and full loads, schemas, and primary keys.

Hands-on docs-as-code experience: Markdown, YAML, Git, and a static site generator (for example, Jekyll).

Daily, confident use of AI tools for research, drafting, and review, including creating and maintaining Claude skills and prompts.

The ability to read code and config files and write basic SQL queries.

The ability to set up test environments and test features end-to-end on your own.

The ability to manage several tickets in parallel, track dependencies on releases and engineering answers, and communicate status proactively.

Nice to have

Experience documenting ETL/ELT, data integration, or developer products.

Basic scripting (Python or shell) to automate documentation tasks.

Experience with ERD tools (for example, dbdocs) and browser automation for screenshots (for example, Playwright).

Why Hevo

Work on docs for a data platform used by 2,000+ companies worldwide.

Own your work from spec to merged PR, with real trust and autonomy.

Work in an AI-forward team that expects you to use, question, and improve the tools.

Collaborate directly with engineers solving hard problems in data integration, scale, and reliability.

About Hevodata

Headquartered in San Francisco, founded in 2017.

People in Elip's index who work here
249
Typical time at Hevodata
18 months
Typical career length so far
4.7 years

Largest teams

  • Engineering94 people
  • Sales16 people
  • Information Technology13 people
  • Customer Success and Support11 people

Totals from public professional profiles in Elip's index; any group under ten people is left out.

All open jobs at Hevodata

Similar open jobs

More jobs in Bengaluru or all jobs on Elip

About this page

Elip lists jobs that employers publish on their own careers sites, never copies from job boards. This one comes from Hevodata's listing on Lever, posted 17 Nov 2026. The summary is Elip's; the description is the employer's. When the job closes, this page says so.