Product Manager

\n Why This Role Exists
\n
\n
Profisee is how enterprises finally solve the data quality issues that have been holding back their most strategic initiatives. Our AI-first master data management (MDM) platform cleans, unifies, and improves critical enterprise data, providing the trusted foundation organizations need for AI, analytics, and digital transformation.
\n
AI systems fail in enterprises not because the models are weak but because the data underneath them is ambiguous, duplicated, and undocumented. An agent that retrieves three versions of the same customer will answer confidently and wrongly. This role exists to close that gap through data governance, data catalog integration, data products, and third-party data enrichment — resolved entities, meaningful semantics, explicit ownership, and enforceable access policy, delivered in a form an agent can actually consume.
\n
\n Reporting & Key Relationships
\n
\n
You will work closely with engineering, design, pre-sales, customer success, marketing, catalog platform partners (Microsoft Purview, Databricks Unity Catalog, Collibra, Alation, Atlan), and external data providers (e.g., Melissa, Loqate, Dun & Bradstreet, Experian, ZoomInfo). You are expected to become the go-to authority for this product domain — internally and with customers — within your first year.
\n
\n Key Performance Objectives
\n
\n
1. Complete structured discovery and publish a prioritized roadmap across all four domains.
\n
By end of Month 3
\n
Interview a representative set of customers, data stewards, and CDO-organization stakeholders, and mine support escalations and pre-sales/CS feedback, across data governance, catalog integration, data products, and enrichment. Translate that research into a prioritized, written set of problems and opportunities that engineering leadership and go-to-market stakeholders sign off on as the basis for the next two quarters of work.
\n
2. Define and ship an initial, buildable version of the data product concept.
\n
By Month 6
\n
Land a clear definition of a Profisee data product — a curated, owned, versioned set of mastered data with a documented contract, quality guarantees, an access policy, and a consumption endpoint (delivered primarily through our MCP server). Specify it precisely enough that engineering can build against it without re-litigating the concept, and clearly enough that sales can position and demo it to at least one design partner or active prospect.
\n
3. Deliver a catalog integration that customers recognize as a genuine step up from a one-way export.
\n
By Month 9
\n
Ship bidirectional integration with at least one major catalog platform (e.g., Microsoft Purview, Collibra) covering both outbound publishing (entity models, quality scores, lineage, stewardship) and inbound inheritance (glossary terms, classifications, sensitivity labels). Validate success with direct confirmation from a reference customer who already has meaningful investment in that catalog.
\n
4. Bring at least one new enrichment capability to market with pricing and margin resolved.
\n
By Month 12
\n
Evaluate the third-party enrichment provider landscape (address verification, firmographic/contact enrichment, industry reference data) well enough to make build/buy/partner calls with conviction. Launch at least one new enrichment capability with metering, packaging, and pricing fully resolved — not deferred — and hit an agreed gross margin target after pass-through provider costs.
\n
5. Turn provider onboarding into a repeatable product motion.
\n
By Month 12
\n
Build the certification, credentialing, and integration framework needed so that onboarding the second and third enrichment providers takes measurably less time and engineering effort than the first — evidence that onboarding has become a product capability rather than a one-off project each time.
\n
6. Establish yourself as the credible internal and external authority in this domain and connect that authority to business outcomes.
\n
Ongoing, assessed at 12 months
\n
Become the person engineering, sales, pre-sales, and marketing turn to first on governance, catalog, data product, and enrichment questions. Participate directly in pre-sales engagements that use governance and data-product capabilities to reach the Chief Data Officer buying center, and show a measurable connection between that work and deal size, competitive win rate, or shortened evaluation-to-production timelines.
\n
\n Competencies
\n
\n
• A track record of owning a product area end-to-end — from discovery and strategy through delivery and iteration — in a B2B SaaS or enterprise software environment (typically 3+ years of PM experience, though the pattern of ownership matters more than the tenure).
\n
• Experience shipping integrations or capabilities through agile engineering teams: sprint planning, backlog prioritization, and writing specifications engineers can build against without hand-holding.
\n
• Comfort with the commercial mechanics of product work — pricing, packaging, metering, and vendor/provider cost structures — since two of the six objectives above are explicitly commercial.
\n
• A history of running customer research (interviews, escalation analysis, pre-sales/CS feedback loops) and turning it into decisions, not just documentation.
\n
• Communication that works in both directions — able to hold their own with engineers on a technical integration question and with senior leadership on why it matters to the business.
\n
• A demonstrated tolerance for ambiguity: someone who has taken a vaguely-scoped, cross-functional problem and driven it to a resolved, shippable outcome.
\n
\n Additional Background That Strengthens Your Candidacy
\n
\n
• Real, demonstrable understanding of data governance in practice: how data organizations actually use catalogs, how metadata is maintained and consumed downstream, and why governance programs succeed or fail — as a product owner or as a practitioner who ran one of these programs.
\n
• A defensible, articulated point of view on how governed data and metadata feed AI systems — specifically why entity resolution and semantic context determine whether an AI answer can be trusted.
\n
• Entity resolution, Data Engineering, Data Quality, Analytics, or Data stewardship experience
\n
• Direct experience at or with a data catalog or metadata platform — Microsoft Purview, Collibra, Alation, Atlan, Databricks Unity Catalog, Snowflake Horizon, or Informatica.
\n
• Familiarity with data mesh, data product, and data contract practice, including a grounded view of where these ideas hold up in large enterprises and where they don't.
\n
• Experience grounding AI or agent systems in enterprise data through retrieval, MCP, or comparable approaches.
\n
• Experience with master data management or data integration platforms.
\n
• Direct experience with third-party data providers such as Melissa, Loqate, Dun & Bradstreet, Experian, or ZoomInfo — as a buyer, integrator, or product owner.
\n
• Experience owning an API-metered or consumption-priced product capability.
\n
• Familiarity with regulatory and control frameworks that drive governance programs — GDPR, CCPA, HIPAA, or frameworks like BCBS 239.
\n
• Familiarity with the Microsoft ecosystem — Azure, Microsoft Fabric, Power BI, or Dynamics.
\n
• Working technical knowledge of databases, SQL, APIs, and cloud architecture.
\n
• Prior experience directly supporting pre-sales or customer-facing engagements as part of a product role.
\n
• Experience working with global partner ecosystems, including systems integrators and value-added resellers.
\n
\n How Performance Will Be Reviewed
\n
\n
We evaluate performance across four competencies: User-Centric Mindset, Communication and Collaboration, Execution, and Business Outcomes. We invest in the growth and development of our team members and believe in providing honest, constructive feedback.
\n
We value strong cross-functional relationships and believe the best products come from teams where engineering, design, product, and go-to-market functions work closely together.
\n
Our product team operates with a high degree of ownership. Product Managers are not project managers or ticket writers. You are expected to be a domain expert, a customer advocate, and a strategic thinker who can also roll up your sleeves and get things done.