Technical Documentation Writer

Other Jobs To Apply

This is not a traditional technical writer role. You will act as the architect and operator of our documentation ecosystem, ensuring accuracy, usability, technical depth, and a developer-first experience. You will work closely with product and engineering teams and leverage modern AI-assisted tools such as Cursor to accelerate documentation creation, code validation, API examples, and ongoing updates. You will define how customers, partners, and internal teams document.


The candidate will have responsibilities across the following functions:


Documentation Portal Ownership:

  • Own the full documentation lifecycle: structure, content, publishing, governance, and updates.
  • Design and maintain a scalable documentation architecture (conceptual guides, API docs, integration docs, release notes, tutorials).
  • Ensure documentation aligns with product releases and roadmap changes.
  • Manage versioning strategy across product releases.


Developer and API Documentation:

  • Create and maintain high-quality API references, integration guides, configuration documentation, architecture overviews, and troubleshooting playbooks.
  • Work closely with engineers to validate examples, SDK snippets, and data pipeline configurations.
  • Ensure clarity for DevOps, SecOps, and data engineering personas.


AI-Assisted Documentation (Cursor-Driven Workflow):

  • Use the cursor to: Generate structured drafts from PRDs and code. Validate API schemas and payload examples. Auto-generate usage examples from source code and refactor and standardise documentation tone and formatting. Identify outdated content across repositories.
  • Implement AI-assisted workflows for ongoing doc maintenance and release synchronisation.


Release and Change Management:

  • Publish clear, structured release notes for every product update.
  • Track feature changes and ensure documentation parity with engineering delivery.
  • Coordinate with product managers for launch readiness.


Documentation Experience and Tooling:

  • Evaluate and manage documentation platforms (e. g., modern static site generators or doc platforms).
  • Optimise searchability, navigation, and developer experience.
  • Define documentation style guides and contribution workflows.
  • Enable internal teams to contribute effectively.


Requirements:

  • Bachelor's degree in computer science, engineering, or a related field.
  • 7+ years in technical documentation, developer documentation, or documentation engineering.
  • Experience with security data platforms and SIEMs.
  • Strong understanding of APIs, distributed systems, and cloud-native architectures.
  • Experience documenting infrastructure, platform, or B2B SaaS products.
  • Hands-on experience using AI-assisted coding tools such as Cursor.
  • Ability to read and understand production-level code.
  • Excellent written communication skills.


Preferred Qualifications:

  • Familiarity with high-volume or streaming data pipelines.
  • Experience with observability systems.
  • Experience working with AWS, GCP, or Azure.
  • Experience managing docs-as-code workflows (Git-based).
  • Prior startup experience in infrastructure or security.
Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...