Director, Data Analysis

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about KPMG and then "KPMG is currently seeking a Director, Data Analysis to join our Digital Nexus organization." That's like about the role. Then Responsibilities list, Qualifications list, Benefits (they mention comprehensive benefits package, details). Pay: they mention salary ranges link but not actual numbers; they say "If required, the ranges displayed below or via the URL below are specifically for those potential hires...". No explicit salary range given, just link. According to rules: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: they do state benefits package details (medical, dental, vision, disability, life insurance, 401(k), personal well-being, PTO, holidays, breaks). So we can include Benefits section. Pay: they do not give explicit salary numbers; they just mention link. Should we include Pay? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Since they didn't state a specific salary range, we should not include Pay section. Schedule: they mention standard work hours, years of service, PTO, holidays, breaks. That's schedule info. They say "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." That's schedule info. So we can include Schedule section. However we need to ensure we only include sections with real specific content. The schedule content is specific enough. So include Schedule. We need headings:

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role (intro), Responsibilities, Qualifications (they used Qualifications heading), Benefits, Schedule. Possibly also Requirements? They have Qualifications but not separate Requirements. Could combine Qualifications as Requirements? The instruction: use headings for those labels if present. The posting has "Qualifications:" heading. So we use

Qualifications

. They also have "Responsibilities:" heading. So

Responsibilities

. They have no explicit "About the role" heading but we can create one for the intro paragraph. It's allowed as a section heading. We should not repeat job title as heading. So we can have

About the role

with the intro paragraph. We need to strip boilerplate: remove EEO, equal-opportunity, scam-warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove lines like "No phone calls or agencies please." "KPMG recruits on a rolling basis." etc. Also remove visa sponsorship details? That's part of Qualifications? It's a requirement: "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)". That's a qualification/requirement; we should keep it as part of Qualifications list. It's substantive. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details about benefits, schedule, etc. We need to format lists with

• . For responsibilities and qualifications, each bullet is a line starting with a capital letter? We'll convert each line to
• . Ensure we keep the full text. Let's extract sections. Intro paragraph: "Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services for organizations in today's most important industries. Our growth is driven by delivering real results for our clients. It's also enabled by our culture, which encourages individual development, embraces an inclusive environment, rewards innovative excellence and supports our communities. With qualities like those, it's no wonder we're consistently ranked among the best companies to work for by Fortune Magazine, Consulting Magazine, Seramount, Fair360 and others. If you're as passionate about your future as we are, join our team. KPMG is currently seeking a Director, Data Analysis to join our Digital Nexus organization." We can keep that as

  under About the role. Responsibilities: list after "Responsibilities:" includes: - Partner with business stakeholders to understand data and information needs, translating requirements into scalable solutions aligned with enterprise data strategy - Lead the delivery of complex data and information initiatives, ensuring successful execution, alignment with business objectives, and measurable outcomes - Drive innovation through the evaluation and adoption of AI, analytics, and emerging technologies to improve insights, automate processes, and enhance decision-making - Oversee data analysis and information architecture activities, including data modeling, interface documentation, data mapping, and governance best practices - Build, mentor, and lead high-performing teams while fostering collaboration between business stakeholders, technical teams, and data subject matter experts (SMEs) - Manage vendor relationships and sourcing activities, including resource onboarding, contract negotiations, Statements of Work (SOWs), Requests for Proposals (RFPs), and external partner performance - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment We'll put each as

• . Qualifications: after "Qualifications:" includes: - Minimum ten years of recent experience in data organizations, including minimum five years in a leadership, architecture, or data management role - Bachelor's degree from an accredited college or university is required - Proven expertise delivering data analysis, governance, integration, migration, and transformation initiatives within large-scale enterprise environments; experience within a Chief Data Office (CDO) organization preferred - Strong knowledge of multiple data domains, including finance, human resources, CRM, and other enterprise data areas, with legal, risk, and compliance (LRC) domain expertise considered a plus - Hands-on experience with data analysis and reporting tools, including SQL, Python, and/or Alteryx, with the ability to derive actionable insights from complex datasets - Demonstrate success managing internal teams and third-party vendors, including resource oversight, contract administration, and SOW management; exceptional organizational, problem-solving, communication, and presentation skills, with the ability to manage multiple concurrent initiatives and effectively translate complex technical concepts for business and executive stakeholders - Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa) We'll keep each as
• . Benefits: after "In addition, KPMG is proud to offer a comprehensive, competitive benefits package, with options designed to help you make the best decisions for yourself, your family, and your lifestyle. Available benefits are based on eligibility. Our Total Rewards package includes a variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support your mental health. Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday. Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." We need to turn that into a Benefits section with maybe a

  describing benefits and maybe a

  for list? The benefits are described in prose; we could keep as

  . Could also list items: medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, personal well-being benefits, PTO, holidays, breaks. But we must not invent details; we can keep as prose. The rule: Use

  • for any list of duties/requirements/benefits, and

    for prose. Since benefits are described in prose, we can keep as

    . However there is a list embedded: "variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits". Could be considered a list but it's okay as prose. Schedule: The schedule info is also in the same paragraph as benefits; but we can separate schedule into its own section. The schedule details: "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." We can put that as

    under Schedule. We must not include Pay section because no explicit salary range. We must not include duplicated lines, boilerplate like EEO, etc. Remove lines about "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations." That's about pay but no actual range; we should not create Pay section. However we might consider including a short note about pay transparency link? The rule: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state that they comply with regulations and provide a link for salary ranges. That is about pay but not stating actual range. Should we include Pay? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (they mention compliance and link). However they didn't state actual numbers. The rule also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The link is not filler but it's a reference. However the section would be just a link; maybe we could include a Pay section with a

    containing the link? But that might be considered filler? The link is substantive info about where to find salary ranges. The instruction says: "Prefer a few substantive sections over many thin ones." If we include Pay, it's thin (just a link). Might be better to omit Pay section as they didn't give actual range. The rule about not creating Pay unless posting actually states them: they did state something about pay (they mention compliance and link). But it's not a range. I'd lean to omit Pay section to avoid thin section. The schedule and benefits are substantive. Now we need to output only HTML fragment, no /, no markdown. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    ...

    Schedule

    ...

    Make sure to preserve all