Startups · AI

Senior Technical Writer

Kong · New York, United States · Remote

← All jobs
About Kong

From APIs to AI, Kong is the fabric of modern connectivity. Centralize LLM access, automate API workflows, and secure your digital ecosystem at scale. Backed by Index, NEA and a16z.

About the role

Our docs get used in a few different ways. Some people land on a page in the middle of a task and just need the answer. Others are working out how to run Kong across a whole company, with real traffic and a lot of teams. The docs also power agent workflows, ours and our customers', like MCP servers and AI assistants. So when a page is wrong, it's wrong everywhere. Found on 1752vc Careers, the job board for startup and VC roles.

What they're looking for

  • You've worked alongside other technical writers on a docs team, not just with engineers or a manager, and you're comfortable giving and getting reviews
  • You've worked as a technical writer at a software company or a startup
  • Experience working with AI and AI-native workflows (building skills using MCP servers)
  • An understanding of how to test software, including APIs and command line tools, and hands-on experience doing it
  • Comfort working in the command line, and solid Git experience
  • Experience maintaining, managing, and reviewing docs in a docs-as-code environment
More about this role

If you don’t think you meet all of the criteria below but are still interested in the job, please apply. Nobody checks every box - we’re looking for candidates that are particularly strong in a few areas, and have some interest and capabilities in others.

Our docs get used in a few different ways. Some people land on a page in the middle of a task and just need the answer. Others are working out how to run Kong across a whole company, with real traffic and a lot of teams. The docs also power agent workflows, ours and our customers', like MCP servers and AI assistants. So when a page is wrong, it's wrong everywhere.

You'll own the docs for at least one product area, and you'll decide what to work on based on what you see. What features are releasing? Where are people getting stuck? What are the field teams hearing? You won't spend all your time in your area, though. You'll work with the other docs writers every day, check in with them when your work is done, ask for help when you're buried, and weigh in on each other's problems. You'll also work closely with product managers and engineers, and you'll be in their conversations early.

We own our docs platform, too. If a workflow...

Read the full posting on Kong's site ↗

All Cost Center

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.