Jobs · Information Technology · New York

Associate Director, AI Enablement Product Owner

KPMG US · Rochester, NY · 1 mo ago
HybridInformation TechnologyFull-time
We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Intro paragraph about KPMG, culture, etc. Could be "About the role" or maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - "Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services..." This is about the company, maybe "About the role"? But "About the role" could include description of role and company context. We'll include a paragraph under

    About the role

    . - Then: "KPMG is currently seeking an Associate Director, AI Enablement Product Owner to join our Digital Nexus technology team." That's the role title, but we shouldn't repeat job title as heading. We can include it in the About the role paragraph. - Then "Responsibilities:" followed by a list of bullet-like sentences (each line starts with a verb). We need to put them under

    Responsibilities

    with
    • each. - Then "Qualifications:" followed by bullet points (some sentences). Under

      Qualifications

      with
      • . - There's also mention of "Some travel may be required", "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship..." That's also qualification/requirement. Could be part of Qualifications. - Then there's a paragraph about 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 such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations." This is about Pay but not giving actual numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does not state actual salary numbers or ranges; it just says they comply with regulations and provide a link. This is not specific salary info. Should we include a Pay section? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that they comply with displaying salary ranges and provide a link, but not actual numbers. Is that considered "states them"? It mentions salary ranges but not giving them. I'd interpret that as not providing actual salary info, so we should NOT create a Pay section because we would have no specific content (just a statement about compliance). The instruction 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 didn't give actual numbers, we should omit Pay section. - Benefits: There's a paragraph: "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=6816_9_26 KPMG offers a comprehensive compensation and benefits package." This is benefits info. It gives specific benefits: medical/dental plans, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. So we can create a Benefits section with
        • items. - Schedule: Not mentioned explicitly. There's mention of "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." That's about PTO, not schedule. No explicit schedule like "full-time", "part-time", "flexible". So we should not create Schedule section. - Skills: Not explicitly listed as a separate section, but qualifications include skills like "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", "Strong trouble-shooting and organizational skills". Could be placed under Qualifications or Skills. The instruction allows Skills heading if there is real specific content. We could create a Skills section pulling out skill-related bullet points. However we need to avoid thin sections. Perhaps better to keep Qualifications as a combined section that includes experience, education, skills, etc. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications, Benefits. That's four sections. That seems good. We must not include boilerplate like EEO, equal opportunity, scam warning, application instructions, navigation, cookie, legal. Also remove duplicated lines. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, qualifications, benefits, etc. Let's extract responsibilities bullet points exactly as given: 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 across the AI business stakeholders and ensure alignment and collaboration on AI enablement activities and outcomes - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment We need to keep each as
        • . Qualifications bullet points: - 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) We should keep all. Now Benefits bullet points: From paragraph: "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." Also: "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also: "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." Also: "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 link; we could keep as a sentence but not a bullet? Might be considered boilerplate? It's a reference; but it's substantive info about where to find details. Could keep as a

          maybe. Also: "Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6816_9_26" That's about salary ranges, but we are not making Pay section. However it's a link; but it's about salary ranges. Since we are not making Pay section, we could either omit that link (as it's about pay) or keep it in Benefits? Probably better to omit because it's about pay and we are not including Pay section. The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we omit the link, we are losing info about where to obtain salary ranges. But we are not creating a Pay section; maybe we could include that link in Benefits? It's not a benefit. Could we include a Pay section with just that link? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that they provide a link to obtain salary ranges. That is stating something about pay (

Similar jobs