Technical Writing Intern

Technical Writing Intern, AuthPlane

Summer 2026, Remote

Reports to: Head of Growth / Product Lead
 Location: Fully remote
 Compensation: Paid / Unpaid
 Eligibility: Undergraduate students, any year

About AuthPlane

AuthPlane is a self-hosted OAuth 2.1 authorization server built specifically for MCP, the Model Context Protocol: the emerging standard for how AI agents connect to tools and data.

We give developers and security teams a spec-compliant way to add production-grade authentication to their MCP servers, especially in environments where cloud-hosted identity is not an option, such as regulated industries, on-premises deployments, and teams that want full control of their auth layer.

AuthPlane is open-source under AGPL-3.0, with no telemetry by default, and built for teams who care about getting OAuth right.

About the role

We’re looking for a curious, clear-thinking undergrad to spend the summer helping AuthPlane explain MCP authentication to the world.

This is a technical writing internship for someone who likes learning complex systems, asking sharp questions, and turning confusing topics into useful, readable content for developers. You’ll work across product, growth, and engineering to help define how AuthPlane talks about MCP, OAuth, agent security, and the emerging infrastructure around AI agents.

You do not need to be a professional engineer. You should be comfortable learning technical concepts, reading docs, interviewing technical teammates, and writing clearly for a developer audience.

Your work will become part of AuthPlane’s public content engine: educational guides, implementation resources, opinionated essays, research-backed reports, and product-adjacent documentation.

What you’ll work on

Category education. Help create evergreen reference material that defines MCP authentication for developers, LLMs, and future buyers. Example topics include the upside and downside of MCPs, MCP and security risks, harnesses and where they are today, and foundational explainers on how MCP changes the way agents connect to tools and data.

Implementation content. Write practical developer-facing guides tied to AuthPlane and the broader MCP ecosystem. This may include quickstarts, troubleshooting guides, best-practice checklists, and explainers on topics like access tokens vs. non-access tokens, MCP authentication best practices, and production readiness for MCP servers.

Point-of-view writing. Support opinionated pieces that help AuthPlane own the narrative around MCP security and authorization. Example topics include the sprawling number of MCP gateways, MCP vs. CLI for agentic interactions, the four gates of agent authorization, and why intent is the next frontier in AI agents.

Research and authority. Help with research-backed content that earns citations and builds credibility. This could include data collection, source review, interviews, benchmark summaries, threat landscape updates, and contributions to larger flagship pieces such as a State of MCP Authentication report.

Developer documentation support. Work with the team to improve clarity across docs, examples, tutorials, FAQs, and product-adjacent writing. You’ll help identify where developers get stuck and turn those gaps into better explanations.

Content operations. Maintain topic briefs, outlines, source lists, editorial calendars, and draft pipelines. You’ll help keep the content engine moving across monthly category education, continuous implementation content, biweekly point-of-view pieces, and quarterly research efforts.

Example projects

Draft a foundational explainer on “What is MCP authentication?” for developers who understand APIs but are new to agent infrastructure.

Turn a technical conversation with the engineering team into a practical guide on access tokens, non-access tokens, and authentication patterns for MCP servers.

Create an outline and source brief for an opinionated launch piece on the growing number of MCP gateways.

Help build a production checklist for MCP authentication best practices.

Support research for a recurring MCP threat-awareness report by collecting examples, summarizing incidents, and identifying patterns.

Rewrite a confusing technical concept into three formats: a long-form guide, a short FAQ, and a concise answer-engine-friendly definition.

What you’ll learn

How to write for developers without sounding like generic B2B marketing

How OAuth, MCP, and AI agent infrastructure fit together

How technical content supports open-source adoption and go-to-market strategy

How to turn engineering knowledge into clear public-facing content

How category education, implementation guides, opinionated essays, and research reports work together in a content strategy

How early-stage infrastructure companies build authority in a new technical category

Who we’re looking for

Currently enrolled undergraduate student, any year, any major

Strong writer with clear thinking and attention to detail

Comfortable learning technical concepts and asking questions when something is unclear

Interested in some combination of AI, developer tools, cybersecurity, open source, APIs, technical communication, or product writing

Able to turn messy notes, interviews, and research into structured drafts

Self-directed and comfortable working from a rough brief

Good judgment about tone: precise, useful, and credible rather than hype-driven

Bonus, not required: experience writing technical docs, blog posts, research papers, tutorials, or explainers

Bonus, not required: familiarity with GitHub, APIs, OAuth, cybersecurity, developer communities, or AI agents

Logistics

10–12 week program over summer 2026

Approximately 30–40 hours per week, with flexible scheduling

Fully remote, with regular video check-ins

You’ll work directly with AuthPlane’s growth, product, and engineering team

How to apply

Send a brief note about why this role interests you, along with one example of work you’re proud of. This could be a technical article, class paper, tutorial, essay, research project, documentation sample, or anything else that shows how you think and explain ideas.

No formal cover letter required. We read every application.

Email applications to: jp@codigo.ai and uruba.niazi@codigo.ai