Data Risk Director
Huntington National Bank · Charlotte, NC · 1 mo ago
Finance$155k–$255k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes Job Summary, Responsibilities, Basic Qualifications, Preferred Qualifications, Exempt Status, Workplace Type, Compensation Range, Benefits. We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, Tobacco-Free Hiring Practice, Note to Agency Recruiters, etc. Also remove duplicated lines.
We need to map content:
Job Summary: "Become a member of Huntington’s Independent (2nd Line) Technology Risk function! We are looking for an IT Risk Director to provide primary oversight for the Data Management, Data Governance, and Data Quality risk domains across the Bank. This 2nd line of defense role includes providing credible challenge and partnership for these domains, as well as assisting 1st line risk teams with their understanding and management of associated risks. This role functions as a senior member of the IT Risk team and will be required to provide an independent, expert view in materials and forums, up to and including the Board of Directors."
That's prose, could be under "About the role" heading.
Responsibilities: The bullet list after "Primary responsibilities include leading a high-performing team which will assist you with:" then a list of responsibilities. We need to extract each bullet.
List:
- Providing Risk Management leadership across the Bank’s Data Management, Data Governance, and Data Quality risks
- Providing leadership in determining the Technology Risk Program's strategy and areas of focus
- Ownership of the Data Management risk in the Huntington IT Risk Framework and Taxonomy, including relevant assessments and metrics/indicators
- Engagement and partnership with the Chief Data and Architecture Office (CDAO) and the CDAO business unit, as well as with 1st line risk groups that directly support the CDAO business unit
- Leadership and participation in the quarterly Operational Pillar Risk Assessment, which details the comprehensive, aggregate Technology Risk profile for the Bank and leadership of the annual Data Management Risk Assessment for the Bank
- Providing ‘vertical’ 2nd line IT risk coverage for the Chief Data and Architecture Office (CDAO) business unit and related efforts across the Bank’s segments – to more deeply understand the landscape for those areas of Huntington and therefore enhance engagement in new initiatives, oversight of any remediation programs, etc.
We need to put these in
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, Tobacco-Free Hiring Practice, Note to Agency Recruiters, etc. Also remove duplicated lines.
We need to map content:
Job Summary: "Become a member of Huntington’s Independent (2nd Line) Technology Risk function! We are looking for an IT Risk Director to provide primary oversight for the Data Management, Data Governance, and Data Quality risk domains across the Bank. This 2nd line of defense role includes providing credible challenge and partnership for these domains, as well as assisting 1st line risk teams with their understanding and management of associated risks. This role functions as a senior member of the IT Risk team and will be required to provide an independent, expert view in materials and forums, up to and including the Board of Directors."
That's prose, could be under "About the role" heading.
Responsibilities: The bullet list after "Primary responsibilities include leading a high-performing team which will assist you with:" then a list of responsibilities. We need to extract each bullet.
List:
- Providing Risk Management leadership across the Bank’s Data Management, Data Governance, and Data Quality risks
- Providing leadership in determining the Technology Risk Program's strategy and areas of focus
- Ownership of the Data Management risk in the Huntington IT Risk Framework and Taxonomy, including relevant assessments and metrics/indicators
- Engagement and partnership with the Chief Data and Architecture Office (CDAO) and the CDAO business unit, as well as with 1st line risk groups that directly support the CDAO business unit
- Leadership and participation in the quarterly Operational Pillar Risk Assessment, which details the comprehensive, aggregate Technology Risk profile for the Bank and leadership of the annual Data Management Risk Assessment for the Bank
- Providing ‘vertical’ 2nd line IT risk coverage for the Chief Data and Architecture Office (CDAO) business unit and related efforts across the Bank’s segments – to more deeply understand the landscape for those areas of Huntington and therefore enhance engagement in new initiatives, oversight of any remediation programs, etc.
We need to put these in - .
Basic Qualifications: list:
- Bachelor's degree or equivalent level of work experience
- 10+ years of experience implementing data governance frameworks (e.g., data policies, standards, and controls)
- experience developing and/or implementing data governance policy and standards
- experience working with IT and/or business segments on the analysis of complex business processes and data governance needs
- leading successful teams
We need to preserve all details. Could be under "Requirements" heading.
Preferred Qualifications: list:
- Technical leadership and management experience on data-centric efforts
- Prior experience in risk management and/or regulatory compliance
- Prior experience communicating with regulators
- Ability to work collaboratively and influence/drive consensus across a large and growing company
- Excellent communication and strong interpersonal skills; ability to speak autonomously on behalf of the 2nd Line of Defense and communicate and influence at senior executive level
- Ability to develop, attract, retain a high performing team; demonstrated ability to coach and develop colleagues at all levels of seniority
- Previous experience at a large firm, ideally in a leadership position; prior/current financial services industry experience is also desired
Could be under "Qualifications" heading (or "Preferred Qualifications").
Exempt Status: "Yes" (not eligible for overtime). Could be under "Pay"? Actually Exempt Status is not Pay or Schedule. Could be under "About the role"? But we have a specific heading for "Pay" and "Schedule". Exempt status is not pay or schedule; maybe we can include under "About the role" as a short sentence? But we must not create sections with filler. We could include Exempt Status in a paragraph under "About the role" or maybe under "Pay"? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning these are examples, not mandatory list. We can create other headings if needed, but better to stick to these. Exempt status could be placed under "About the role" as a note.
Workplace Type: "Office" with description about flexible work arrangement. Could be under "Schedule"? Actually schedule is about work hours; workplace type is about office vs remote. Could be under "Schedule" heading? Not ideal. Could be under "About the role" as well. But we have a "Schedule" heading; maybe we can put workplace type there? The instruction: include a section ONLY when posting has real, specific content for it. Workplace Type is specific content; we could create a heading "Workplace Type" but not in the list of examples. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for those categories; but we could also use other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; we should map content to those headings where appropriate. For workplace type, maybe we can put under "Schedule"? Not exactly. Could be under "About the role". But we might also create a "Workplace Type" heading if we think it's needed; but the instruction says prefer a few substantive sections over many thin ones. So we should try to incorporate workplace type into existing sections, maybe under "About the role" or "Schedule". Since schedule is about work hours, not location. Could put under "About the role". Similarly Exempt status could be under "About the role". Benefits: we have description of benefits: health insurance, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO). That's Benefits heading.
Pay: Compensation Range $155,000 - $255,000 annual salary plus note about actual compensation varying and incentive compensation plan. That's Pay heading.
Schedule: Not explicitly given; we have workplace type but not schedule. Could we infer schedule? Not given. So we should not create Schedule section if no specific content. So we omit Schedule.
Skills: Not explicitly listed; we have some skills in preferred qualifications (communication, interpersonal, influence). Could be under Skills heading. But we already have Qualifications sections. Could combine. The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. That's six sections. That seems fine.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, Tobacco-Free Hiring Practice, Note to Agency Recruiters, etc.
We must preserve all substantive info. Let's extract all substantive sentences.
Job Summary paragraph: we have that.
Responsibilities list: we have.
Basic Qualifications list: we have.
Preferred Qualifications list: we have.
Exempt Status: "Yes" (not eligible for overtime). We'll include as a sentence under About the role maybe: "Exempt status: Yes (not eligible for overtime pay)."
Workplace Type: description: "Office. Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team."
We need to preserve that. Could be a paragraph under About the role.
Compensation Range: "$155,000 - $255,000 annual salary The compensation range represents the anticipated low and high end of the base compensation range for this position. Actual compensation will vary based on various factors including but not limited to location, experience, and education. Colleagues in this position are also eligible to participate in an applicable incentive compensation plan."
Benefits: "In addition, Huntington provides a variety of benefits to colleagues, including health insurance coverage, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO)."
We need to ensure we didn't miss any other substantive info: maybe "Our Approach to Office Workplace Type" heading inside the text; we just keep the sentences.
Now produce HTML:
About the role
Become a member of Huntington’s Independent (2nd Line) Technology Risk function! We are looking for an IT Risk Director to provide primary oversight for the Data Management, Data Governance, and Data Quality risk domains across the Bank. This 2nd line of defense role includes providing credible challenge and partnership for these domains, as well as assisting 1st line risk teams with their understanding and management of associated risks. This role functions as a senior member of the IT Risk team and will be required to provide an independent, expert view in materials and forums, up to and including the Board of Directors. Exempt status: Yes (not eligible for overtime pay). Our approach to office work: Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team.
Responsibilities
- Providing Risk Management leadership across the Bank’s Data Management, Data Governance, and Data Quality risks
- Providing leadership in determining the Technology Risk Program's strategy and areas of focus
- Ownership of the Data Management risk in the Huntington IT Risk Framework and Taxonomy, including relevant assessments and metrics/indicators
- Engagement and partnership with the Chief Data and Architecture Office (CDAO) and the CDAO business unit, as well as with 1st line risk groups that directly support the CDAO business unit
- Leadership and participation in the quarterly Operational Pillar Risk Assessment, which details the comprehensive, aggregate Technology Risk profile for the Bank and leadership of the annual Data Management Risk Assessment for the Bank
- Providing ‘vertical’ 2nd line IT risk coverage for the Chief Data and Architecture Office (CDAO) business unit and related efforts across the Bank’s segments – to more deeply understand the landscape for those areas of Huntington and therefore enhance engagement in new initiatives, oversight of any remediation programs, etc.
Requirements
- Bachelor's degree or equivalent level of work experience
- 10+ years of experience implementing data governance frameworks (e.g., data policies, standards, and controls)
- Experience developing and/or implementing data governance policy and standards
- Experience working with IT and/or business segments on the analysis of complex business processes and data governance needs
- Leading successful teams
Qualifications
- Technical leadership and management experience on data-centric efforts
- Prior experience in risk management and/or regulatory compliance
- Prior experience communicating with regulators
- Ability to work collaboratively and influence/drive consensus across a large and growing company
- Excellent communication and strong interpersonal skills; ability to speak
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for those categories; but we could also use other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; we should map content to those headings where appropriate. For workplace type, maybe we can put under "Schedule"? Not exactly. Could be under "About the role". But we might also create a "Workplace Type" heading if we think it's needed; but the instruction says prefer a few substantive sections over many thin ones. So we should try to incorporate workplace type into existing sections, maybe under "About the role" or "Schedule". Since schedule is about work hours, not location. Could put under "About the role". Similarly Exempt status could be under "About the role". Benefits: we have description of benefits: health insurance, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO). That's Benefits heading.
Pay: Compensation Range $155,000 - $255,000 annual salary plus note about actual compensation varying and incentive compensation plan. That's Pay heading.
Schedule: Not explicitly given; we have workplace type but not schedule. Could we infer schedule? Not given. So we should not create Schedule section if no specific content. So we omit Schedule.
Skills: Not explicitly listed; we have some skills in preferred qualifications (communication, interpersonal, influence). Could be under Skills heading. But we already have Qualifications sections. Could combine. The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. That's six sections. That seems fine.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, Tobacco-Free Hiring Practice, Note to Agency Recruiters, etc.
We must preserve all substantive info. Let's extract all substantive sentences.
Job Summary paragraph: we have that.
Responsibilities list: we have.
Basic Qualifications list: we have.
Preferred Qualifications list: we have.
Exempt Status: "Yes" (not eligible for overtime). We'll include as a sentence under About the role maybe: "Exempt status: Yes (not eligible for overtime pay)."
Workplace Type: description: "Office. Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team."
We need to preserve that. Could be a paragraph under About the role.
Compensation Range: "$155,000 - $255,000 annual salary The compensation range represents the anticipated low and high end of the base compensation range for this position. Actual compensation will vary based on various factors including but not limited to location, experience, and education. Colleagues in this position are also eligible to participate in an applicable incentive compensation plan."
Benefits: "In addition, Huntington provides a variety of benefits to colleagues, including health insurance coverage, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO)."
We need to ensure we didn't miss any other substantive info: maybe "Our Approach to Office Workplace Type" heading inside the text; we just keep the sentences.
Now produce HTML:
About the role
About the role
Become a member of Huntington’s Independent (2nd Line) Technology Risk function! We are looking for an IT Risk Director to provide primary oversight for the Data Management, Data Governance, and Data Quality risk domains across the Bank. This 2nd line of defense role includes providing credible challenge and partnership for these domains, as well as assisting 1st line risk teams with their understanding and management of associated risks. This role functions as a senior member of the IT Risk team and will be required to provide an independent, expert view in materials and forums, up to and including the Board of Directors. Exempt status: Yes (not eligible for overtime pay). Our approach to office work: Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team.
Responsibilities
- Providing Risk Management leadership across the Bank’s Data Management, Data Governance, and Data Quality risks
- Providing leadership in determining the Technology Risk Program's strategy and areas of focus
- Ownership of the Data Management risk in the Huntington IT Risk Framework and Taxonomy, including relevant assessments and metrics/indicators
- Engagement and partnership with the Chief Data and Architecture Office (CDAO) and the CDAO business unit, as well as with 1st line risk groups that directly support the CDAO business unit
- Leadership and participation in the quarterly Operational Pillar Risk Assessment, which details the comprehensive, aggregate Technology Risk profile for the Bank and leadership of the annual Data Management Risk Assessment for the Bank
- Providing ‘vertical’ 2nd line IT risk coverage for the Chief Data and Architecture Office (CDAO) business unit and related efforts across the Bank’s segments – to more deeply understand the landscape for those areas of Huntington and therefore enhance engagement in new initiatives, oversight of any remediation programs, etc.
Requirements
- Bachelor's degree or equivalent level of work experience
- 10+ years of experience implementing data governance frameworks (e.g., data policies, standards, and controls)
- Experience developing and/or implementing data governance policy and standards
- Experience working with IT and/or business segments on the analysis of complex business processes and data governance needs
- Leading successful teams
Qualifications
- Technical leadership and management experience on data-centric efforts
- Prior experience in risk management and/or regulatory compliance
- Prior experience communicating with regulators
- Ability to work collaboratively and influence/drive consensus across a large and growing company
- Excellent communication and strong interpersonal skills; ability to speak