DronaHQ Technical Writer Interview: Rounds, Questions and Preparation

What the job involves

A technical writer in Indian SaaS and B2B products creates clear, accurate documentation such as API references, user guides, tutorials, release notes, and knowledge base articles. You work closely with product managers, engineers, and support teams to translate complex features into simple, task-oriented content for developers and business users. The role also involves maintaining docs-as-code workflows, versioning, and continuously improving content based on user feedback.

Role and Technical Knowledge

1. 1

   What is the difference between a user guide and an API reference, and when would you write each for a B2B SaaS product?

   Explain that user guides are task-oriented for non-technical users, while API references are lookup-oriented for developers. Give a concrete example like onboarding a workflow vs. authenticating an endpoint.

2. 2

   How would you document a new feature that has both a no-code UI and a REST API?

   Cover separating audiences, linking UI steps to API equivalents, and using consistent terminology. Mention versioning and cross-references.

3. 3

   What is docs-as-code, and why do many Indian SaaS companies prefer it?

   Describe writing in Markdown, storing docs in Git, using pull requests and CI/CD for publishing. Highlight collaboration, version control, and faster releases.

4. 4

   How do you decide what to include in release notes versus a knowledge base article?

   Release notes announce changes briefly with impact and links. Knowledge base articles explain how to use or troubleshoot a feature in depth.

Practical Scenarios

1. 5

   You are asked to document an API endpoint but the engineer gives you only a Postman collection. What do you do?

   Explain how you would inspect requests and responses, ask clarifying questions, test the endpoint, and draft parameters, errors, and examples.

2. 6

   A support team reports that users keep asking the same question about a feature you documented. How do you fix it?

   Suggest reviewing the existing doc, improving search keywords, adding a quick-start or FAQ, and checking if the content is buried in the wrong section.

3. 7

   You have two days to document a new integration before launch. How do you prioritise?

   Focus on the critical path: authentication, core use case, common errors, and a working example. Defer edge cases and advanced configuration.

4. 8

   How would you handle a product manager who wants marketing language in technical documentation?

   Acknowledge the goal, explain that technical users prefer direct and accurate language, and propose keeping marketing copy on the website while docs stay neutral.

Writing and Editing Skills

1. 9

   How do you write for a developer audience versus a business user audience?

   Developers want code samples, parameters, error codes, and edge cases. Business users want outcomes, steps, and screenshots with minimal jargon.

2. 10

   What is your process for editing a first draft?

   Cover checking accuracy against the product, removing ambiguity, cutting fluff, verifying steps, and reading aloud for flow. Mention peer review.

3. 11

   How do you use screenshots and diagrams without making documentation outdated quickly?

   Use them only when they add clarity, keep them simple, and note the product version. Prefer text steps where possible and set a review cadence.

4. 12

   What makes a good error message in documentation?

   It states what went wrong, why, and how to fix it. Include the exact error text, likely causes, and a corrected example.

Behavioural and HR Questions

1. 13

   Tell me about a time you had to learn a complex topic quickly to explain it to someone else.

   Use a project, internship, or college example. Show your research method, who you asked, and how you simplified the final explanation.

2. 14

   Why do you want to work as a technical writer in a SaaS company rather than in other industries?

   Connect to fast release cycles, close collaboration with engineering, and the satisfaction of helping users solve problems at scale.

3. 15

   How do you handle feedback when an engineer says your documentation is incorrect?

   Show that you welcome corrections, ask for specifics, verify against the product, and update the doc while thanking the reviewer.

4. 16

   Where do you see yourself in two years as a technical writer?

   Mention deepening product and API knowledge, owning a documentation area, improving information architecture, and mentoring interns.