This is an individual contributor role. You won't be managing a team of PMs, you'll be directly driving the roadmap working directly with engineering, sales and marketing to make sure we're building the right things in the right order. You'll own the full product lifecycle: from understanding what developers need, to defining what we build, to making sure it ships and lands well.

The best person for this role has shipped developer tools before. You know what it's like to have engineers as your end users, and you know how different that is from building for a general consumer audience. You have strong opinions about what "good" looks like in developer experience, and you're not afraid to push for it.

What You'll Do

• Own product definition. Write clear, well-researched specs that engineering can build from and that sales can speak to. Be the person who turns ambiguous problems into crisp decisions.
• Conduct ongoing customer research and turn those conversations into a clear picture of what matters and why.
• Partner with engineering on sequencing and scope. You're not just writing specs and throwing them over the wall. You'll be in the "room" working through tradeoffs, keeping projects moving, and calling out when something is off track.
• Coordinate timelines and rollout. Make sure our team knows what's shipping and when.
• Define and move product metrics. Set the north star for each initiative. Know what success looks like before you start, instrument the right things, and hold yourself accountable to the numbers after launch.
• Work with sales and marketing on go-to-market. You'll review positioning, docs, and launch content to make sure it's technically accurate and actually resonates with the people we're trying to reach.
• Maintain and communicate the product roadmap both internally and externally.
• Surface and prioritize enterprise needs. Work closely with our enterprise customers, especially during evaluations and expansion conversations, to make sure their requirements are feeding back into the product.

What We're Looking For

• Mission alignment. You care about helping the world stop writing everything twice. Flutter is our tool for that, and Shorebird aims to take Flutter beyond where Google can.
• 5+ years of product management experience, with at least 2-3 years working on developer tools, infrastructure, or a product where engineers were your primary end users. You've lived the pain points you'll be solving.
• Strong product instincts. You know how to frame a problem, prioritize ruthlessly, and make good decisions with incomplete information. You've done this enough times that the process is second nature.
• A research-first mindset. You don't guess at what users need, you go find out. You're comfortable talking to developers directly and turning qualitative signals into something actionable.
• Technical credibility. You don't need to write production code, but you need to earn the respect of the team members you're working with. You can read a PR, understand an architecture tradeoff, and ask the right questions.
• Excellent written communication. You'll be writing specs, roadmap updates, and internal briefs. Clear, concise, direct writing is a core part of the job.
• Comfort with ambiguity and small-team environments. You'll be building the processes around the product function.
• Cross-functional range. You can shift from a deep customer discovery call to a metrics review to a go-to-market conversation in the same day. You know how to show up differently for different audiences.
• Bonus: direct experience with mobile or Flutter development, or a background in devtools, SDKs, CLI tooling, or similar technical product categories.

Why Join

• You'll be the first dedicated Product hire at Shorebird. That means real ownership, real scope, and a real chance to shape how the product function works at the company.
• Unlike Product roles at big companies, you won't be managing up through layers of stakeholders. The engineers building the product, the customers using it, and the CEO making strategic decisions are all within arm's reach.
• We travel periodically to a central location to work and socialize as a team for a week.
• Work directly with a small team solving hard, high-impact problems.
• Competitive compensation + equity.

What Your First Days Will Look Like

First Day

We're all remote, so you'll start by opening up Discord and saying hello. Most of us hang out on video throughout the day. We'll get you access to Linear, Notion, Plain, and our docs. We'll walk you through where things stand: what's shipping, what's being defined, and what questions nobody has answered yet.

First Week

You'll spend time getting oriented on the product, the codebase at a high level, and the customer base. You'll read through recent support threads, sales calls, and open Linear issues to start building context. We'll introduce you to a handful of customers and enterprise prospects so you can start forming your own opinions about what matters.

First Month

By now you'll have a point of view. You'll have identified the biggest gaps in how we currently define and prioritize work, and you'll be starting to fill them. You'll own at least one active initiative end-to-end, and you'll have started establishing a rhythm with engineering around spec reviews, planning, and weekly check-ins.

First Quarter

You're in a rhythm. You have a working roadmap that the team trusts, a clear set of metrics you're moving, and a research practice that's feeding insights into what we build next. Engineering knows what's coming and why. Sales has what they need to speak to the product.

Beyond that, it's hard to predict. We're a small startup. What we're looking for first and foremost is someone who wants to work in that environment and genuinely cares about making developers successful.