Craft beautiful documentation with us

Learning a new API or code library should feel magical

As developers, we spend most of our time either reading documentation or writing it. Documentation is the UX we use when interacting with a new API or programming language, yet it’s almost always relegated to an afterthought.

We don’t want to just make writing “good documentation” easier – we want to change what “good documentation” even means. Let’s replace paragraphs of text with simple onboarding flows, custom-tailored code examples, intuitive SDKs and interactive UIs. (Here's some things we're excited to work on.)

Developers are just like regular consumers. They like simple, beautiful, easy-to-use products, too.

We have a long way to go still. That's why we need you!

209 Kearny St #2, San Francisco, CA

Y Combinator Winter 2015

Seed funding (Raised over $1MM)

Competitive salary and significant equity

Good work/life balance. We don't work on weekends.

Quarterly product roadmap retreats at locations like Santa Cruz or Tahoe.

Unlimited days off. And don't even think of coming in on your birthday!

Ability to work from home a few days a week, if you're more productive that way.

Stay healthy! Paid monthly gym membership.

Full healthcare, vision and dental coverage; paid maternity / paternity leave.

API Engineer

We want creating a ReadMe to be the first thing a developer does when it comes time to create an API. We don't want to just be documentation... we want ReadMe to be the entire UI for APIs.

ReadMe needs to start collecting documentation in the form of semantic metadata, rather than paragraphs of text. Swagger is emerging as the winner, so we'll start with building tooling around that. You should have a love for Swagger in concept, but a healthy wariness for it in practice: Swagger is confusing and tough to get started with, and we need to make it much easier for people to understand and implement.

We want to normalize APIs on the documentation/SDK layer. This means that anyone should be able to write their APIs however they want (API key as a header? sign requests with JWT? be x-www-form-urlencoded?), however all APIs on ReadMe should feel consistent to end users. We'll do this through a combination of things, including generating SDKs and building tooling around authentication.

Lastly, we want to start pushing our own philosophies... which you'll craft. APIs are simple, however people find infinite ways to complicate them. We'll never force anyone to do things a particular way, however going forward we want to start promoting best practices that will make working with ReadMe easier and better.

It's important that you love APIs, but focus on usability and ease-of-use rather than complexity.


  • Making our "Try It Now" feature work like a charm in any situation
  • Auto-Generating code samples and SDKs in various programming languages
  • Allowing people to manage their API keys in ReadMe
  • Tackle the issue of authentication... it's confusing, and a huge barrier to entry for APIs
  • Work on leveraging what we know about the API and the user to custom-tailor documentation
  • Keep up to date with API technologies, and making that simple for everyone to understand and work with
  • Writing blog posts and (if you want!) speaking at conferences about APIs

Developer Bloggerremotepart-time

We’re looking for a developer who loves to write! We’re searching for someone who is good at explaining complex topics in a way that junior engineers would understand and senior developers would still find engaging. If you can impart wisdom, clarify something complex and crack a joke in the same sentence… you’re what we’re looking for.

The job will be a part-time remote job, and you can write as much or as little as you’d like. At first the medium will be blog posts, but we’d love to expand into content marketing sites, open source projects, and whatever else makes sense to help get the word out!

(Please not that we're only looking for actual developers who like to write... we already have non-technical blog writers!)

Potential Topics

  • API best practices
  • Microservices
  • Swagger (how, why, etc)
  • Reviews of developer tools
  • New feature announcements
  • In-depth guides on how to use our product
We're looking for an array of writers! We already have a blog that chugs along, so we're just looking for people to contribute to it... so we're flexible! We're just looking for opinionated people who want a platform to help people learn.

Full-stack Node/JS Developer

We're looking for a product-focused Node/Angular developer to join our team. ReadMe replaces paragraphs of text with custom-tailored developer experiences. The role requires both frontend (Angular) and backend (Express) programming. Having a good sense of product and design is vital.

We're a small startup with a big reach, so you'll be able to have a huge impact. Working at ReadMe means there's a lot to be done, but also autonomy, flexibility, and a clear mandate to tackle big problems.


  • owning major feature development. You'll lead the development of things like syncing API references from Github, creating easy onboarding flows, and new integrations.
  • helping to build a developer-focused company culture.
  • leading technical initiatives that grow and scale ReadMe.
  • Building a documentation platform that redefines the way people consume APIs and documentation.


  • Passionate about making products people love
  • Previous professional experience as a programmer
  • You have the ability to take ideas from conception to release
  • Your GitHub is full of everything from embarrassing hacks to impressive Open Source contributions
  • You stay up to date with the latest web technologies
  • Comfortable in Angular/Node
  • Understanding that roles are flexible and willing to take on new opportunities as ReadMe grows!

Bonus Points

  • Experience at early stage startups
  • Experience with developer tools
  • love of owls!

Some Of Our Favorite Customers

ReadMe currently provides the developer experience for thousands of awesome companies.

Need beautiful documentation?

You may not be looking for a job, but everyone needs beautiful documentation!

Sign Up for ReadMe!