Associate Director, AI Application Engineer

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about KPMG, then "KPMG is currently seeking an Associate Director, AI Application Engineer to join our Digital Nexus Technology organization." That's like a brief description. Then Responsibilities list (bulleted). Then Qualifications list (bulleted). Then Benefits: they mention comprehensive benefits package, medical/dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. Also they mention salary ranges link but not actual numbers. According to rules: include Pay/Schedule/Benefits sections only if posting actually states them. Benefits are stated (they describe benefits). So we can include a Benefits section. Pay: they mention salary ranges but not actual numbers; they say "If required, the ranges displayed below or via the URL below are specifically for those potential hires..." They do not give explicit numbers. The rule says 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. Since they do not give explicit salary numbers, we should not create a Pay section. Schedule: they mention standard work hours, 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-related info (PTO, holidays, breaks). So we could include a Schedule section with that info. However we need to ensure we don't create filler. The content is substantive: description of PTO, holidays, breaks. So we can include Schedule. We need headings:

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections that have real content: About the role (intro paragraph), Responsibilities, Qualifications, Benefits, Schedule. Possibly also Requirements? They have Qualifications; maybe we treat Qualifications as Requirements. The posting uses "Qualifications:" heading. We'll map that to

Qualifications

. They also have "Responsibilities:" heading. We'll map that. We need to not repeat job title as heading. The page already shows it, so we don't add a heading for the title. We need to use

• for any list of duties/requirements/benefits. For prose, use

  . We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, visa sponsorship note? Actually visa sponsorship note is part of Qualifications? It says "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 is substantive? It's a requirement about work authorization. Should we keep? It's a qualification/requirement. It's not boilerplate; it's a specific requirement. So we should keep it as part of Qualifications. We need to remove the EEO statement, the "KPMG is an equal opportunity employer..." etc. Also remove the "No phone calls or agencies please." etc. Also remove the "Los Angeles County applicants: Material job duties..." that's a legal notice; maybe considered boilerplate? It's specific to location but still legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That includes legal notices like Fair Chance Act. So we should remove that Los Angeles County paragraph. Also remove the link to salary ranges and benefits link? The benefits link is part of benefits description: "Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." That's a reference; we could keep the sentence but maybe it's okay. It's not boilerplate; it's a pointer. We'll keep. Also remove the "Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6690_9_26". That's a link to salary ranges; but we are not including Pay section, but we could keep the link as part of maybe a note? However it's about pay; but we are not including Pay section. The rule says do not create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't forbid mentioning pay elsewhere. But we might keep it as a

  under maybe About the role? However it's a link to salary ranges; it's not a specific salary. Might be considered filler? It's not placeholder like "commensurate with experience". It's a real link. I'd keep it as a paragraph maybe under About the role or separate? But we need to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that link. Where to place? Could be under a

  after the intro. But we need to avoid creating a Pay section. So we can just include a paragraph with that link. Similarly, the benefits link: "Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." Keep as paragraph. Now we need to structure. We'll start with an

  for the introductory paragraph about KPMG being a great place to work, etc., up to "KPMG is currently seeking an Associate Director, AI Application Engineer to join our Digital Nexus Technology organization." Then

  Responsibilities

  with
  • each bullet. Then

    Qualifications

    with
    • each bullet. Then

      Benefits

      with
      • each benefit item. Then

        Schedule

        with

        describing PTO, holidays, breaks. We also need to include the salary range link and benefits link maybe as

        under About the role or after Qualifications? Could be under About the role as extra info. We must not include any heading that has no real content. So we will not include Pay. Now let's extract the content. 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 an Associate Director, AI Application Engineer to join our Digital Nexus Technology organization." We'll keep that as a

        . Now Responsibilities bullets (as listed): - Lead a team of engineers in the design, development, deployment, and support of AI-enabled applications and platform capabilities using .NET Core, C#, Python, and modern cloud-native technologies - Define technical vision, architecture, and roadmaps for AI solutions, driving delivery, solution design, reviews, and integration with Azure, Google Cloud, enterprise platforms, APIs, and external systems - Design and implement advanced AI capabilities, including agent orchestration, enterprise search, retrieval-augmented generation (RAG), model integration, reusable AI services, and agent-to-agent (A2A) and Model Context Protocol (MCP) interactions - Lead platform engineering and cloud infrastructure initiatives utilizing Kubernetes (AKS), API Management, Terraform, CI/CD pipelines, GitHub Actions, Infrastructure-as-Code, and DevOps/MLOps best practices - Establish engineering standards and governance through code reviews, automated testing, SDLC compliance, security, privacy, risk, identity management, Trusted AI principles, and enterprise architecture controls - Research emerging technologies, recommend innovative solution architectures, present technical strategies to diverse stakeholders, and lead operational support, troubleshooting, performance optimization, and continuous improvement initiatives while fostering a culture of professionalism and accountability - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment. Now Qualifications bullets: - Minimum eight years of recent technology experience, including a minimum of five years leading engineering teams and at least two years delivering AI platforms and solutions that drive measurable business outcomes - Bachelor's degree from an accredited college or university is preferred; high school diploma or GED required - Experience designing, building, and operating AI-enabled applications, agent-based systems, and enterprise-scale cloud solutions using Azure AI, Google AI services, or comparable cloud-based AI technologies - Strong full-stack development experience with modern technologies including C#, .NET, JavaScript, TypeScript, React.js, Node.js, HTML, and CSS - Deep expertise in cloud engineering, including Azure AI services, Kubernetes (AKS), API development, DevOps practices, CI/CD pipelines, Infrastructure-as-Code, and Terraform; proficiency in automation, scripting, and testing using Python, PowerShell, Bash, YAML, and related development and operational tools - Excellent communication and stakeholder management skills, with the ability to present architecture decisions, technical strategies, and solution recommendations to executive, business, and technical audiences - 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) Now Benefits bullets (extracted): - Comprehensive, competitive benefits package - Variety of 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 (depending on job classification, standard work hours, and years of service) - Calendar of holidays to be observed during the year - Two breaks each year where employees will not be required to use Personal Time Off (one at year end and the other around the July 4th holiday) We could combine some. But we need to preserve all substantive information; we can list each as separate

      • . Now Schedule section: The posting mentions schedule info: "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 already included PTO, holidays, breaks in Benefits. But schedule could be separate: maybe we just keep schedule as a

        describing standard work hours? The posting does not explicitly state standard work hours (like 9-5). It mentions "standard work hours" but not specifics. So schedule section may be redundant with benefits. However we can still include Schedule section with that info (PTO, holidays, breaks). But we