Truecaller 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 center articles, API references, release notes, and onboarding guides. They work closely with product managers, engineers, and support teams to translate complex features into clear, accurate content for developers and business users. The role demands strong writing, editing, and information architecture skills, plus the ability to learn software quickly.

Role and technical knowledge

1. 1

   What is docs-as-code, and why is it useful for a SaaS company like a caller ID and spam detection app?

   Explain that docs live in the same repository as code, use version control, and are reviewed via pull requests. Mention benefits like consistency, faster updates, and collaboration with engineers.

2. 2

   How would you document a REST API endpoint for a new feature that lets business users verify phone numbers in bulk?

   Cover endpoint URL, HTTP method, authentication, request parameters, sample request and response in JSON, error codes, rate limits, and a short use case. Show that you understand OpenAPI or similar specs.

3. 3

   What is the difference between a help center article and an API reference, and when would you use each?

   Help center articles are task-oriented for end users, while API references are technical and structured for developers. Explain that both need different tone, format, and level of detail.

4. 4

   Which style guide do you prefer for software documentation, and why?

   Mention a common guide like Google or Microsoft, and highlight principles such as consistency, active voice, short sentences, and user-focused language. Show awareness that companies may have their own guide.

Practical scenarios

1. 5

   A product manager asks you to document a feature that is still in development. How do you proceed?

   Describe gathering information from specs, prototypes, and stand-ups, writing a draft, and setting up a review cycle with engineers. Mention using placeholders and updating as the feature evolves.

2. 6

   You notice that an existing help article has outdated screenshots and steps after a UI change. What do you do?

   Explain how you would verify the change, update the content, and check for related articles. Mention using analytics or support tickets to prioritise updates and setting up a regular review process.

3. 7

   How would you handle a situation where an engineer gives you incomplete or confusing information for a technical topic?

   Show that you would ask specific questions, request a demo or screen share, and cross-check with other sources like code comments or test cases. Emphasise patience and collaboration.

4. 8

   You need to write release notes for a minor bug fix and a major new feature in the same release. How do you structure them?

   Suggest grouping by impact, leading with the major feature, and keeping bug fixes brief. Mention using clear headings, user benefits, and links to detailed documentation.

Behavioural and collaboration

1. 9

   Tell me about a time you had to explain a complex topic to someone who was not technical.

   Use the STAR method. Focus on how you simplified the concept, checked understanding, and adjusted your language. Highlight patience and clarity.

2. 10

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

   Show that you welcome feedback, ask for specifics, and revise your work. Mention a concrete example and what you learned from it.

3. 11

   How do you prioritise your work when multiple product teams need documentation at the same time?

   Talk about assessing urgency, impact on users, and release dates. Mention communicating with stakeholders and using a simple prioritisation framework.

4. 12

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

   Connect your interest to fast-paced product cycles, continuous learning, and direct impact on user experience. Show enthusiasm for technology and clear communication.

HR and motivation

1. 13

   What do you know about our company and our products, and how does that relate to the technical writer role?

   Research the company's main products, target users, and recent news. Explain how clear documentation can improve user adoption and reduce support load for those products.

2. 14

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

   Show ambition to grow into areas like information architecture, API documentation leadership, or content strategy. Mention learning new tools and mentoring juniors.

3. 15

   How do you handle tight deadlines and last-minute changes in a product release?

   Emphasise flexibility, regular communication with the team, and keeping documentation modular so updates are quick. Give an example of staying calm under pressure.

4. 16

   What are your salary expectations for this role as a fresher?

   Research typical entry-level technical writer salaries in Indian SaaS companies. Give a reasonable range and express openness to the overall compensation package.