Associate Director, AI Application Engineer
KPMG US · Fort Worth, TX · 1 mo ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading only if there is real specific content. We must not repeat job title as heading. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove salary range details? Pay section only if posting actually states them. The posting includes salary range info: "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." Also a link to salary ranges. That is specific content about pay. So we can include a Pay section with that info (maybe summarizing but must preserve all substantive info, not invent or summarize away detail). We need to preserve all substantive info; we can include the text as is (maybe trimmed). We should not create Schedule section unless posting actually states schedule. It mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also mentions holiday calendar and two breaks each year. That's schedule/benefits info. So we can include a Schedule section with that info. Benefits section: they talk about comprehensive benefits package, medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, etc. So we include Benefits.
We need sections: About the role (intro paragraph about KPMG and the role). Responsibilities (list). Qualifications (maybe combine Requirements and Qualifications? The posting has "Qualifications:" section with bullet-like sentences. Also there is "Requirements:" not explicitly but we can treat Qualifications as requirements. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. There's no separate "Skills" heading but we can extract skills from qualifications. Could create a Skills section summarizing technical skills. But we must not create a section if posting has no real specific content for it. The posting does mention many skills: .NET Core, C#, Python, Azure, Google Cloud, Kubernetes, etc. So we can create a Skills section with those. However we must not invent or summarize away detail; we can list them as bullet points.
We need to avoid duplicating content. We'll parse the posting.
Let's extract sections:
Intro: "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."
That's About the role.
Responsibilities: bullet list after "Responsibilities:" (the long paragraph with colon-separated items). We need to split into list items. The text after "Responsibilities:" is a long sentence with items separated by line breaks? Actually it's a paragraph with each responsibility separated by line breaks? In the source it's lines separated by line breaks but not bullet. We'll treat each sentence starting with a capital verb as a separate item.
List:
- 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.
Qualifications: after "Qualifications:" we have:
- 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)
We could also separate "Skills" from qualifications: many technical skills listed. But we can keep Qualifications as is, and maybe Skills section could extract the technical skills: .NET Core, C#, Python, Azure, Google Cloud, Kubernetes, AKS, API Management, Terraform, CI/CD, GitHub Actions, DevOps/MLOps, etc. However that would duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Qualifications and Skills into one section? But they ask to use headings for Skills if there is content. We could decide to not create a Skills section because the qualifications already cover skills; but we could still create a Skills section if we want to highlight them. However to avoid thin sections, maybe we omit Skills and keep Qualifications.
Benefits: after "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." and following sentences about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, Personal Time Off, holiday calendar, two breaks each year. Also link to Benefits & How We Work. So we can include Benefits section with that info.
Pay: after "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges..." and link. So we include Pay section with that text.
Schedule: The posting mentions "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. Could be placed under Benefits or Schedule. Since they ask for Schedule heading if content exists, we can create Schedule section with that info.
We must not include boilerplate like EEO, equal opportunity, visa sponsorship details? The visa sponsorship is part of Qualifications (must be authorized to work in US). That's substantive. We'll keep it.
We must remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions (like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc). Also remove links to benefits page? We can keep mention but not the URL? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the mention of link but maybe we can keep the URL as it's substantive. However the link is to Benefits & How We Work; it's not essential but it's substantive. We'll keep it.
Similarly for pay transparency link we keep.
We must not include the repeated line "KPMG offers a comprehensive compensation and benefits package." (that's duplicate of benefits). We'll keep only one.
We must not include the repeated EEO paragraph.
We must not include the Los Angeles County applicants section? That's legal/EEO/scram? It's about Fair Chance Act. That's likely boilerplate legal. Should be removed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that section.
Also remove "KPMG is an equal opportunity employer." etc.
Also remove "The attached link contains further information regarding KPMG's compliance..." etc.
Also remove "No phone calls or agencies please." etc.
Also remove "KPMG recruits on a rolling basis." etc.
Also remove "Los Angeles County applicants: Material job duties for this position are listed above." etc.
Now construct HTML.
We'll have:
for each heading only if there is real specific content. We must not repeat job title as heading. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove salary range details? Pay section only if posting actually states them. The posting includes salary range info: "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." Also a link to salary ranges. That is specific content about pay. So we can include a Pay section with that info (maybe summarizing but must preserve all substantive info, not invent or summarize away detail). We need to preserve all substantive info; we can include the text as is (maybe trimmed). We should not create Schedule section unless posting actually states schedule. It mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also mentions holiday calendar and two breaks each year. That's schedule/benefits info. So we can include a Schedule section with that info. Benefits section: they talk about comprehensive benefits package, medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, etc. So we include Benefits.
We need sections: About the role (intro paragraph about KPMG and the role). Responsibilities (list). Qualifications (maybe combine Requirements and Qualifications? The posting has "Qualifications:" section with bullet-like sentences. Also there is "Requirements:" not explicitly but we can treat Qualifications as requirements. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. There's no separate "Skills" heading but we can extract skills from qualifications. Could create a Skills section summarizing technical skills. But we must not create a section if posting has no real specific content for it. The posting does mention many skills: .NET Core, C#, Python, Azure, Google Cloud, Kubernetes, etc. So we can create a Skills section with those. However we must not invent or summarize away detail; we can list them as bullet points.
We need to avoid duplicating content. We'll parse the posting.
Let's extract sections:
Intro: "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."
That's About the role.
Responsibilities: bullet list after "Responsibilities:" (the long paragraph with colon-separated items). We need to split into list items. The text after "Responsibilities:" is a long sentence with items separated by line breaks? Actually it's a paragraph with each responsibility separated by line breaks? In the source it's lines separated by line breaks but not bullet. We'll treat each sentence starting with a capital verb as a separate item.
List:
- 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.
Qualifications: after "Qualifications:" we have:
- 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)
We could also separate "Skills" from qualifications: many technical skills listed. But we can keep Qualifications as is, and maybe Skills section could extract the technical skills: .NET Core, C#, Python, Azure, Google Cloud, Kubernetes, AKS, API Management, Terraform, CI/CD, GitHub Actions, DevOps/MLOps, etc. However that would duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Qualifications and Skills into one section? But they ask to use headings for Skills if there is content. We could decide to not create a Skills section because the qualifications already cover skills; but we could still create a Skills section if we want to highlight them. However to avoid thin sections, maybe we omit Skills and keep Qualifications.
Benefits: after "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." and following sentences about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, Personal Time Off, holiday calendar, two breaks each year. Also link to Benefits & How We Work. So we can include Benefits section with that info.
Pay: after "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges..." and link. So we include Pay section with that text.
Schedule: The posting mentions "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. Could be placed under Benefits or Schedule. Since they ask for Schedule heading if content exists, we can create Schedule section with that info.
We must not include boilerplate like EEO, equal opportunity, visa sponsorship details? The visa sponsorship is part of Qualifications (must be authorized to work in US). That's substantive. We'll keep it.
We must remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions (like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc). Also remove links to benefits page? We can keep mention but not the URL? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the mention of link but maybe we can keep the URL as it's substantive. However the link is to Benefits & How We Work; it's not essential but it's substantive. We'll keep it.
Similarly for pay transparency link we keep.
We must not include the repeated line "KPMG offers a comprehensive compensation and benefits package." (that's duplicate of benefits). We'll keep only one.
We must not include the repeated EEO paragraph.
We must not include the Los Angeles County applicants section? That's legal/EEO/scram? It's about Fair Chance Act. That's likely boilerplate legal. Should be removed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that section.
Also remove "KPMG is an equal opportunity employer." etc.
Also remove "The attached link contains further information regarding KPMG's compliance..." etc.
Also remove "No phone calls or agencies please." etc.
Also remove "KPMG recruits on a rolling basis." etc.
Also remove "Los Angeles County applicants: Material job duties for this position are listed above." etc.
Now construct HTML.
We'll have:
About the role
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.
Responsibilities
- 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