Product Owner, Data Products & Onboarding
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to include a section only when posting has real, specific content for it — never emit a heading followed by filler/placeholder text.
Thus we need sections: About the role (maybe includes description of team, role, reporting). Responsibilities (list of duties). Requirements (list of must-have). Qualifications (maybe nice-to-have). Skills (maybe combine). Benefits (list). Pay (specific numbers). Schedule (hybrid). Ensure we don't create sections with vague content.
Let's extract content precisely.
About the role: Could combine the introductory paragraphs about Fitch Group, Technology & Data Team, and the specific role description. Must not include boilerplate like "Whether you're an experienced professional or just starting your career, we offer an exciting and supportive environment where you can grow, innovate, and make a difference." That's somewhat generic but still substantive? It's about environment; could be included but maybe it's fluff. The instruction: "Prefer a few substantive sections over many thin ones." Might still include.
But we need to avoid filler like "commensurate with experience", "not specified", etc. That paragraph is not filler.
Thus About the role could be a
containing the description.
Let's gather:
- As a leading, global financial information services provider, Fitch Group delivers vital credit and risk insights, robust data, and dynamic tools to champion more efficient, transparent financial markets. With over 100 years of experience and colleagues in over 30 countries, Fitch Group’s culture of credibility, independence, and transparency is embedded throughout its structure, which includes Fitch Ratings, one of the world’s top three credit ratings agencies, and Fitch Solutions, a leading provider of insights, data and analytics. With dual headquarters in London and New York, Fitch Group is owned by Hearst. Fitch's Technology & Data Team is a dynamic department where innovation meets impact. Our team includes the Chief Data Office, Chief Software Office, Chief Technology Office, Emerging Technology, Shared Technology Services, Technology, Risk and the Executive Program Management Office (EPMO). Driven by our investment in cutting-edge technologies like AI and cloud solutions, we’re home to a diverse range of roles and backgrounds united by a shared passion for leveraging modern technology to drive projects that matter to our organization and clients. We are also proud to be recognized by Built In as a Best Place to Work in Technology 3 years in a row. Whether you're an experienced professional or just starting your career, we offer an exciting and supportive environment where you can grow, innovate, and make a difference. Want to learn more about a career in technology and data at Fitch? Visit: https://careers.fitch.group/content/Technology-and-Data/?locale=en_US
But we must remove the Visit link and maybe the sentence about wanting to learn more? The instruction: remove application instructions. The "Want to learn more..." is like a call to action; could be considered application instruction? Probably remove that sentence and the link.
Thus About the role paragraph ends before that.
Now responsibilities: Let's list bullet points:
- Reporting to: Data Products & Onboarding Leader
- Partnering closely with: Other Marketplace teams, Technology teams, Data Governance, and business teams across the enterprise
- The Product Owner, Data Products & Onboarding will own an assigned portfolio of data products within the domain and lead product delivery through cross-functional pods, partnering with business stakeholders, data producers and consumers, and technology teams from definition through production and lifecycle management.
- How You’ll Make An Impact: A highly visible product role within Fitch’s enterprise data ecosystem. The opportunity to shape how governed enterprise data products are designed, delivered, operated, and continuously improved. A role at the intersection of data product management and data engineering, working with business, technology and data teams to turn complex data needs into trusted data products, enabling safe innovation with data at scale.
We could combine into a
with - items.
Requirements (You May Be a Good Fit If):
- 8+ years across data products, data platforms, data engineering or related disciplines, including significant product ownership or management responsibility.
- Experience owning complex enterprise data products from definition through production and lifecycle management.
- Strong technical understanding of modern data architectures and delivery patterns, including data pipelines, ingestion and transformation, cloud data lakes, and virtualized/federated access.
- Experience with technologies such as AWS/S3, Starburst/Trino, Spark, Snowflake or Databricks, or comparable platforms.
- Strong product management capabilities across roadmap, backlog, prioritization and requirements, translating business needs into scalable data-product solutions.
- Strong stakeholder leadership across business, engineering, architecture and governance teams.
Qualifications (What Would Make You Stand Out):
- Financial markets, credit, risk or financial-data experience
- Prior data engineering, data architecture or technical data-product experience
Skills: Could be derived from requirements but maybe we can treat as separate: technical understanding, product management capabilities, stakeholder leadership. But we already have those in requirements. Might be redundant. The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We have content for Requirements and Qualifications, so we should include both.
Skills: Could be omitted if no distinct content beyond what's already covered. But we could list skills like "Technical understanding of modern data architectures", "Product management capabilities", "Stakeholder leadership". However those are already in requirements. To avoid duplication, maybe we skip Skills section.
Benefits (Why Choose Fitch):
- Hybrid Work Environment: 2 to 3 days a week in office required based on your line of business and location
- A Culture of Learning & Mobility: Dedicated trainings, leadership development and mentorship programs designed to ensure that your time at Fitch will be a continuous learning opportunity
- Investing in Your Future: Retirement planning, financial wellness and tuition reimbursement programs that empower you to achieve your short and long-term goals
- Promoting Health & Wellness: Comprehensive healthcare offerings that prioritize a healthy body & mind
- Supportive Parenting Policies: Family-first policies, including a generous global parental leave plan, designed to help you balance career and family life effectively
- Dedication to Giving Back: Paid volunteer days and support for community engagement initiatives
Also mention AI embedded etc but that's not a benefit.
Pay: Provide the salary range.
- Expected base pay rates for the role will be between USD 130,000 and USD 160,000 per year. Actual salaries will be determined on an individualized basis and may vary based on factors including but not limited to education, training, experience, past performance, and other job-related factors. Base pay is one part of Fitch’s total compensation package, which, depending on the position, may also include commission earnings, discretionary bonuses, long-term incentives, and other benefits sponsored by Fitch.
Schedule: Could be the hybrid work environment detail, but that's already in Benefits. However schedule is separate heading; we could still include schedule with same content? Might be duplicate. The instruction: include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (Hybrid Work Environment: 2 to 3 days a week in office required). That's specific. So we can have Schedule section with that detail. Benefits section can still include other benefits; we could keep hybrid in both? Might be duplication but maybe okay. Better to put hybrid in Schedule and keep other benefits in Benefits (excluding hybrid). Let
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include a section only when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Thus we need sections: About the role (maybe includes description of team, role, reporting). Responsibilities (list of duties). Requirements (list of must-have). Qualifications (maybe nice-to-have). Skills (maybe combine). Benefits (list). Pay (specific numbers). Schedule (hybrid). Ensure we don't create sections with vague content. Let's extract content precisely. About the role: Could combine the introductory paragraphs about Fitch Group, Technology & Data Team, and the specific role description. Must not include boilerplate like "Whether you're an experienced professional or just starting your career, we offer an exciting and supportive environment where you can grow, innovate, and make a difference." That's somewhat generic but still substantive? It's about environment; could be included but maybe it's fluff. The instruction: "Prefer a few substantive sections over many thin ones." Might still include. But we need to avoid filler like "commensurate with experience", "not specified", etc. That paragraph is not filler. Thus About the role could be a
containing the description. Let's gather: - As a leading, global financial information services provider, Fitch Group delivers vital credit and risk insights, robust data, and dynamic tools to champion more efficient, transparent financial markets. With over 100 years of experience and colleagues in over 30 countries, Fitch Group’s culture of credibility, independence, and transparency is embedded throughout its structure, which includes Fitch Ratings, one of the world’s top three credit ratings agencies, and Fitch Solutions, a leading provider of insights, data and analytics. With dual headquarters in London and New York, Fitch Group is owned by Hearst. Fitch's Technology & Data Team is a dynamic department where innovation meets impact. Our team includes the Chief Data Office, Chief Software Office, Chief Technology Office, Emerging Technology, Shared Technology Services, Technology, Risk and the Executive Program Management Office (EPMO). Driven by our investment in cutting-edge technologies like AI and cloud solutions, we’re home to a diverse range of roles and backgrounds united by a shared passion for leveraging modern technology to drive projects that matter to our organization and clients. We are also proud to be recognized by Built In as a Best Place to Work in Technology 3 years in a row. Whether you're an experienced professional or just starting your career, we offer an exciting and supportive environment where you can grow, innovate, and make a difference. Want to learn more about a career in technology and data at Fitch? Visit: https://careers.fitch.group/content/Technology-and-Data/?locale=en_US But we must remove the Visit link and maybe the sentence about wanting to learn more? The instruction: remove application instructions. The "Want to learn more..." is like a call to action; could be considered application instruction? Probably remove that sentence and the link. Thus About the role paragraph ends before that. Now responsibilities: Let's list bullet points: - Reporting to: Data Products & Onboarding Leader - Partnering closely with: Other Marketplace teams, Technology teams, Data Governance, and business teams across the enterprise - The Product Owner, Data Products & Onboarding will own an assigned portfolio of data products within the domain and lead product delivery through cross-functional pods, partnering with business stakeholders, data producers and consumers, and technology teams from definition through production and lifecycle management. - How You’ll Make An Impact: A highly visible product role within Fitch’s enterprise data ecosystem. The opportunity to shape how governed enterprise data products are designed, delivered, operated, and continuously improved. A role at the intersection of data product management and data engineering, working with business, technology and data teams to turn complex data needs into trusted data products, enabling safe innovation with data at scale. We could combine into a
- with
- items. Requirements (You May Be a Good Fit If): - 8+ years across data products, data platforms, data engineering or related disciplines, including significant product ownership or management responsibility. - Experience owning complex enterprise data products from definition through production and lifecycle management. - Strong technical understanding of modern data architectures and delivery patterns, including data pipelines, ingestion and transformation, cloud data lakes, and virtualized/federated access. - Experience with technologies such as AWS/S3, Starburst/Trino, Spark, Snowflake or Databricks, or comparable platforms. - Strong product management capabilities across roadmap, backlog, prioritization and requirements, translating business needs into scalable data-product solutions. - Strong stakeholder leadership across business, engineering, architecture and governance teams. Qualifications (What Would Make You Stand Out): - Financial markets, credit, risk or financial-data experience - Prior data engineering, data architecture or technical data-product experience Skills: Could be derived from requirements but maybe we can treat as separate: technical understanding, product management capabilities, stakeholder leadership. But we already have those in requirements. Might be redundant. The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We have content for Requirements and Qualifications, so we should include both. Skills: Could be omitted if no distinct content beyond what's already covered. But we could list skills like "Technical understanding of modern data architectures", "Product management capabilities", "Stakeholder leadership". However those are already in requirements. To avoid duplication, maybe we skip Skills section. Benefits (Why Choose Fitch): - Hybrid Work Environment: 2 to 3 days a week in office required based on your line of business and location - A Culture of Learning & Mobility: Dedicated trainings, leadership development and mentorship programs designed to ensure that your time at Fitch will be a continuous learning opportunity - Investing in Your Future: Retirement planning, financial wellness and tuition reimbursement programs that empower you to achieve your short and long-term goals - Promoting Health & Wellness: Comprehensive healthcare offerings that prioritize a healthy body & mind - Supportive Parenting Policies: Family-first policies, including a generous global parental leave plan, designed to help you balance career and family life effectively - Dedication to Giving Back: Paid volunteer days and support for community engagement initiatives Also mention AI embedded etc but that's not a benefit. Pay: Provide the salary range. - Expected base pay rates for the role will be between USD 130,000 and USD 160,000 per year. Actual salaries will be determined on an individualized basis and may vary based on factors including but not limited to education, training, experience, past performance, and other job-related factors. Base pay is one part of Fitch’s total compensation package, which, depending on the position, may also include commission earnings, discretionary bonuses, long-term incentives, and other benefits sponsored by Fitch. Schedule: Could be the hybrid work environment detail, but that's already in Benefits. However schedule is separate heading; we could still include schedule with same content? Might be duplicate. The instruction: include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (Hybrid Work Environment: 2 to 3 days a week in office required). That's specific. So we can have Schedule section with that detail. Benefits section can still include other benefits; we could keep hybrid in both? Might be duplication but maybe okay. Better to put hybrid in Schedule and keep other benefits in Benefits (excluding hybrid). Let