Product Lead, Data Catalog & Semantic Layer

What You'll Do

• Roadmap and strategy — you'll set the vision and roadmap for the catalog and semantic layer, develop points of view in ambiguous territory, and drive the team toward them.
• Data catalog and metadata layer — the systems that describe every table, field, and object in Rippling's data model, including how we auto-generate rich metadata for customer-defined custom fields, custom objects, and imported data where no internal team can write descriptions manually
• Field selection and semantic mapping — the product strategy for how our AI disambiguates user intent across native objects, custom objects, and imported data: when to auto-resolve, when to ask, and how the mapping gets smarter over time
• Data lineage — the model and tooling that map how data flows and depends on itself, serving humans exploring their data, AI features reasoning about context, and the platform itself (so we can warn users before a deleted field breaks a downstream report or workflow)
• Catalog UI — search, browse, discovery, detail views, lineage visualization, and metadata editing, much of it for non-technical users who've never looked at a schema
• Cross-team standards and proactive partnership — setting the bar for how metadata works across Rippling, for both internal teams and customer data. You'll earn it by getting ahead of what other teams need, then build the review processes, standards, and intake that make good practice stick

Qualifications

• 8+ years of product experience, with meaningful time in the data platform or data infrastructure space — semantic layers, metadata, data catalogs, or closely adjacent
• AI-native thinking: you understand how LLMs use structured context, what it means for metadata to ground a model's behavior, and why catalog quality directly affects AI feature reliability
• Systems orientation: your instinct is always "how do we generate and maintain this at scale" — not "how do we get humans to fill this in"
• Cross-functional influence: you build relationships before you need them. Other teams should want to loop you in early because you make their work better — not because they're required to. You anticipate what's coming and get ahead of it, and over time you create the structural touchpoints that make good metadata practice stick across the org
• Strong opinions, well-reasoned: once you form a point of view, you drive it. You don't wait to be told what to build
• Technical depth: you can read a schema, discuss retrieval trade-offs, and work with engineers as a peer — you don't need translation
• Comfort with foundational work: you're motivated by building the layer that makes everything else work, even when it's invisible to end users