Need help? Reach out to us
Back to library

Indian SaaS and B2B products

Solutions Infini Technical Writer Interview: Rounds, Questions and Preparation

For Technical Writer roles at companies like Solutions Infini

Share with friends

Preparing together? Send them this role's questions.

https://www.cynchrony.in/library/solutions-infini-technical-writer

What the job involves

A technical writer in Indian SaaS and B2B products creates user guides, API documentation, help articles, and release notes for software used by businesses. The role involves working closely with product managers, engineers, and support teams to translate complex features into clear, accurate content. Day to day, you may update docs for a new feature, review UI text, or improve existing articles based on customer feedback.

Role and technical knowledge

  1. 1

    What is the difference between a user guide and API reference documentation?

    A strong answer explains that user guides are task-oriented for end users, while API references are structured for developers with endpoints, parameters, and examples.

  2. 2

    How would you document a new webhook feature for a B2B SaaS product?

    Cover the event types, payload structure, authentication, retry logic, and a sample request/response, plus where to place it in the docs.

  3. 3

    What is docs-as-code and why do many SaaS companies use it?

    Explain writing in Markdown, storing in Git, reviewing via pull requests, and publishing through static site generators for version control and collaboration.

  4. 4

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

    Focus on user impact, new features, bug fixes, breaking changes, and clear action items, avoiding internal jargon or overly technical details.

Practical scenarios

  1. 5

    You have to document a complex feature with no existing specs. How do you start?

    Describe interviewing the product manager and engineers, using the product yourself, creating a draft outline, and iterating with reviewers.

  2. 6

    A developer says your documentation is wrong but does not explain why. What do you do?

    Show that you ask specific questions, reproduce the issue, check with support or other engineers, and update the docs with clear examples.

  3. 7

    How would you improve an existing help article that has high support ticket volume?

    Mention analyzing tickets, rewriting for clarity, adding screenshots or steps, and testing with a colleague or customer to confirm it solves the problem.

  4. 8

    You need to document an API endpoint but the engineer is busy. How do you proceed?

    Suggest using the API yourself, checking code comments or Swagger files, writing a draft, and then asking for a quick review rather than blocking.

Behavioural and collaboration

  1. 9

    Tell me about a time you had to explain something technical to a non-technical person.

    Use a project or college example, highlight simplifying without losing accuracy, and mention the outcome or feedback you received.

  2. 10

    How do you handle tight deadlines when multiple product teams need documentation?

    Show prioritization based on release dates and user impact, communicating trade-offs, and possibly delivering a minimal viable doc first.

  3. 11

    Describe a situation where you received critical feedback on your writing.

    Focus on how you listened, asked clarifying questions, revised the content, and improved your process for next time.

  4. 12

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

    Connect your interest in technology and clear communication, mention the fast-paced learning environment, and show curiosity about B2B products.

HR and motivation

  1. 13

    What do you know about our company and the products we build?

    Research the company's SaaS offerings, target customers, and recent news, and relate it to why you want to write for their users.

  2. 14

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

    Mention following style guides, reading other SaaS docs, practicing with tools like Markdown or Git, and taking feedback seriously.

  3. 15

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

    Show a growth path such as owning a product area, mentoring juniors, or specializing in API or developer documentation.

  4. 16

    What are your salary expectations for this role?

    Give a reasonable range based on research for fresher technical writers in Indian SaaS, and express flexibility and eagerness to learn.

Ready to try it for real?

Take a timed test or talk through a mock interview for this role, then see your scores.

This is practice material for Technical Writer roles, written with AI. It is not a list of questions Solutions Infini or any other company has asked.