Hubilo Technical Writer Interview: Rounds, Questions and Preparation

What the job involves

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

Role and Technical Knowledge

1. 1

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

   Explain that user guides are task-oriented for end-users, while API references are for developers and list endpoints, parameters, and responses. Mention that both are needed for different audiences in B2B SaaS.

2. 2

   How would you document a new feature that has no existing documentation, from scratch?

   Outline steps: interview product and engineering, test the feature yourself, create an outline, write a draft, get reviews, and publish. Emphasize starting with user goals and use cases.

3. 3

   What is DITA, and why might a SaaS company use it for documentation?

   DITA is an XML-based standard for structured authoring that enables content reuse and multichannel publishing. SaaS companies use it for consistency and scalability across products.

4. 4

   Explain how you would write a release note for a bug fix versus a new feature.

   Bug fix notes are brief, focus on what was broken and what is fixed, and may include workarounds. New feature notes explain the benefit, how to use it, and link to detailed docs.

Practical Scenarios

1. 5

   You are asked to document an API endpoint, but the engineer gives you incomplete information. What do you do?

   Describe how you would ask specific questions, test the endpoint using tools like Postman, and cross-check with existing code or Swagger files. Highlight proactive communication and verification.

2. 6

   A product manager wants to publish documentation for a feature that is still in beta. How do you handle it?

   Suggest labeling the docs as beta, adding a disclaimer, and setting up a process to update them when the feature changes. Mention coordinating with the PM on timelines and review cycles.

3. 7

   You notice that existing help articles are outdated and causing support tickets. How would you prioritize updates?

   Propose analyzing support ticket data, identifying high-traffic articles, and creating a content audit schedule. Emphasize collaboration with support and using analytics to prioritize.

4. 8

   How would you structure documentation for a product with multiple user roles, such as admin, manager, and end-user?

   Explain creating separate sections or guides per role, using clear navigation, and avoiding duplication with reusable content. Mention considering search and filtering by role.

Behavioural and Collaboration

1. 9

   Tell me about a time you had to explain a complex topic to someone non-technical. How did you ensure clarity?

   Use a specific example, such as a college project or internship, and describe how you simplified jargon, used analogies, and checked for understanding. Highlight empathy for the audience.

2. 10

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

   Show openness to feedback, describe how you incorporated it, and mention any process you now follow to improve, like peer reviews or style guide checks.

3. 11

   How do you handle disagreements with a subject matter expert about the accuracy of documentation?

   Emphasize respectful discussion, referring to evidence like product behavior or official specs, and escalating if needed. Focus on the goal of accurate, user-friendly content.

4. 12

   Give an example of a time you managed multiple deadlines. How did you prioritize?

   Use a real example from academics or internships, and explain how you assessed urgency and impact, communicated with stakeholders, and used tools like calendars or task boards.

HR and Company Fit

1. 13

   Why do you want to work as a technical writer in a SaaS company like Hubilo?

   Show interest in SaaS and B2B products, mention the challenge of simplifying complex software, and connect to your skills. Avoid generic answers about loving writing.

2. 14

   What do you know about our product and how would you approach learning it?

   Demonstrate basic research about the company's product, then outline a plan: read existing docs, use the product, talk to users, and ask questions. Show initiative.

3. 15

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

   Focus on growing into a subject matter expert, leading documentation projects, or specializing in API or developer docs. Align with the company's needs.

4. 16

   How do you stay updated with trends in technical writing and SaaS?

   Mention following blogs, communities like Write the Docs, taking courses, and experimenting with tools. Show curiosity and continuous learning.