Data Governance for Data Products
U.S. Bank · Minneapolis, MN · 1 mo ago
Information Technology$105k–$124k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, the initial paragraph: "At U.S. Bank, we’re on a journey..." This is about the company, maybe "About the role"? Actually it's about the company culture. Could be "About the role" or "About U.S. Bank". The instruction: use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, the initial paragraph: "At U.S. Bank, we’re on a journey..." This is about the company, maybe "About the role"? Actually it's about the company culture. Could be "About the role" or "About U.S. Bank". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role (or About U.S. Bank). The content: the first paragraph describing mission, values, career opportunities. That's substantive.
Then "Job Description Provides subject matter expertise..." This is responsibilities. So we can have a Responsibilities section with bullet list of duties.
Then "Core competencies: ..." That's skills/qualifications. Could be Skills section.
Then "Basic Qualifications Bachelor's degree..." That's qualifications.
Then "Preferred Skills/Experience ..." That's also skills.
Then "Location expectations This role requires working from a U.S. Bank location three (3) or more days per week." That's schedule? Actually schedule: location expectations. Could be Schedule section (or Work Location). But we only have Schedule heading allowed. We could put location expectations under Schedule? Might be better to create a Schedule section with that content. However schedule usually refers to work schedule (e.g., full-time, part-time). But we have location expectation (hybrid). Could treat as Schedule.
Then "Benefits: Our approach..." That's Benefits section.
Then "Pay Range: $105,400.00 - $124,000.00" That's Pay section.
We should not include boilerplate like EEO, E-Verify, etc. Also remove duplicated lines, application instructions, etc.
We need to preserve all substantive information. So we need to include the details from responsibilities, qualifications, skills, benefits, pay, location expectations.
We must not repeat the job title as heading. The job title is not given explicitly; but we can ignore.
We must not put Job ID/requisition numbers as headings.
We must not create sections with filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
About the role
At U.S. Bank, we’re on a journey to do our best. Helping the customers and businesses we serve to make better and smarter financial decisions and enabling the communities we support to grow and succeed. We believe it takes all of us to bring our shared ambition to life, and each person is unique in their potential. A career with U.S. Bank gives you a wide, ever-growing range of opportunities to discover what makes you thrive at every stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One.
Responsibilities
- Provides subject matter expertise in Enterprise Data Governance, Data Domain Management, and Data Product Governance within the Innovation and Transformation Office, part of Risk Management and Compliance.
- Advances the treatment of data as an enterprise asset through the establishment of data domain accountability, data product ownership, and sustainable governance practices.
- Partners with Data Product Owners, Data Domain Owners, Data Stewards, Business stakeholders, and Technology teams to identify, define, govern, and operationalize risk data products that support critical business capabilities and regulatory requirements.
- Ensures data products are aligned to Enterprise Data Governance policies and standards, while meeting quality, transparency, security, and lifecycle management expectations.
- Supports the creation and management of curated, reusable, and governed data products designed to serve defined business purposes and consumer needs.
- Facilitates documentation of business value, ownership, consumption patterns, data quality expectations, controls, lineage, and lifecycle requirements necessary to establish trusted and scalable data assets.
- Drives adoption of data product management principles by promoting user-centric design, reusability, transparency, and measurable business outcomes.
- Collaborates across Risk programs and Technology organizations to enable modern data architecture capabilities, improve data accessibility, increase operational efficiency, and strengthen regulatory compliance.
- Helps shape guidance on data governance frameworks, data management best practices, metadata and lineage concepts, data quality management, and modern cloud-based data platforms.
- Supports continuous improvement of Risk data governance and data product operating model capabilities to maximize the value, trustworthiness, and strategic use of U.S. Bank's data assets.
Qualifications
- Bachelor's degree, or equivalent work experience
- Four to five years of experience in data governance activities
Skills
- Core competencies: Data Product Lifecycle Management, Data Quality and Defect Management, Metadata and Data Lineage, Product Management mindset, Stakeholder and Consumer Engagement, Modern Data Platforms (Databricks, cloud data platforms, APIs), Change Management and Adoption, Strong analytic and problem solving skills, Strong written and verbal communication skills
- Preferred Skills/Experience: Advanced project management/business analysis knowledge and familiarity with the business line processes and/or applications; Advanced understanding of Data Governance principles; Thorough knowledge of data architecture concepts and data governance tooling
Schedule
This role requires working from a U.S. Bank location three (3) or more days per week.
Benefits
- Healthcare (medical, dental, vision)
- Basic term and optional term life insurance
- Short-term and long-term disability
- Pregnancy disability and parental leave
- 401(k) and employer-funded retirement plan
- Paid vacation (from two to five weeks depending on salary grade and tenure)
- Up to 11 paid holiday opportunities
- Adoption assistance
- Sick and Safe Leave accruals of one hour for every 30 worked, up to 80 hours per calendar year unless otherwise provided by law
Pay
Pay Range: $105,400.00 - $124,000.00
We need to ensure we didn't include any boilerplate like EEO, E-Verify, background check, etc. Also we removed the line about disability accommodations? That's a bit of boilerplate but maybe considered substantive? It's about accommodation request. Might be considered EEO/legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The disability accommodations line is likely part of EEO/legal. So we should remove it. Also we removed the line about "Review our full benefits available by employment status here." That's a link; we can keep the benefits list but drop that line. We also removed the line about "U.S. Bank is an equal opportunity employer..." etc. We also removed the E-Verify paragraph. We also removed the background check paragraphs. We also removed the "Applicants must be able to comply with U.S. Bank policies..." etc. We also removed "Posting may be closed earlier due to high volume of applicants." Now check that we preserved all substantive information: The initial paragraph about mission, values, career opportunities. Yes. Responsibilities: we captured all bullet points from the job description paragraph. Need to ensure we didn't miss any nuance: The original responsibilities paragraph is a long sentence with many clauses. We broke into bullet points covering each clause. Let's verify we captured all: Original: "Provides subject matter expertise in Enterprise Data Governance, Data Domain Management, and Data Product Governance within the Innovation and Transformation Office, part of Risk Management and Compliance. This is a hands-on role responsible for advancing the treatment of data as an enterprise asset through the establishment of data domain accountability, data product ownership, and sustainable governance practices. Partners with Data Product Owners, Data Domain Owners, Data Stewards, Business stakeholders, and Technology teams to identify, define, govern, and operationalize risk data products that support critical business capabilities and regulatory requirements. Ensures data products are aligned to Enterprise Data Governance policies and standards, while meeting quality, transparency, security, and lifecycle management expectations. Supports the creation and management of curated, reusable, and governed data products designed to serve defined business purposes and consumer needs. Facilitates documentation of business value, ownership, consumption patterns, data quality expectations, controls, lineage, and lifecycle requirements necessary to establish trusted and scalable data assets. Drives adoption of data product management principles by promoting user-centric design, reusability, transparency, and measurable business outcomes. Collaborates across Risk programs and Technology organizations to enable modern data architecture capabilities, improve data accessibility, increase operational efficiency, and strengthen regulatory compliance. Helps shape guidance on data governance frameworks, data management best practices, metadata and lineage concepts, data quality management, and modern cloud-based data platforms. Supports continuous improvement of Risk data governance and data product operating model capabilities to maximize the value, trustworthiness, and strategic use of U.S. Bank's data assets." We captured each sentence as a bullet. Good. Qualifications: Bachelor's degree, or equivalent work experience; Four to five years of experience in data governance activities. Good. Skills: we combined core competencies and preferred skills. Might be better to separate into Skills and Preferred Skills but we only have Skills heading allowed. Could still list both under Skills. That's fine. Schedule: location expectation. Benefits: we listed all benefits from the list. Ensure we didn't miss any: Healthcare (medical, dental, vision); Basic term and optional term life insurance; Short-term and long-term disability; Pregnancy disability and parental leave; 401(k) and employer-funded retirement plan; Paid vacation (from two to five weeks depending on salary grade and tenure); Up to 11 paid holiday opportunities; Adoption assistance; Sick and Safe Leave accruals of one hour for every 30 worked, up to 80 hours per calendar year unless otherwise provided by law. Good. Pay: Pay Range: $105,400.00 - $124,000.00. We didn't include any mention of "incentive and recognition programs, equity stock purchase 401(k) contribution and pension" because that was in the boilerplate after benefits? Actually after benefits paragraph: "In addition to salary, U.S. Bank offers a comprehensive benefits package, including incentive and recognition programs, equity stock purchase 401(k) contribution and pension (all benefits are subject to eligibility requirements)." That's substantive about benefits. Should we include? It's part of benefits description. We could add a bullet: Incentive and recognition programs, equity stock purchase, 401(k) contribution and pension. However we already have 401(k) and employer-funded retirement plan; but equity stock purchase and pension are extra. The instruction: preserve ALL substantive information. So we should include that. We need to incorporate that into Benefits section. Also the benefits paragraph earlier: "Our approach to benefits and total rewards considers our team members’ whole selves and what may be needed to thrive in and outside work. That's why our benefits are designed to help you and your family boost your health, protect your financial security and give you peace of mind." That's fluff but still substantive? It's descriptive but maybe considered boilerplate? It's not specific benefit; it's generic. Might be considered filler but not disallowed. The instruction: do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies