Technical Writer - API Platform

About the Role

WSO2's API Management Business Unit is looking for an engineer who loves to write. This is not a traditional technical writing role solely focused on product documentation or step-by-step walkthroughs. We need someone with real software development experience who can take complex topics in the API management and AI space and turn them into compelling, developer-friendly blog content (for our blog and external partner blogs) that our audience actually wants to read.

You'll be writing about things like API gateway architecture, AI-powered integration patterns, the evolution of developer platforms, and how engineering teams are solving real problems with WSO2's technology. The goal is content that earns respect from developers and architects people who can tell immediately whether the author understands what they're talking about. You need to be that author.

This role sits within the product marketing team, working closely with engineering, developer relations, and product leadership. You'll have access to the people building our platform and the customers using it. What we need from you is the ability to synthesize that into written content that is technically rigorous, clearly expressed, and genuinely useful to a developer audience.

Key Responsibilities

Technical Blog Content and Thought Leadership

• Write in-depth technical blog posts, articles, and thought leadership pieces that explore API management, AI integration, developer platforms, and cloud native architecture from an engineering perspective.
• Take complex technical concepts (e.g., API lifecycle management, service mesh patterns, event-driven architectures, or AI/MCP integration) and make them accessible and engaging for a developer audience.
• Research and develop content around industry trends, emerging patterns, and technical challenges in the API and AI ecosystem, positioning WSO2 as a credible voice that developers trust.
• Create content that supports WSO2's product-led growth motion by demonstrating the value of our platform through real technical depth, not marketing fluff.

Engineering-Informed Writing

• Draw on your own software development background to write with credibility. You should be comfortable spinning up an API, reading through a codebase, or working through an integration scenario yourself before writing about it.
• Build and test code samples, example integrations, and proof-of-concept projects that accompany your written content, ensuring everything you publish actually works.
• Collaborate with WSO2's engineering teams to understand new features, architectural decisions, and technical trade-offs at a level that lets you write about them with authority.
• Stay hands-on with WSO2's products (particularly our API management platform and Choreo) so your content reflects real, current experience rather than secondhand summaries.

Content Strategy and Developer Engagement

• Partner with product marketing and developer relations to identify high-impact content topics that align with WSO2's go-to-market strategy and resonate with our developer audience.
• Analyze what's working. Track content performance, developer engagement, and community response to continuously refine the topics, formats, and angles that land best.
• Contribute to the broader content calendar, helping shape a consistent publishing cadence of technical content that builds WSO2's reputation in the API and AI space.
• Engage with developer communities, forums, and social channels to understand what developers are talking about, struggling with, and curious about. Then, write content that meets them there.

Cross-Functional Collaboration

• Work closely with product managers and engineers to get early access to upcoming features and architectural changes, turning those into timely, well-informed content.
• Partner with the DevRel team to ensure alignment between community-facing content, technical evangelism efforts, and the blog's editorial direction.
• Support product launches by creating technical content that helps developers understand not just what's new, but why it matters and how to use it.
• Contribute your engineering perspective to broader marketing initiatives, helping ensure that messaging, positioning, and campaign content is technically accurate and resonates with a developer audience.

Qualifications and Skills

• A background in software engineering or computer science, whether through a degree, bootcamp, or professional experience. You should have built software, not just written about it.
• At least 1  year of professional experience in software development.
• 1-3 years of professional experience in technical writing, developer advocacy, or a combination. Recent graduates with strong engineering fundamentals and a demonstrated passion for writing are encouraged to apply.
• Hands-on experience with APIs (building them, consuming them, debugging them). Familiarity with REST, GraphQL, gRPC, or event-driven architectures is expected.
• Proficiency in at least one programming language (Java, Python, JavaScript/TypeScript, Go, or similar) and comfort navigating unfamiliar codebases.
• Strong written English and the ability to explain complex technical ideas in a way that is clear, precise, and engaging. We'll ask for writing samples.
• Genuine interest in the API management, AI, and developer tools space. You should be someone who reads engineering blogs, follows industry trends, and has opinions about developer experience.
• Familiarity with Git, Markdown, and modern content workflows. Experience with static site generators or CMS platforms is a plus.
• Understanding of API specifications (OpenAPI/Swagger, AsyncAPI) and developer tooling (Postman, cURL, API gateways) is a plus.
• Comfort working in a globally distributed team with asynchronous communication across time zones.

Nice to Haves

• A personal technical blog, published articles, or open source contributions that showcase your writing and technical thinking.
• Experience with or exposure to API gateway platforms, integration middleware, identity and access management, or cloud-native development.
• Familiarity with AI/ML concepts, particularly as they relate to API orchestration, intelligent automation, or AI-powered developer tools.
• Experience creating or a strong interest in learning how to produce developer-focused video content like screen-recorded walkthroughs, explainer videos, demo recordings, or similar formats that bring technical topics to life beyond the written word.
• A desire to present and run technical webinars based on the topics you write about, engaging directly with developer audiences in a live format and representing WSO2 as a knowledgeable, approachable voice in the API and AI space.
• Familiarity with SEO principles, keyword research, and organic content performance reporting. This is not a prerequisite (you'll learn these as part of the role) but any existing exposure is a head start.