ApplySarthi

Technical Writer

Hevodata

Tailor my CV for this job, freeView job and applyYour CV rewritten for this role, from your real experience. Sign in with Google, nothing to install.

Got this interview? Our apps help you get the job.

Skills named in this job

Read from the description itself, not inferred.

This role on the market

192 open writer roles across 97 companies are on ApplySarthi right now, most of them in Hyderabad (15), Bengaluru (14), Delhi NCR (2).

What writer roles keep asking for: Stakeholder management (18%), Git (16%) — counted across their open postings here.

Technical Writer jobs in India · Remote Technical Writer jobs · Confluence jobs · ETL jobs · Playwright jobs · Python jobs

Hevodata has 39 open roles listed here.

Counted across 14 company job boards, updated as roles open and close.

Preparing for this interview

Interviews for writer roles keep coming back to Stakeholder management, Git. Practise those questions before you sit with Hevodata.

Questions you are likely to be asked

  1. Why do you want to join Hevodata?
  2. What is your experience with ETL? Tell me one thing you learned the hard way.
  3. What is a weakness you are working on, and how?
  4. Tell me about yourself, and why this role is the right next step.
  5. Tell me about a problem you solved at work that you are proud of.

Prep Sarthi gives you a free mock interview: an AI interviewer asks you questions like these out loud, from your own CV and this job, and shows your score and your weakest answer.

Practise the Technical Writer at Hevodata interview free →

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.

Match this job to your CV

ApplySarthi scores your CV against this role, shows the skills you are missing, and writes a tailored version for the application.

Check my match →

Similar open roles

Need answers during your interview? Try Live Sarthi.

Live Sarthi, an Interview Sarthi app, shows answer suggestions during the call.

Try Live Sarthi free →

A Windows app, from the same team as ApplySarthi.

Listed on lever · posted 2026-11-17. ApplySarthi collects openings and links to application pages; the role is advertised by Hevodata, not by us.