protege - Product Manager, Platform
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT
Requirements
• 5-8 years of PM experience, ideally in data infrastructure, data tooling, or data-adjacent platforms. • Experience at a company moving from services or custom delivery toward repeatable, product-led operations. • Strong fluency in how data gets ingested, transformed, validated, and delivered at scale. • Ability to write clear specs and prioritization memos that engineers and cross-functional partners can use without heavy translation. • Comfort making decisions with incomplete information and communicating tradeoffs honestly. • Credibility with teams you do not formally manage, earned through proximity, judgment, and follow-through. • A high bar for clarity in writing and communication. • Bonus if you also have: • Experience at a company that licenses or commercializes data as a product. • Familiarity with agentic or LLM-based data tooling. • Experience with healthcare or media data, or prior experience embedding with a customer-facing Solutions org. • Working with Protege • We move fast - thoughtfully. Speed matters in what we’re building, and so does intention. We are biased toward action and always learning. • We’re a lean, high-trust team. Everyone has real ownership. Clarity and autonomy drive our best work. • We take our work seriously, not ourselves. We solve hard problems with humility and celebrate wins - big and small. • We’re kind, direct, and inclusive. We give feedback early and often, with the goal of helping one another grow. • We’re builders at heart. Every person at Protege is hands-on, resourceful, and focused on creating momentum. • We grow fast - together. You’ll be surrounded by people who care about impact, who challenge you to think bigger, and who are genuinely excited about what comes next.
Responsibilities
• Own the bespoke-to-platform loop • Stay close to what Solutions teams are building in the field, including ingestion patterns, transformation workflows, and delivery formats. • Identify what is truly repeatable versus what is one-off, and translate repeated patterns into platform opportunities. • Drive the process by which manual delivery work becomes reusable Atlas capability. • Define what gets built • Own the Atlas roadmap for your area and prioritize opportunities against one another with explicit reasoning. • Write sharp, unambiguous specs grounded in real delivery work and scoped to what engineering can build in a reasonable window. • Make clear tradeoffs between near-term deal pressure and longer-term platform leverage. • Work as a bridge, not a gatekeeper • Spend time in delivery retros, with Solutions teams, and on customer calls when useful so your judgment stays close to the real work. • Partner directly with Engineering and Data Lab to make platform investments concrete, legible, and appropriately scoped. • Work with the Head of Product to align Atlas priorities with Protege’s broader product strategy as the business scales. • Build the operating rhythm • Design how reusable patterns get flagged, how they are evaluated, how roadmap decisions are made, and how updates flow back to the field. • Create a process that people actually use — lightweight enough to support delivery speed, but structured enough to improve reuse and decision quality over time. • Help Protege build the product muscles required to move from bespoke work toward repeatable, product-led operations. • What this role is not • It is not a project-manager role focused on status tracking or sprint hygiene. • It is not an ivory-tower platform role disconnected from customer delivery reality. • It is a hands-on PM role defined by judgment, proximity to the work, and the ability to create leverage from repeated patterns. • What Success Looks Like • 30 days: Learn the real work • Build a working understanding of Atlas, how Solutions teams deliver today, and where repeated patterns are already visible. • Earn trust by showing up in the right rooms and asking the right technical and operational questions. • 60 days: Make product calls from field evidence • Run an early version of the bespoke-to-platform loop and produce initial specs tied to real delivery needs. • Show strong judgment about what should be productized now, what should wait, and what should remain custom. • 90 days: Establish the operating system • Create a repeatable cadence for intake, prioritization, roadmap updates, and feedback to the field. • Make Atlas roadmap decisions more grounded, more transparent, and more useful to both Solutions and Engineering.
Benefits
• Pre-seed/seed-stage startup • Series A or B startup • Series C or D startup • Series E+ startup • Protege would be my first startup • or drag and drop here • In 2-3 sentences, please explain how your experience aligns well with the role
No credit card. Takes 10 seconds.