Are you ready to unlock intelligence?
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 could be better, you can build a better one. Add Vale rules, upgrade the platform, set up auto-generated docs. We have a docs engineer that can help you turn your needs into real features!
Own your product area
Own the documentation strategy for your area. That means getting into the product, seeing what's about to ship, deciding what needs writing, and planning the work. Share that plan with the docs team so everyone knows what's in motion. If something looks off, we'll sort it out together.
Work with product and field teams to find where a docs gap is blocking someone, and bring the data: user behavior, field feedback, adoption numbers. Who asked loudest shouldn't decide what gets written.
Sit in on product management discussions and say what you're seeing, so the docs and the product strategy stay in step.
Write it and test it
Write and edit how-to guides, reference documentation, and the pages that point people where they need to go, like landing pages and overviews.
Test everything you write. You're usually the first person outside engineering to use a new feature, so run the software, talk to the experts, and use the command line and API testing tools. If the steps don't work, the page isn't finished.
Review docs for technical accuracy and make sure they follow our guidelines.
Keep it all current
Maintain what's already published. Update it, revise it, and deprecate what's out of date.
Improve how we do docs, including document management and version control in Git, and help plan docs work so it ships on schedule.
Must have
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
About Kong:
Kong Inc., the AI Connectivity Company, is building the connectivity layer of AI. Trusted by the Fortune 500® and AI-native startups alike, Kong’s unified API and AI platform enables organizations to secure, manage, accelerate, govern, and monetize the flow of intelligence across APIs and AI traffic — on any model, any cloud. For more information, visit www.konghq.com.