Associate Director, AI Application Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: introductory paragraph about KPMG (maybe About the role). Then "Responsibilities:" list. Then "Qualifications:" list. Also mentions benefits: "KPMG is proud to offer a comprehensive, competitive benefits package..." and details about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. Also mentions salary ranges: "KPMG LLP and its subsidiaries ... 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." It does not give actual numbers, just says ranges displayed below or via URL. No actual salary numbers provided. So we should not create Pay section because no specific salary info. Schedule: mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also mentions calendar of holidays and breaks. That's schedule info? Could be considered schedule. But we need specific content: they mention standard work hours? Not given explicitly. They mention PTO, holidays, breaks. That's more benefits/time off. Might be considered Benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated (they describe benefits). So we can include Benefits section. Schedule: they mention standard work hours? Not explicit. They mention PTO per fiscal year, holidays, breaks. That's more time off, could be considered Benefits. Safer to not create Schedule section unless explicit. So we will have sections: About the role (intro paragraph), Responsibilities, Qualifications, Benefits. Possibly Skills? The qualifications list includes skills; but we could combine into Qualifications. The instruction: prefer few substantive sections over many thin ones. So we can have About the role, Responsibilities, Qualifications, Benefits. Use

for each heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines like "No phone calls or agencies please." etc. Also remove EEO statements. Also remove visa sponsorship details? That is substantive? It's about work authorization requirement. That is a qualification? Could be included in 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's a requirement. Should we keep? It's substantive. We'll include in Qualifications. Also mention "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." This is about pay but no actual numbers. We should not create Pay section because no specific salary. But we could include a short paragraph about pay transparency? The instruction: never create Pay section unless posting actually states them. It does state that they comply with salary range display and provides a URL. That is about pay but not actual numbers. Might be considered pay info. However they say "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." Since no ranges are displayed in the text, we could still mention that they provide a link for salary ranges. But we should not invent details. We could include a

  under Benefits? Or maybe a separate Pay section with a note that salary ranges are available via link. But the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they provide salary ranges via URL. So we could include a Pay section with a

  that says "Salary ranges are available via the provided link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6690_9_26". That is not inventing. However we must avoid filler like "commensurate with experience". This is specific: they provide a link. So we can include Pay section. But also note they say "KPMG offers a comprehensive compensation and benefits package." That's generic. We already have Benefits. Thus sections: About the role (intro), Responsibilities, Qualifications, Benefits, Pay. We must not include Schedule. Now we need to extract the substantive 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 should not repeat the job title as heading, but we can keep it in the paragraph. That's fine. Now Responsibilities: list after "Responsibilities:" includes multiple sentences each starting with a verb. We need to turn each into

• . Let's capture them: - 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: after "Qualifications:" includes: - 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: 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 should keep that as Benefits section. Could also include the link to Benefits & How We Work but not needed. Now Pay: after "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..." Actually benefits repeated. Then later: "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 KPMG offers a comprehensive compensation and benefits package." Thus we can create Pay section with a

  that says: "Salary ranges are available via the provided link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6690_9_26". Also note that salary is determined based on skills, experience, etc. Could include that sentence. But we must not invent. The posting says: "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 substantive. So we can include that as well. Thus Pay section:

  Salary is determined based on applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications, and market considerations. Salary ranges are available via the provided link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6690_9_26

  Now we must ensure we don't include boilerplate like EEO, equal opportunity, visa sponsorship? We kept visa sponsorship as part of Qualifications. That's okay. We must remove lines like "KPMG is an equal opportunity employer..." etc. Also remove "No