Enterprise Data Management Lead

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - Intro paragraph about WSFS Bank (maybe "About the role"? Actually the description includes mission, etc. Could be "About the role" or "About WSFS Bank". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: - Job Description (intro) describing WSFS Bank mission etc. Could be "About the role" or "About WSFS". Probably "About the role" fits. - Job Responsibilities: list of responsibilities. - Minimum Qualifications: list of qualifications (education, experience). Could be "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. Usually "Minimum Qualifications" could be under "Qualifications". "Requirements" could be similar. Since we have both education and experience, we could put under "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have separate headings possible. However we should not create empty sections. We have content for qualifications (education, experience). Could also have "Skills" section for skills like SQL, communication, etc. The posting includes many skill-like items: proficiency with SQL, strong data profiling, etc. Those could go under Skills. We also have Salary Range and Benefits info. So we need Pay and Benefits sections. Schedule: not mentioned. So omit Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, accommodation, etc. Also remove application instructions, legal, etc. The posting includes accommodation request, EEO statement, etc. Remove those. We must preserve all substantive information. So we need to keep the mission paragraph, responsibilities list, qualifications list, skills list, salary range, benefits description. We need to format as HTML:

About the role

then

... mission paragraph ...

. Then

Responsibilities

then

• ... each responsibility ...

. Then

Qualifications

then maybe split into

for education/experience? Could also separate Requirements and Qualifications but we have only one. We'll put qualifications list. Then

Skills

then
for skill items. Then

Pay

then

salary range ... maybe also mention incentive awards. Keep that. Then

Benefits

then
for benefits items. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't include duplicated lines. The responsibilities list includes many items; we need to copy them exactly as given but as list items. Let's extract responsibilities: From "Job Responsibilities:" list: - Develop and lead the strategy, implementation, and continuous improvement/maturation of Enterprise Data Management and Governance capabilities. - Maintain and evolve the data governance framework, including policies, standards, and operating procedures. - Partner with business lines to understand processes, data flows, and Critical Data Elements (CDEs) to ensure alignment with enterprise data standards. - Collaborate with Data Owners and Data Stewards to promote consistent data usage, quality, and lifecycle practices across the enterprise. - Recommend enhancements to enterprise data processes, governance workflows, and supporting tools to meet strategic objectives. - Identify data quality issues, establish data quality controls and KPIs, and drive improvement actions with business and operations teams. - Conduct gap analysis of existing enterprise data practices to inform target-state governance and lifecycle management models. - Support the definition of metadata standards, data classifications, business definitions, and reference data alignment. - Help business articulate and translate business needs into clear data requirements, definitions, and governance artifacts. - Partner with architecture, analytics, and platform teams to ensure governance and data quality requirements are embedded in enterprise solutions. - Facilitate change management for data ownership, stewardship, data access, retention, and lifecycle controls. - Promote adoption of data governance processes across the Bank through training, communication, and ongoing engagement. - Chair/co-chair the data governance committee - Participate in enterprise data governance committees and support the operationalization of data roles and responsibilities. - Serve as a senior advisor and subject-matter expert for governance standards, lifecycle practices, metadata, and data quality. - Provide leadership, coaching, and guidance to team members and cross-functional partners. Note: Some lines end with period, some not. We'll keep as is. Now Minimum Qualifications list: - Bachelor’s Degree in Computer Science, Information Systems, or related analytical discipline; Master’s Degree preferred or equivalent combination of education and/or work experience. - Minimum of 15 years of progressively responsible experience in enterprise data management, data governance, or related domains in a regulated industry. - Financial services industry experience in banking and/or wealth highly preferred. - Minimum of 10 years working across requirements, design, and governance enablement for data warehouse or cloud data platform solutions (in partnership with architecture/engineering teams). - Demonstrated experience defining, building and transforming data governance, data management, or MDM programs in an enterprise environment. - Demonstrated experience chairing or co-chairing a data governance committee or council, including facilitating cross-functional stakeholder engagement, driving data governance initiatives, and overseeing adherence to data quality, data management, and regulatory requirements. - Experience with information architecture concepts, data modeling concepts, and data integration strategies (without hands-on ETL/ELT ownership). - Experience working with large, complex datasets originating from multiple platforms and business processes. - Experience supporting BI and analytics capabilities. - Experience implementing data solutions across banking and wealth platforms. - Strong understanding of data management capabilities including cataloging, lineage, metadata, data definitions, and data quality. - Knowledge of regulatory obligations affecting data (GLBA, SOX, GDPR, etc.). - Strong data profiling and data quality analysis skills. - Proficiency with SQL concepts and data analysis techniques. - Strong skills in Microsoft Office tools (Excel, Access, PowerPoint). - Ability to interpret industry trends and translate them into the enterprise data roadmap. - Understanding of database design and cloud data architecture patterns at a conceptual level. - Experience with modern data cloud platforms, Salesforce, and Financial Services core platforms. - Familiarity with network and PC operating environments. - Project management skills (Agile/Waterfall) and experience with complex project execution. - Excellent written and verbal communication skills. - Ability to build strong, value-added relationships with business partners and technology teams. - Ability to interface with regulatory bodies and audit teams. - Understanding of business case development and ROI frameworks. - Ability? Actually text: "Understanding of business case development and ROI frameworks." - Ability to travel within the WSFS Bank footprint in the Greater Philadelphia region as needed. - WSFS Bank will only consider candidates who are presently authorized to work for any employer in the United States and who will not require work visa sponsorship from WSFS Bank now or in the future in order to retain their authorization to work in the United States. We need to decide what goes under Qualifications vs Skills. The instruction includes Skills as a possible heading. Many of the items are skills (SQL, Office tools, communication, etc.). However the qualifications list includes education, experience, etc. We could split: Qualifications for education/experience requirements; Skills for technical/soft skills. But we must not create thin sections. However we have enough content for both. Let's define: Qualifications: education, years experience, industry experience, etc. Could include the first few items about degree, years, financial services, etc. But many items are also experience/skills. Simplify: Use Qualifications for the bullet list under "Minimum Qualifications" (the whole block). Then Skills maybe not needed. But we have many skill-specific items that could be considered part of qualifications. However the instruction says we can include Skills section if posting has real specific content for it. The posting does have skill-specific items like SQL, Office tools, communication, etc. So we could create Skills section for those. But we must not duplicate content. If we put all qualifications under Qualifications, we would not need Skills. However we might miss highlighting skills. But the instruction says preserve ALL substantive information; we can keep them under Qualifications. That's fine. Then we would not have a Skills section, which is okay if we don't have specific content for Skills beyond what's already in Qualifications. However the instruction says "Prefer a few substantive sections over many thin ones." So better to have fewer sections. So we could combine everything into Qualifications and Responsibilities, plus Pay and Benefits. That's four sections. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to ensure we don't include Schedule. Now we need to strip out boilerplate: The accommodation request, EEO statement, etc. Also the line about "For more information about Associate benefits, please visit https://..." maybe we can keep as part of Benefits? It's a link; but it's more like a reference. Might be considered boilerplate? It's a link to benefits info. Could keep but it's not substantive? It's a pointer. Might be considered not essential. Safer to omit. Also remove the line "WSFS Bank is inclusive and supportive of individual needs..." etc. That's EEO/accommodation boilerplate. Remove. Also remove the line about "WSFS is an equal opportunity employer..." etc. Remove. Now we need to format. Let's craft HTML:

About the role

At WSFS Bank, we empower our Associates to grow their careers, guide our customers to secure their financial futures, and actively support our Communities so they can fully thrive. Careers with WSFS Bank offer an inclusive and supportive culture, competitive salaries, advancement opportunities, and more. We are the region's locally headquartered bank and wealth management company. We are honored to consistently be named a Top Workplace by our Associates, who make a difference every day for the people, businesses, and Communities we serve. We Stand For Service® is more than part of our name, it’s our mission and our purpose. The Enterprise Data Management Lead drives the strategy, standards, and execution of enterprise data governance and lifecycle management practices across WSFS. The role focuses on establishing and maintaining frameworks, policies, and processes that ensure WSFS data is trusted, well‑defined, high‑quality, and appropriately controlled from creation through archival. The Lead partners with Data Owners, Data Stewards, business leaders, and technology teams to advance data maturity, support analytics and regulatory needs, and enable operational efficiency. While highly knowledgeable about data concepts and architecture principles, this is not a hands‑on engineering or ETL/ELT role; the focus is on embedding governance, quality, and lifecycle requirements through partnership and enterprise influence.

Then Responsibilities ul. Then Qualifications ul. Then Pay

salary range and incentive awards. Then Benefits

list of benefits. We need to ensure we preserve all substantive information from the benefits paragraph: "WSFS provides a competitive benefits package, which includes medical, dental, and vision coverage; a 401(k) plan; life, accident, and disability insurance; flexible spending accounts (FSAs) and health savings accounts (HSAs); and wellness programs. Additional benefits may include paid parental leave, military leave, vacation and other paid time off, sick leave in accordance with applicable state laws, and paid holidays. Benefit offerings are subject to eligibility requirements, legal limitations, and may vary based on an Associate’s location and employment status." We can turn that into a
with each benefit as
• . However the sentence includes semicolons separating items. We'll split accordingly. List: - medical, dental, and vision coverage - a 401(k) plan - life, accident, and disability insurance - flexible spending accounts (FSAs) and health savings accounts (HSAs) - wellness programs - paid