Senior Documentation Manager

RevenueCat removes the headaches of building and scaling in‑app subscriptions. Since graduating from YC’s S18 batch we’ve grown into the default monetization platform for mobile: we’re in >40% of newly shipped subscription apps, we process $10B+ in annual purchase volume, and we help everyone from a solo dev in Brazil to the OpenAI mobile team understand and grow their revenue.

We’re a remote‑first crew of 120+, spread across 25 countries, and guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. If you want your work to touch hundreds of millions of end‑users (and help the developers behind them get paid), you’ll fit right in.

About the team

Documentation at RevenueCat sits at the intersection of Product, Engineering, Support, and Marketing. Our docs are often the first - and sometimes only - way developers experience RevenueCat.

This role will be the first hire to own the end-to-end documentation experience: how it’s structured, how it stays accurate, how it scales with the product, and how it serves both humans and machines. You’ll work closely with Engineering, Product, Design, Support, Advocacy, and Content to ensure our documentation tells a clear, consistent story as RevenueCat continues to grow in scope and complexity.

The Role

As Senior Documentation Manager, you’ll be responsible for making RevenueCat’s documentation a durable competitive advantage.

Today, we have strong individual documentation pages, but they don’t always form a cohesive system. Documentation can lag behind shipped features, vary in tone and structure depending on who wrote it, and mix conceptual docs, troubleshooting, and help content in ways that create friction for customers.

Your job is to fix that - and design a documentation system that scales.

You will:

Own documentation strategy and information architecture

• Define a clear, opinionated structure for RevenueCat’s documentation that supports:

• New apps getting started quickly

• Existing apps migrating or expanding usage

• Customers using only a subset of RevenueCat’s features

• Ensure documentation tells a coherent story across features, platforms, and use cases

• Decide what belongs in product docs vs help center vs troubleshooting guides, and enforce those boundaries

Establish consistency in voice, style, and quality

• Develop and maintain documentation brand and style guidelines

• Ensure docs written by engineers, PMs, and others meet a consistent bar for clarity, tone, and usability

• Actively manage and prune legacy documentation, especially in high-visibility areas

Partner deeply with Engineering and Product

• Work with Engineering to ensure new features ship with accurate, high-quality documentation

• Build processes that prevent docs from falling out of date as the product evolves

• Review and improve technical accuracy without becoming a bottleneck to shipping

Make documentation useful for both humans and AI

• Treat AI readability and machine consumption as first-class concerns alongside human readers

• Structure content so it works well for LLMs, search, and future AI-driven tooling

• Anticipate where the documentation system will break as scale increases, and proactively design solutions

Expand documentation into a broader learning ecosystem

• Collaborate with Content Marketing, Advocacy, and Design to extend docs with:

• Videos

• Blog posts

• Tutorials and guides

• Ensure these assets reinforce (not fragment) the core documentation experience

About you:

You’re a documentation leader who thinks in systems, not pages. You care deeply about clarity, accuracy, and structure, and you’re opinionated about what good documentation looks like at scale.

You have:

• 5-8+ years experience in technical documentation, developer education, or technical content leadership

• Experience owning documentation for a complex, evolving developer platform or API-driven product, with hands-on ownership of a git-based, markdown-driven documentation system (Docusaurus is a plus)

• A strong editorial mindset paired with enough technical depth to work effectively with engineers

• A track record of designing processes that keep documentation accurate over time, not just launching one-off rewrites

You bring:

• Excellent written communication and editorial judgment

• Strong information architecture instincts

• Comfort pushing back when documentation quality or placement undermines the user experience

• Experience collaborating cross-functionally in a remote, async-first environment

Values & ways of working:

• You’re energized by helping developers succeed with less friction

• You default to ownership and long-term thinking

• You’re pragmatic - you ship improvements iteratively rather than waiting for a perfect overhaul

• You’re comfortable operating without a pre-existing playbook and building one as you go

In the first month, you'll:

• Become deeply familiar with RevenueCat’s product and existing documentation

• Integrate RevenueCat yourself into a sample app to experience the docs end-to-end

• Audit the current documentation for structure, tone, accuracy, and redundancy

• Develop initial documentation brand and style guidelines

• Propose a restructured documentation approach that’s more approachable for both new apps and existing apps migrating to RevenueCat

Within the first 3 months, you'll:

• Lead a documentation overhaul that tells a cohesive, end-to-end story

• Ensure customers feel oriented and confident whether they’re using the full platform or a single feature

• Establish tight collaboration loops with Engineering, Product, Design, and Marketing around new feature launches

Within the first 6 months, you'll:

• Design and implement systems and processes to keep documentation up to date over time

• Partner with Developer Advocacy to create complementary videos, blogs, and educational assets

• Make AI readability as important as human readability across our documentation

Within the first 12 months, you'll:

• Establish public documentation as the source of truth for how RevenueCat works internally and externally

• Make documentation good enough that it’s actively used to onboard and train new engineers

• Move help center and troubleshooting content into a clearly separated, purpose-built home

• Expand troubleshooting content so issues are easier to diagnose for both humans and AI

• Anticipate scaling limits in our documentation system and proactively address them through automation, tooling, or hiring plans

What we offer:

• Competitive equity in a fast-growing, Series C startup backed by top-tier investors, including Y Combinator

• 10-year window to exercise vested equity options

• Fully remote and flexible work environment

• 4-5 weeks of suggested time off annually for mental, physical, and emotional recharge

• $2,000 USD for workspace setup and $1,000 USD annual stipend for continuous learning

Curious about the interview process? Discover more in our blog post about how we hire and learn tips to help you succeed.