Associate Director, AI Enablement Product Owner
before any headings, as a general description. The instruction says output only HTML fragment, no /. We can include a leading
with that intro. Then sections. Responsibilities: bullet list. Qualifications: bullet list. Skills: maybe combine with qualifications? The posting includes qualifications and also some skill-like statements: "Exceptional written, verbal, presentation, and editorial skills..." etc. Those could go under Skills. Benefits: The posting mentions benefits: comprehensive competitive benefits package, medical/dental, vision, disability, life insurance, 401(k), personal well-being, PTO, holidays, breaks. Also link to benefits page. So we can include Benefits section. Pay: The posting mentions salary ranges: "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. There's a link to salary ranges by city outside of CA. So there is some pay info (reference to ranges). According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that salary ranges are displayed via URL, but not actual numbers. Is that considered stating them? It 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 implies there are ranges displayed somewhere (maybe later in posting). Since we don't have the actual numbers, but we know they exist via link. Could we include Pay section with a note that salary ranges are available via link? The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The posting does not give explicit numbers, but says ranges displayed below or via URL. That's not exactly filler; it's a direction to see ranges. Might be acceptable to include Pay section with a
stating that salary ranges are available via the provided link (and mention that actual offer based on factors). However we must not invent details. We can say: "Salary ranges are available via the link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6816_9_26". That's factual. Schedule: The posting mentions standard work hours, years of service, PTO, holidays, breaks. It says: "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 (work hours, PTO, holidays). So we can include Schedule section with that info. Now we need to decide headings: About the role (maybe we can use "About KPMG" but not in list). The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for the introductory paragraph about KPMG and the role? Could also include a brief about the role itself (the AI Enablement Product Owner). The intro didn't describe role specifics; responsibilities do. So About the role could be a short paragraph summarizing the role: "Associate Director, AI Enablement Product Owner to join our Digital Nexus technology team." That's from the posting. So we can put that. Responsibilities: bullet list. Requirements: maybe we can combine with Qualifications? The posting has "Qualifications:" section. There's no separate "Requirements". Could treat Qualifications as Requirements. But we have both headings allowed. We could put qualifications under Requirements, and skills under Skills. Or we could put qualifications under Qualifications and skills under Skills. The posting includes both qualification items and skill items. Let's parse: Qualifications block: - Minimum eight years of recent experience leading AI product management, platform enablement, or technology adoption initiatives, including experience managing vendor relationships, release cycles, and roadmaps for enterprise AI platforms (for example, Anthropic, OpenAI, or similar) - Bachelor's degree from an accredited college or university is preferred; minimum of a high school diploma or GED is required - Experience evaluating and defining use cases for generative AI/LLM capabilities across platforms preferred, along with working knowledge of AI product lifecycle management, technical release management, and change/enablement methodologies - Exceptional written, verbal, presentation, and editorial skills with keen attention to detail and ability to think creatively, out of the box - Capability to effectively interact with and influence individuals at all levels of responsibility and authority, including vendor partners and technical teams; ability to prioritize, delegate, and foster the development of high-performance teams to lead/support an environment driven by customer service and teamwork - Strong trouble-shooting and organizational skills and capability to work on multiple projects simultaneously; ability to participate in resource planning processes based on defined organizational plans - Some travel may be required - 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 mix of experience, education, skills, etc. Then after that there is a paragraph about salary transparency, benefits, etc. We could treat the qualifications block as Requirements (or Qualifications). Then we could extract skill-specific statements into Skills: maybe the "Exceptional written, verbal..." etc. But they are already in qualifications. To avoid duplication, we could keep Qualifications section for education/experience/authorization, and Skills section for the soft skills. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine qualifications and skills into one section called Qualifications (or Requirements). But we have to follow headings list; we can choose which to include. We could include Responsibilities, Qualifications, Benefits, Pay, Schedule. And maybe About the role. That's 5 sections. We need to ensure we don't create sections with filler. All have content. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statement, "KPMG is an equal opportunity employer..." etc. Also "No phone calls or agencies please." Also "KPMG recruits on a rolling basis..." etc. Also Los Angeles County specifics about criminal history. Also "KPMG LLP and its subsidiaries..." etc. Also "KPMG offers a comprehensive compensation and benefits package." That's benefits but we already have benefits. Also "KPMG is proud to offer a comprehensive, competitive benefits package..." That's benefits. We need to remove EEO, visa sponsorship details? The visa sponsorship is part of qualifications (Applicants must be authorized to work in the U.S...). That's substantive, keep. The EEO statement is boilerplate, remove. The "No phone calls or agencies please" is boilerplate, remove. The "KPMG recruits on a rolling basis..." is boilerplate, remove. The Los Angeles County criminal history details is likely legal boilerplate, remove. The "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's part of pay transparency, keep? It's not boilerplate; it's about pay. We'll keep relevant pay info. Now let's craft HTML. We'll start with a
for intro about KPMG and role? Actually we can put About the role heading with paragraph: "Associate Director, AI Enablement Product Owner to join our Digital Nexus technology team." plus maybe the company description? The company description is not role-specific but could be part of About the role. However the instruction says "Do NOT repeat the job title as a heading". It's okay to have it in paragraph. Let's do:
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 Enablement Product Owner to join our Digital Nexus technology team.
That preserves the intro and role. Now Responsibilities:Responsibilities
- Own the end-to-end product roadmap and release schedule for Anthropic (Claude) and OpenAI platforms, partnering with vendor account teams and internal technical/platform owners to plan, prioritize, and communicate upcoming model, feature, and capability releases across the organization
- Continuously evaluate new AI capabilities and platform updates from Anthropic and OpenAI against other AI platforms and vendors, assessing business fit, risk, and competitive positioning to inform adoption and platform strategy recommendations
- Act as the primary liaison between Anthropic, OpenAI, and other AI vendors, technical/platform owners, and business stakeholders to ensure alignment on roadmap, priorities, and messaging; partner with business stakeholders across functions to identify, define, and prioritize high-value AI use cases
- Design, launch, and manage preview and early access programs for new AI capabilities, coordinating pilot participants and technical/business stakeholders, gathering and synthesizing feedback, and translating results into go/no-go and broader rollout recommendations
- Own end-to-end enablement strategy and execution for AI capabilities, collaborating with the Enterprise enablement team to prepare communications and campaigns, learning and training content, and adoption playbooks that drive awareness, readiness, and sustained usage; define and track adoption and enablement success metrics throughout the product and rollout lifecycle, and identify and resolve barriers to adoption
- Provide leadership and guidance to the digital enablement team, build and maintain strong relationships with senior stakeholders