> Markdown version of [/jobs/ext/2548413-director-product-management-data-intelligence-foundation](https://www.wearedevelopers.com/jobs/ext/2548413-director-product-management-data-intelligence-foundation). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Director, Product Management - Data Intelligence Foundation

- **Company:** Relativity
- **Location:** Boston, MA, United States
- **Experience:** Expert
- **Salary:** $188,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Data Infrastructure, Graph Database, Data Intelligence, Metadata, MongoDB, Snowflake, Core Data, Information Technology, Data Management, Machine Learning Operations, Databricks
- **Published:** August 8, 2026
- **Apply:** https://diversityjobs.com/main/sendform/8/8/28176/1/17856004?backUrl=%2Fcareer%2F17856004%2FDirector-Product-Management-Data-Intelligence-Foundation-Massachusetts-Boston

## About the Role

* 12+ years in product management; 5+ years leading platform or infrastructure PM organizations

 * Deep fluency with data platform primitives, including storage systems, metadata layers, knowledge graphs, query engines, or equivalent. You can design an API contract, contribute to engineering scope decisions, and articulate the trade-offs in a data consistency model.

 * Demonstrated ability to manage and build a PM team through hiring, leveling, and establishing product practice for a new domain

 * Bachelor's degree in Business, Computer Science, Engineering, or Design, or comparable work experience

Preferred qualifications

 * Experience building at companies where the data platform is the product, not a supporting system. Snowflake, Databricks, Elastic, MongoDB, Palantir, and similar are strong indicators of the right background.

 * Experience building for AI systems, agents, or ML pipelines as primary consumers. You understand what a model needs from data that a human doesn't, and you design for both.

Ways of working

 * Engineering credibility is paramount. You will be in technical discussions with skilled and knowledgeable engineering leaders regularly. You need to be a peer in those conversations, not a relay.

 * Organizational cadence. You establish the operating rhythm for a multi-pillar PM org: the forum structure, planning cadence, and decision frameworks that let the team move with velocity and alignment. When priorities conflict across pillars, you hold the trade-off clearly and resolve it cleanly.

 * Internal GTM ownership. Adoption of the Foundational Layer means every product team at Relativity builds with it. You define how internal teams discover, integrate, and get value from platform services, and you measure it. This is a product strategy job and a change management job simultaneously.

 * Coaching a scaling PM org. You build PM capability, not just PM headcount, leveling people up while running at speed.

 * Cross-functional influence without authority. You don't control the teams that need to adopt what you build. You make the new path clearly better and bring teams along through clarity, evidence, and trust.

 * Directional clarity under ambiguity. Several of these primitives are being defined as the engineering teams build. You make good decisions with incomplete information and update them when required.

## Description

The full PM layer across multiple engineering orgs (~# engineers):

 * Files / Natives: The storage primitive for legal documents, images, and native files. You define the substrate that makes immutable legal data consistently accessible across every product, partner integration, and AI workflow, with the SLAs, access contracts, and API surface that teams can build on with confidence. The underlying data primitives are the foundation; the degree to which the retrieval layer (Query Plane) matches this structure determines how easily the organization can navigate between "slow data" and "fast data" use cases.

 * Ontology / Relationship: The semantic layer of the Relativity Intelligence Model. Ontology encodes meaning: what kinds of things exist in legal data and how they relate, so that AI agents can reason, not just query. You define what Relativity's Ontology becomes: the entities, relationships, and contracts that give every Skill and Agent a shared vocabulary for legal data.

 * Data Capabilities: Reporting, Audit, and internal data infrastructure. The operational backbone that makes the platform observable, auditable, and explainable. These are non-negotiable properties in legal data intelligence use cases.

 * Knowledge / Metadata: The core data model that every product team, customer, and integration partner works with. A unified materialized document layer, consistent across all workspaces, is the mandate. Your roadmap evolves this surface to serve AI application teams as first-class consumers alongside the users who have relied on it for years.

 * Query Plane: One of the most performance-sensitive and strategically important services in the product. The mandate is a unified retrieval pillar with a rich materialized document layer: standardized ingestion APIs independent of data source, hybrid retrieval (lexical + vector) with reranking, chunking as a managed capability, and tiered storage (cold/warm/hot).


## Related Videos

- [Stop Renaming Teams, Start Product Thinking: A PM's Guide to Platform-as-a-Product](https://www.wearedevelopers.com/videos/100342-stop-renaming-teams-start-product-thinking-a-pm-s-guide-to-platform-as-a-product)
- [How Cisco embraced a DevOps culture within its network engineering team](https://www.wearedevelopers.com/videos/99-how-cisco-embraced-a-devops-culture-within-its-network-engineering-team)
- [A Data Mesh needs Open Metadata](https://www.wearedevelopers.com/videos/505-a-data-mesh-needs-open-metadata)
- [40 Minutes to Build a Serverless COVID-19 REST and GraphQL APIs](https://www.wearedevelopers.com/videos/208-40-minutes-to-build-a-serverless-covid-19-rest-and-graphql-apis)
- [From Messy Queries to Scalable Systems - How Data Engineering actually works](https://www.wearedevelopers.com/videos/100203-from-messy-queries-to-scalable-systems-how-data-engineering-actually-works)
- [How building an industry DBMS differs from building a research one](https://www.wearedevelopers.com/videos/768-how-building-an-industry-dbms-differs-from-building-a-research-one)

## Related Articles

- [Coffee with Developers - Maria Apazoglou - Making AI understandable for all in production](https://www.wearedevelopers.com/magazine/475-coffee-with-developers-maria-apazoglou-making-ai-understandable-for-all-in-production)
- [From developer to manager – what does it take to become an engineering manager?](https://www.wearedevelopers.com/magazine/42-from-developer-to-manager-what-does-it-take-to-become-an-engineering-manager)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering)
- [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)
- [Résumé-Driven Development: How IT trends affect the job market for software developers](https://www.wearedevelopers.com/magazine/59-resume-driven-development-how-it-trends-affect-the-job-market-for-software-developers)