Qandle Technical Writer Interview: Rounds, Questions and Preparation

What the job involves

A technical writer in Indian SaaS and B2B products creates user guides, API docs, help articles, and release notes that help customers and internal teams understand complex software. You will work closely with product managers, engineers, and support teams to translate features into clear, accurate, and concise content. The role demands strong writing, editing, and tooling skills, plus the ability to learn fast in a fast-growing environment.

Role and technical knowledge

1. 1

   What is the difference between a user guide, a help article, and API reference documentation in a SaaS product?

   Explain purpose, audience, and format. User guide is task-oriented for end users, help article is short and searchable for specific problems, API reference is for developers with endpoints and parameters.

2. 2

   How would you document a new feature like an employee attendance dashboard for a B2B HR tool?

   Cover structure: overview, prerequisites, step-by-step instructions, screenshots or GIFs, and common errors. Mention checking with PM and support for edge cases.

3. 3

   What do you know about REST APIs and how would you document an endpoint?

   Mention HTTP methods, URL, request headers, query parameters, request body, response codes, and example JSON. Show you can read API specs or use tools like Postman.

4. 4

   Which tools have you used for writing and publishing documentation?

   Name specific tools like Markdown, Git, Confluence, Zendesk, or static site generators. Explain how you used them, even in college projects or internships.

Practical scenarios

1. 5

   You are asked to document a feature that is still in development and the engineer is too busy to explain it. What do you do?

   Show initiative: check existing specs, tickets, or prototypes, ask specific questions, and propose a draft for review. Emphasise asynchronous communication and not blocking others.

2. 6

   A customer complains that your help article is outdated after a UI change. How do you handle it?

   Acknowledge the issue, verify the change, update the article, and add a process to prevent it, like linking docs to release notes or setting review reminders.

3. 7

   How would you write release notes for a bug fix that only affects a small set of users?

   Be transparent but concise. State what was fixed, who is affected, and any action needed. Avoid jargon and keep it scannable.

4. 8

   You need to explain a complex billing cycle to non-technical HR managers. How do you simplify it?

   Use analogies, a step-by-step flow, and a simple diagram. Avoid technical terms and focus on what the user needs to do and when.

Behavioural and collaboration

1. 9

   Tell me about a time you had to explain something complicated to someone who was not technical.

   Use the STAR method. Highlight how you assessed their knowledge, chose the right level of detail, and checked understanding.

2. 10

   Describe a situation where you received critical feedback on your writing. How did you respond?

   Show you are open to feedback, ask clarifying questions, and revise. Mention a specific change you made and the result.

3. 11

   How do you prioritise your work when multiple teams ask for documentation updates at the same time?

   Talk about impact, deadlines, and dependencies. Mention communicating with stakeholders and using a simple prioritisation framework.

4. 12

   Why do you want to work as a technical writer in a fast-growing SaaS company like Qandle?

   Connect your interest in simplifying complex products, learning new technologies, and working in a collaborative startup environment. Show you understand the sector.

HR and motivation

1. 13

   What do you think are the biggest challenges for a technical writer in a small SaaS company?

   Mention wearing multiple hats, keeping up with rapid releases, and limited resources. Show you are adaptable and proactive.

2. 14

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

   Show growth in skills like information architecture, API docs, or team leadership. Align with the company's need for scalable documentation.

3. 15

   How do you keep your writing skills sharp and stay updated with documentation trends?

   Mention reading blogs, following communities like Write the Docs, taking courses, and practising by documenting personal projects.

4. 16

   What are your salary expectations for this role?

   Research typical fresher salaries for technical writers in Indian SaaS. Give a range and say you are open to discussion based on overall fit and learning opportunities.