Associate Director, Technology Enablement LRMC (Legal, Risk Management and Compliance)

We need to output HTML fragment with sections: About the role? Not present. Responsibilities, Qualifications, Benefits, Pay, Schedule? The posting includes responsibilities, qualifications, benefits (some description), pay (salary ranges mentioned but not specific numbers). The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have benefits described: "comprehensive, competitive benefits package... medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, personal well-being benefits... Personal Time Off per fiscal year... calendar of holidays... two breaks each year..." That's specific enough for Benefits section. Pay: The posting says "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..." It does not give actual numbers, just says ranges displayed below or via URL. No actual numbers given. So we should NOT create Pay section because no specific salary range is provided. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specifics, so include Benefits. Pay we do not have specific numbers, so omit. Schedule: Not mentioned. So omit. We also need About the role? Not present as a heading; but we could include a short paragraph about the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We have a paragraph at start describing KPMG and the role. That could be considered "About the role". It's substantive. So we can create an

  About the role

  with a

  containing that description (maybe trimmed). Must preserve all substantive information; do not invent or summarize away detail. So we need to keep the description: "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 an Associate Director, LRMC (Legal, Risk Management and Compliance) Technology Enablement to join our Legal Risk Management Compliance organization." We should not repeat the job title as a heading, but we can include it in the paragraph. That's fine. Now Responsibilities: we have a block starting with "Responsibilities:" then a list of items separated by semicolons? Actually each responsibility is a sentence ending with semicolon. We need to turn each into

• . The text: - Provide end-to-end management and delivery oversight of technology projects, from business case refinement through deployment and continuous improvement, ensuring project goals are met with minimal guidance; prioritize enhancements for existing systems based on stakeholder feedback and manage the execution of the delivery roadmap - Assume business and product ownership of assigned implemented solutions, managing system enhancements and updates to support tactical requirements; promote customer satisfaction by ensuring technology solutions meet the immediate operational requirements of business stakeholders - Oversee the technology delivery lifecycle, ensuring that core technical teams adhere to established Software Development Life Cycle (SDLC) processes; monitor technical teams to ensure they generate the required documentation evidencing compliance with firm policy, risk management, and security standards - Facilitate transparent progress and status reporting to project sponsors, portfolio stakeholders, and department leaders; monitor and track project budgets, tracking spend against plan, identifying variances, and supporting the annual budgeting process - Serve as a technology liaison to department leaders and functional partners within the assigned LRMC portfolio, aligning digital delivery with tactical plans; interact regularly with department leaders and Digital Nexus, proactively sharing ideas to improve service and recommending digital solutions that support business value - Direct the daily workflows of cross-functional, matrixed, on- and offshore resources to execute project deliverables on time and within budget; mentor, develop, and share technical and process expertise with junior team members and peers to build organizational capability and support career progression - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment We need to split each bullet at semicolons? Actually each bullet contains two clauses separated by semicolon; but it's still one responsibility. We can keep as one
• containing the whole sentence (including semicolon). That's fine. Now Qualifications: block starting with "Qualifications:" then list items separated by semicolons or line breaks. We need to turn each into
• . Let's parse: - Minimum eight years of recent progressive experience in technology project/program management, business systems enablement, or strategic technology portfolio management; proven track record of successfully delivering complex, enterprise-grade technology projects or programs within a matrixed corporate environment - Master's degree from an accredited college or university or relevant advanced degree is preferred; Bachelor's degree from an accredited college or university is required; Project Management Professional (PMP), Program Management Professional (PgMP), or equivalent project/program delivery certifications is a plus but not required - Strong working knowledge of various project delivery methodologies (such as Agile, Waterfall, Hybrid) and software development lifecycles (SDLC); solid understanding of IT compliance, SDLC governance, and risk management documentation standards - Demonstrated capability in financial management, including project budgeting, forecasting, and resource allocation - Proficient stakeholder management skills with the ability to interact confidently with and influence department leaders and delivery partners - Proven experience managing, mentoring, and developing direct reports and leading cross-functional, multi-disciplinary teams - Applicant 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 should keep each as
• . Note that some items have multiple clauses separated by semicolons; still one
• . Now Benefits: we have paragraph after qualifications: "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. 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. Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=7872_9_26 KPMG offers a comprehensive compensation and benefits package." We need to extract benefits specifics: medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, robust suite of personal well-being benefits to support mental health, Personal Time Off per fiscal year, calendar of holidays, two breaks each year (year end and around July 4th). Also mention that details can be found at link. We should preserve all substantive info. We can make a
  • for each benefit item. We should not include the salary range link as part of Benefits? It's about pay transparency; but it's a link for salary ranges. Since we are not including Pay section, we could still include the link as part of Benefits? It's about pay transparency, not benefits. Probably better to omit that link as it's not benefits. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive info about salary ranges. But we are not making a Pay section; we could still include it as a

    under Benefits? Might be misplaced. Perhaps we should include a Pay section only if we have actual salary range; we don't. The link is about salary ranges, but we could still mention that salary ranges are available via link, but that's still pay info. Since we are not making Pay section, maybe we should still include a short

    noting that salary ranges are available via link (but that's still pay). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that salary ranges are displayed below or via URL. So there is some pay info, but not specific numbers. The instruction says never create Pay section unless posting actually states them. It does state that salary ranges are displayed (though not given). That's still stating them, albeit not giving numbers. However the instruction also says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The posting says "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." That's not a placeholder like "varies". It's saying ranges are displayed below or via URL. Since we don't have the actual ranges in the text, we could still include a Pay section with a

    that says salary ranges are available via the provided link. That's not filler; it's actual info. However the instruction also says "Prefer a few substantive sections over many thin ones." Might be okay to include Pay section with a short paragraph. But we need to decide. The example of filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". The posting does not have those; it says ranges displayed below or via URL. So we could include Pay section with a

    that says "Salary ranges are available via the link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=7872_9_26". That's substantive. Similarly, we have no schedule info, so omit Schedule. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not include sections like Requirements, Skills (none). Use

    for each. Now we need to output only HTML fragment, no /, no markdown