Principal Product Manager

What You'll Do

• Set the strategy and roadmap for Directory, including foundational data model work and customer-facing features — and sequence it in a way that unblocks the rest of the product organization
• Translate product work into business outcomes: define the 1–3 OKRs your work moves, establish the metrics that prove it, and connect your roadmap to what the business has prioritized
• Drive cross-functional adoption: building the feature isn't enough — you're actively working with the product teams that depend on Directory to ensure what you ship gets integrated and used the way it was intended
• Develop and evangelize product strategy internally and externally, from Procore's executive team to Procore's largest customers
• Write requirements that don't require a follow-up meeting to interpret — behavior, edge cases, permissions, governance, and API dependencies are specified, not gestured at
• Execute within a high-velocity agile environment that delivers incremental value quickly and iterates based on user feedback
• Define, measure, and report key metrics that demonstrate the value your team creates

What We're Looking For

• 10+ years of experience in Product Management at a SaaS company
• A proven track record of owning a complex, cross-functional domain — not just shipping features, but moving metrics and changing how a product area works
• Demonstrated ability to connect product outcomes to business outcomes: you identify the OKRs you're moving, define how you'll measure success before you ship, and can explain it to an executive without warming them up first
• Experience influencing cross-functional teams — including partner product teams, engineering, and GTM — to drive adoption of platform work, not just awareness of it
• Strong systems thinking: you catch the governance gap, the permissions edge case, and the downstream dependency before someone else has to raise it
• You write for engineers — PRDs that close gaps, not open them; functional requirements that are behaviorally precise and edge-complete
• Comfortable with ambiguity: you don't wait for clarity, you create it; you make a call, state your reasoning, and move
• Experience in data-model-heavy domains — directory, identity, company or vendor management, or similar — is strongly preferred
• Familiarity with workflows where the accuracy of underlying company or vendor data is load-bearing for downstream processes is a strong plus