Filtr uses AI to scan 1000+ jobs and finds postings that perfectly matches your resume

Redefine how developers interact with APIs and ensure documentation feels alive, not just written. APIs often come with static text, and developers are expected to figure things out. ReadMe aims to make documentation dynamic, interactive, and thoughtfully designed, providing great API experiences.

Requirements

• Get into the code (even a little). While you won’t be expected to ship production code, you should feel comfortable reading APIs, inspecting dev environments, and exploring technical edge cases in a GitHub repo.
• Familiar with developer tools, APIs, and technical environments—and not afraid to dig into repos or talk through tradeoffs.
• debugging an edge case

Responsibilities

• Own developer-facing product experiences. You’ll be responsible for shaping and improving the parts of ReadMe that developers interact with every day—like the API Explorer, reference guides, and SDKs—making sure they feel intuitive, powerful, and genuinely helpful.
• Make technical things feel human. You’ll turn complex systems into interfaces and workflows that feel natural and easy to navigate—even when the underlying tech isn’t.
• Ensure ReadMe is awesome by default. You’ll think critically about onboarding, defaults, and feature discoverability so the best version of our product is the one users experience first — not the one they have to dig for.
• Remove friction, not just explain it. Our philosophy is "no excuses." If something is confusing, we don’t explain it away, we fix it. You’ll help shape the product so customers don’t hit snags in the first place.
• Understand developer pain points. You'll chat with users, dig into where they’re getting stuck, and help the team understand where things feel clunky or confusing.
• Act as the voice of the developer. Be the connective tissue across product, design, engineering, and support—ensuring every decision is rooted in what’s best for the developers who use ReadMe.
• Get into the code (even a little). While you won’t be expected to ship production code, you should feel comfortable reading APIs, inspecting dev environments, and exploring technical edge cases in a GitHub repo.

Other

• Own developer-facing product experiences.
• Make technical things feel human.
• Ensure ReadMe is awesome by default.
• Remove friction, not just explain it.
• Understand developer pain points.