Verloop Technologies Technical Writer Interview: Rounds, Questions and Preparation

What the job involves

A technical writer in Indian SaaS and B2B products creates user-facing documentation such as help articles, API references, onboarding guides, and release notes. They work closely with product managers, engineers, and support teams to translate complex features into clear, accurate content for business users and developers. The role also involves maintaining style guides, improving information architecture, and updating docs with every product release.

Role and Technical Knowledge

1. 1

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

   Explain the audience and purpose of each: user guides for end-to-end workflows, help articles for quick task-based answers, and API references for developers integrating with the product.

2. 2

   How would you document a new feature that has no existing documentation and only a rough product spec?

   Describe a process: read the spec, interview the PM or engineer, test the feature in a sandbox, draft a task-based article, and get a technical review before publishing.

3. 3

   What is docs-as-code and why is it useful for a B2B SaaS company?

   Cover writing in Markdown or reStructuredText, storing docs in Git, using pull requests for review, and automating builds so docs stay in sync with product releases.

4. 4

   How do you decide what to include in a release note for a B2B product?

   Focus on user impact, not internal ticket numbers: what changed, who it affects, how to use it, and whether any action is required. Keep it short and scannable.

Practical Scenarios

1. 5

   A support team says customers keep asking the same question about a confusing feature. How do you fix the documentation?

   Show that you would review the existing article, identify the gap, rewrite it with clearer steps and examples, and add it to the help center search or onboarding flow.

2. 6

   You have to document an API endpoint but the engineer is busy. What do you do?

   Suggest reading the OpenAPI spec, testing the endpoint yourself with Postman or curl, checking existing code comments, and scheduling a short review with the engineer later.

3. 7

   How would you handle a product update that changes the UI and makes several screenshots and steps outdated?

   Explain a triage approach: update high-traffic articles first, use a docs backlog, add version notes if needed, and set up a review process with the release manager.

4. 8

   A developer says your documentation is too basic. How do you respond?

   Show willingness to learn: ask what depth they need, add code samples, edge cases, and error handling, and consider separate quick-start and advanced sections.

Writing and Editing Skills

1. 9

   How do you make a technical concept easy for a non-technical business user to understand?

   Mention using analogies, avoiding jargon, breaking steps into short numbered lists, and leading with the user goal rather than the feature name.

2. 10

   What is active voice and why does it matter in technical writing?

   Active voice makes instructions direct and clear, for example 'Click Save' instead of 'The Save button should be clicked.' It reduces ambiguity for global users.

3. 11

   How do you maintain consistency across a large help center with multiple writers?

   Talk about a shared style guide, terminology list, templates, peer reviews, and using a linting tool or checklist before publishing.

4. 12

   Give an example of how you would rewrite a confusing sentence from a product spec.

   Pick a jargon-heavy sentence, identify the user action, and rewrite it as a short instruction or a simple explanation with a concrete example.

Behavioural and HR Questions

1. 13

   Tell us about a time you had to learn a technical topic quickly for a project or assignment.

   Use the STAR method: describe the topic, how you researched it, the resources you used, and the final output you delivered.

2. 14

   How do you handle feedback when an engineer or PM disagrees with your documentation?

   Show that you listen, ask clarifying questions, focus on the user's needs, and are willing to revise if the feedback improves accuracy or clarity.

3. 15

   Why do you want to work as a technical writer in a SaaS company rather than a traditional publishing role?

   Connect your interest to fast-paced product cycles, continuous learning, direct impact on user experience, and collaboration with engineering and product teams.

4. 16

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

   Mention growing into API documentation, information architecture, or leading documentation for a product area, while staying hands-on with writing.