Data Product Manager, Methodology & Semantic Governance

We need to output HTML fragment with sections only where there is real specific content. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Why work at Curinos?" maybe considered benefits? Actually benefits section: we have "Competitive benefits, including a range of Financial, Health and Lifestyle benefits to choose from Flexible working options... Unlimited PTO policy, floating holidays, volunteering days and a day off for your birthday Learning and development tools... Work with industry leading Subject Matter Experts... Regular social events... Collaborative, supportive culture... Employee Assistance Program..." That's benefits. So we can include Benefits section with those details. Pay: Salary Range: $145,000- $155,000 USD (plus Bonus). So we can include Pay section. Schedule: Not explicitly mentioned; there is hybrid/remote, but schedule not given. So we should not create Schedule section unless posting actually states them. It says "This role is open to hybrid/ remote candidates based in the United States." That's about location/modality, not schedule. So we should not create Schedule. Qualifications: There's "Technical Qualifications" and "Preferred Experience". Could map to Qualifications and Skills? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We have "Job Description" paragraph describing role. That could be About the role. Responsibilities: list of bullet points under "Responsibilities". We'll put those in

• . Requirements: maybe "Desired Skills & Expertise" could be Requirements? Actually "Desired Skills & Expertise" list of experience and abilities. Could be Requirements or Skills. The headings list includes both Requirements and Skills. We need to split: Requirements could be mandatory experience (4+ years etc). Skills could be desired skills/expertise? But we have also "Technical Qualifications". Might map to Qualifications. Let's think. We have sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe the "Desired Skills & Expertise" list). Qualifications (Technical Qualifications). Skills (maybe "Desired Skills & Expertise"? but we already used). Actually we could treat "Desired Skills & Expertise" as Skills. And Requirements could be something else? There's no explicit "Requirements" besides maybe the hybrid/remote location? But we should not invent. Better to follow the posting: they have "Desired Skills & Expertise" and "Technical Qualifications" and "Preferred Experience". Also "How You Work" (behavioral). Could map to Skills? Hmm. We need to preserve all substantive info. We can create multiple sections as needed, but only those headings that have real content. We can use About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's seven sections. We'll fill each with appropriate content. Let's extract content: About the role: The introductory paragraphs before "Job Description": "Curinos empowers financial institutions to put customers at the center of every decision. Our AI-first platform transforms proprietary data, advanced analytics and deep financial services expertise into timely recommendations - delivered right where teams work. The result: confident decisions, stronger customer relationships, and lasting, profitable growth. Curinos operates under a hybrid modality and has office locations in New York, Chicago, Boston, Toronto, and London. This role is open to hybrid/ remote candidates based in the United States. Job Description This highly visible individual contributor role sits at the intersection of Product, Platform, Analytics, and Subject Matter Expertise. You will establish and maintain the standards that govern how Curinos benchmarks and metrics are defined, calculated, approved, and evolved. In practice, benchmark methodology includes the rules, calculations, eligibility and sufficiency criteria, data sources, quality standards, contractual considerations, and governance processes that make consistent, comparable, and trusted. You will also serve as the steward of the shared semantic layer that powers Curinos One. This semantic layer is the common foundation for business logic, canonical metric definitions, calculation rules, metadata, lineage, and analytical concepts. It lets teams build from the same definitions rather than recreating them product by product, whether the consumer is a BI dashboard, an internal analyst, or an AI-driven feature within Curinos One. This role combines analytical rigor, strong process leadership, and hands-on data investigation. You will dig into datasets, calculations, and business logic while designing governance that teams want to use because it reduces ambiguity, improves quality, and helps them move faster. You own the semantic layer and benchmark methodology as a data product, with a roadmap focused on trust, quality, and reusability rather than customer-facing features, and with real authority over what gets approved and how the underlying data asset is maintained over time." That's a lot; we can keep as About the role. Responsibilities: The bullet list under "Responsibilities": there are four bullet points each starting with a bold heading? Actually text: Define Benchmark Methodologies Own the standards, rules, calculations, eligibility criteria, data-use considerations, and documentation that make Curinos benchmarks consistent, explainable, and fit for client use Govern Methodology Decisions and Change Hold approval authority over benchmark methodology changes. Lead the review and approval process for benchmark methodology changes, working with Product, Data, Risk, Legal, and client-facing teams to evaluate trade-offs, weigh controls, and reach sound, well-supported decisions Build the Shared Semantic Foundation for Curinos One Steward the common metric definitions, business logic, metadata, lineage, and glossary, including field-level definitions and data grain specifications, so teams can reuse trusted analytical concepts across Steward the Semantic Layer as a Living Asset Act as the accountable owner of the semantic layer's ongoing health, including data quality, lineage accuracy, and definition drift over time. When a metric definition degrades, a data source changes, or lineage breaks, you are the one who catches it, diagnoses it, and drives the fix, not just the one who wrote the original standard We'll turn each into
• . Requirements: Could be the "Desired Skills & Expertise" list? Actually that list includes experience, ability to work with data, influence stakeholders, etc. That seems like requirements. We'll put that as Requirements. Qualifications: "Technical Qualifications" list: Hands-on experience working with Databricks is required, Strong data analysis skills..., Ability to understand..., Working knowledge of Lakehouse..., Comfort partnering closely... We'll put that as Qualifications. Skills: Could be "Preferred Experience" and "How You Work"? Actually "Preferred Experience" includes experience developing benchmarks, building semantic layers, familiarity with risk management etc. That's more like preferred qualifications/skills. And "How You Work" describes behavioral traits. Could be Skills. We'll combine those into Skills section. Benefits: The "Why work at Curinos?" paragraph includes benefits. We'll extract that. Pay: Salary Range. We must not include boilerplate like "Applying", "Inclusivity at Curinos", EEO, etc. Remove those. Now produce HTML fragment with

  headings and

  or

  • . Ensure no extra text outside. Let's craft. About the role: combine intro paragraphs into one

    . Might be long but okay. Responsibilities:

    • each. Requirements:
      • each bullet from Desired Skills & Expertise. Qualifications:
        • each bullet from Technical Qualifications. Skills: combine Preferred Experience and How You Work into
          • each? Could be separate paragraphs but we can list as
            • . We'll split each sentence as separate
            • maybe. Benefits:

              with benefits description. Pay:

              with salary range. Let's extract exact text. From posting: About the role text: I'll copy the paragraph(s) before "Job Description". Actually there is "Job Description" heading but we should not repeat as heading. The text after "Job Description" is part of About the role. We'll combine. Full About the role text: "Curinos empowers financial institutions to put customers at the center of every decision. Our AI-first platform transforms proprietary data, advanced analytics and deep financial services expertise into timely recommendations - delivered right where teams work. The result: confident decisions, stronger customer relationships, and lasting, profitable growth. Curinos operates under a hybrid modality and has office locations in New York, Chicago, Boston, Toronto, and London. This role is open to hybrid/ remote candidates based in the United States. This highly visible individual contributor role sits at the intersection of Product, Platform, Analytics, and Subject Matter Expertise. You will establish and maintain the standards that govern how Curinos benchmarks and metrics are defined, calculated, approved, and evolved. In practice, benchmark methodology includes the rules, calculations, eligibility and sufficiency criteria, data sources, quality standards, contractual considerations, and governance processes that make consistent, comparable, and trusted. You will also serve as the steward of the shared semantic layer that powers Curinos One. This semantic layer is the common foundation for business logic, canonical metric definitions, calculation rules, metadata, lineage, and analytical concepts. It lets teams build from the same definitions rather than recreating them product by product, whether the consumer is a BI dashboard, an internal analyst, or an AI-driven feature within Curinos One. This role combines analytical rigor, strong process leadership, and hands-on data investigation. You will dig into datasets, calculations, and business logic while designing governance that teams want to use because it reduces ambiguity, improves quality, and helps them move faster. You own the semantic layer and benchmark methodology as a data product, with a roadmap focused on trust, quality, and reusability rather than customer-facing features, and with real authority over what gets approved and how the underlying data asset is maintained over time." That's fine. Responsibilities bullets: - Define Benchmark Methodologies Own the standards, rules, calculations, eligibility criteria, data-use considerations, and documentation that make Curinos benchmarks consistent, explainable, and fit for client use - Govern Methodology Decisions and Change Hold approval authority over benchmark methodology changes. Lead the review and approval process for benchmark methodology changes, working with Product, Data, Risk, Legal, and client-facing teams to evaluate trade-offs, weigh controls, and reach sound, well-supported decisions - Build the Shared Semantic Foundation for Curinos One Steward the common metric definitions, business logic, metadata, lineage, and glossary, including field-level definitions and data grain specifications, so teams can reuse trusted analytical concepts across - Steward the Semantic Layer as a Living Asset Act as the accountable owner of the semantic layer's ongoing health, including data quality, lineage accuracy, and definition drift over time. When a metric definition degrades, a data source changes, or lineage breaks, you are the one who catches it, diagnoses it, and drives the fix, not just the one who wrote the original standard We'll keep as is. Requirements (Desired Skills & Expertise): List: - 4+ years of experience in Product Management, Data Governance, Analytics, Data Strategy, Technical Success, Advisory Services, Business Intelligence, or a similar role involving analytical products, data-intensive client solutions, methodology design, business logic, or cross-functional decision-making - Demonstrated ability to work directly with data and methodology, including investigating datasets, understanding calculations, challenging assumptions, and translating findings into durable standards or decisions - Proven ability to influence and align stakeholders across multiple teams without direct authority - Experience creating, improving, and operationalizing governance, review, quality, or decision-making processes that people adopt and use consistently - Ability to facilitate decisions across diverse stakeholder groups and drive complex analytical or methodological questions to resolution - Excellent written communication and documentation skills, with the ability to make technical and methodological concepts clear to varied audiences. - Strong knowledge of retail banking products and data, including deposit and loan pricing,