We're looking for a Product Manager with 3–6 years of experience who can take a problem space, decide what matters, and drive it to release. You'll own discovery, scope, and sequencing for your area, write the specs engineers actually build from, and stay close to a community that is unusually vocal about what it needs. This role suits someone who has already shipped real products and now wants ownership in a small, fast-moving developer tools company.
What you'll do
● Own a product area end to end: discovery, definition, prioritization, release, and follow-through on adoption
● Build a clear point of view on developer workflows in your area, grounded in user conversations, GitHub issues, support themes, and usage data
● Write PRDs, specs, and user stories that are unambiguous enough for engineering to estimate and build without repeated clarification
● Break large problems into shippable increments and maintain a roadmap that reflects real constraints, not wishful sequencing
● Partner with Engineering on scope and trade-offs, and with Design on flows, edge cases, and error states
● Run customer and community discovery: interviews, issue triage, and structured synthesis into requirements
● Define success measures before launch, then check whether the change actually moved them
● Drive release readiness: documentation, changelog, community communication, and support enablement
● Turn recurring customer problems into a prioritized case for investment, and say no clearly when something doesn't make the cut
● Mentor junior PMs and interns on writing, structuring problems, and working with engineering
● Contribute to internal product tooling and process where it removes friction for the team
About you
● 3–6 years in product management, ideally including time on a technical or developer-facing product
● Track record of shipping: you can walk through features you owned, the decisions you made, and what you'd do differently
● Strong writing. You can take an ambiguous problem and produce a document that leaves a team aligned rather than confused
● Comfortable working technically: reading API docs, understanding HTTP semantics, authentication flows, Git workflows, and how developers actually integrate tools
● Able to prototype or vibe-code enough to pressure-test an idea and communicate product direction concretely
● Good judgment on prioritization. You can distinguish a loud request from an important one, and explain the difference
● Comfortable with data: defining metrics, pulling what you need, and drawing conclusions you can defend
● Direct and collaborative with Engineering, Design, and Support. You escalate early and unblock quickly
● Self-driven, detail-oriented, and effective working asynchronously across time zones
● Genuinely curious about developer problems, and willing to sit in a Discord thread until you understand one
Bonus
● Experience shipping open-source or developer tools products
● Hands-on use of Bruno, Postman, Insomnia, or curl in your own work
● Depth in API testing, API design, authentication, CI/CD, or adjacent tooling
● Experience working in public: managing GitHub issues, RFCs, or community roadmaps
● Prior experience in a small or early-stage team, where the PM does the work rather than delegating it
● Technical background before moving into product
