San Francisco | $170–220K base + 0.5–1.0% equity
You're our first product hire, owning the product function end-to-end at an AI-native company creating a new category.
Richard and Max set vision and stay close to customers. What's missing is someone who owns what happens between vision and shipped product — the roadmap, the customer discovery cadence, the analytics, the cycle rhythm, and the hundred small scoping calls per week that shape what actually gets built.
You'll be handed problem areas and trusted to run. You will work with the founders and the team to triangulate on direction regularly — not for oversight, but because product and engineering need to stay tight at this stage. Between those moments, the outcome is yours.
This is explicitly an enterprise product role. Our customers are Snowflake, Vanta, Benchling, and similar. Our users are Heads of Solution Engineering and VPs of Sales. If you're looking for consumer product work, this isn't the role.
<aside> ℹ️
The question every buyer asks before signing a deal isn't "what does this cost?" — it's "what is this actually worth to us, and can you prove it?"
There's no infrastructure for this yet. It's done by consultants at $500/hr, by sales teams guessing in spreadsheets, or it doesn't get done at all. We're building the intelligence layer for the outcome economy: value agents that uncover what each customer uniquely gains from a product, generate defensible business cases in minutes, and measure ROI across the full customer lifecycle.
Our customers include Snowflake (3,000+ reps on the platform), Ironclad, Vanta, Benchling, Cognite, and Pendo. Zero churn. Team of 6. We're not optimizing an existing category. We're creating one.
</aside>
Richard and Max have strong views on where the product is going. Your job is to turn that into a cycle-by-cycle plan the engineering team can execute against — scoped, sequenced, grounded in customer evidence, and resilient to the weekly chaos of a 6-person company selling to public companies. You maintain the roadmap. You write specs when they're needed. You make the hundred small scoping decisions per week that are currently stealing the founders' attention.
Customer signal at Minoa today is a collection of Slack threads, founder memory, and deployment calls. You'll turn it into a system: customer advisory council, structured discovery cadence, product analytics instrumentation, and a standing review of what users are actually doing inside the product. You're not just "the voice of the customer" — you're the person building the machine that makes customer signal legible to the whole team in real time.
Cycle planning. Commitment tracking. Reviews that actually close. The cadence that turns "we're working on it" into "it shipped and customers are using it." You bring rigor without bureaucracy, without Agile theater. If engineers are shipping faster with more clarity because of you, you're winning.
The commitments the team makes in cycle planning should be the commitments the team ships. You notice when scope is being rationalized down to something not worth doing, when a commitment is two weeks late and nobody's flagged it, when a "yes" in a planning meeting didn't have real consensus behind it. You hold the bar when everyone else is tired. Done without ego, done constantly.