Assoc. Dir, Agentic Standards & Context Intelligence

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No metadata like Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the job description. Key sections: - About the role: The first paragraph(s) describing the role: "Generative and agentic AI are reshaping...". That's about the role. - Responsibilities: "Primary Responsibilities Include:" then bullet list. - Requirements: "Basic Qualifications" list. - Qualifications: "Preferred Qualifications" list. - Skills: "Required Skills" and "Preferred Skills" maybe combine? The instruction: Use

for Skills. Could have one Skills section containing both required and preferred? Might split? Probably one Skills section with both required and preferred lists. - Benefits: The paragraph about benefits: "We offer a comprehensive package of benefits. Available benefits include medical, dental, vision healthcare and other insurance benefits (for employee and family), retirement benefits, including 401(k), paid holidays, vacation, and compassionate and sick days." - Pay: The salary range: "The salary range for this role is $173,200.00 - $272,600.00". Also mention annual bonus and long-term incentive. So Pay section. - Schedule: Not explicitly given. There's "Travel Requirements: 10%" and "Flexible Work Arrangements: Hybrid". That could be considered schedule? But schedule heading only if posting actually states them. There's no explicit schedule like full-time, part-time, shift. Might not include Schedule. Also there is "Relocation: No relocation", "VISA Sponsorship: No", "Travel Requirements: 10%", "Flexible Work Arrangements: Hybrid". Could be considered under Benefits? Not exactly. Might include a section like "Work Arrangements" but not allowed headings. Only allowed headings list. So we could incorporate travel and flexible work into Benefits? Not ideal. Perhaps we omit Schedule because no explicit schedule. We must not include boilerplate like EEO, accommodation, etc. Remove all that. We must preserve all substantive info: need to include details like responsibilities bullet points, qualifications bullet points, skills lists, benefits, pay, maybe travel and flexible work as part of Benefits? Could add a

under Benefits that includes those details. Also need to include the description about the role (About the role). Should we include the initial paragraphs as About the role? Yes. Let's extract About the role text: Starting from "Generative and agentic AI are reshaping how commercial teams work — from how insights are surfaced, to how content is created and reviewed, to how decisions are made in market. To move at the speed of that opportunity without compromising on trust, compliance, or quality, the Human Health Division is scaling a GenAI & Agentic Center of Excellence: the team that defines the standards, reusable frameworks, and shared context foundations used to build, evaluate, and ship enterprise-grade AI agents across the commercial portfolio. As adoption expands across therapeutic areas, business units, and international markets, two things determine whether agents scale well: an opinionated, well-governed rulebook that every agent team can start from, and a shared context foundation so that agents reason with consistent business meaning rather than re-interpreting raw data differently each time. Standards without context produce compliant but analytically wrong agents; context without standards produces inconsistency at scale. The Associate Director, Agentic Standards & Context Intelligence Lead will lead the Agentic Standards & Context Intelligence pillar within the CoE, owning both halves of that equation. This leader will be accountable for the enterprise standards, playbooks, and specifications that shape how commercial AI agents are designed, deployed, and operated — and for the shared, governed context layer that encodes commercial entities, metric definitions, and domain semantics so agents reason with a common understanding of the business. This individual will partner closely with responsible-AI, engineering, platform, data, business activation, and enterprise governance teams to ensure standards and context are not only published, but activated in the day-to-day work of the teams building AI agents." That's the About the role. Now Responsibilities: list after "Primary Responsibilities Include:" then bullet points: - Standards vision and roadmap: Defining and evolving playbooks, specifications, and technical standards across the full agent lifecycle (design, deploy, monitor, improve), and driving them from research-backed drafts through use-case-validated versions. - Context intelligence strategy: Owning the strategy for the shared, governed context layer — ontology, knowledge graph, semantic definitions, metric registries, and business glossary — so agents reason with consistent commercial meaning (brands, channels, vendors, KPIs) rather than raw table lookups. - Context as infrastructure: Elevating context handling to a first-class, measurable component of the platform, with instrumentation, lifecycle controls, versioning, and health metrics (accuracy, freshness, compliance) that make context quality continuously measurable and improvable at scale. - Standards adoption and enablement: Driving socialization and adoption of agentic standards and context patterns across business, CoE, and platform teams through enablement content, starter kits, reference patterns, and developer-facing integrations. - Enterprise alignment: Aligning CoE standards and context approaches with broader enterprise architecture, data, and governance functions — clarifying CoE vs. enterprise responsibilities and influencing enterprise-level standards. - Cross-pillar partnership: Partnering with responsible-AI, governance, engagement, and platform teams to translate standards and context capabilities into reusable delivery patterns and operational practices. - Measurement and continuous improvement: Establishing metrics for standards adoption, context quality, and business impact, and running feedback loops that translate developer and business input into standards and context revisions. - Team leadership: Leading, coaching, and scaling a team of technical specialists across standards authorship, context engineering, and adoption. Now Basic Qualifications bullet list: - Bachelor's degree in Computer Science, Data Science, Engineering, Information Technology, or a related STEM field - Experience defining and driving adoption of technical standards, playbooks, or frameworks in a large, matrixed organization - Hands-on understanding of the GenAI agent lifecycle (design, deploy, monitor, improve), including retrieval-augmented generation, tool use, orchestration, evaluation, and guardrails - Experience with context engineering concepts applied to AI systems — grounding, retrieval strategy, semantic definitions, or shared context layers - Experience influencing senior stakeholders across engineering, data, product, and enterprise governance functions Preferred Qualifications bullet list: - Experience in a regulated industry (pharmaceutical, healthcare, financial services) with audit and compliance obligations - Experience designing or governing ontology, knowledge graph, semantic layer, business glossary, or metric registry capabilities for analytics or AI consumption - Experience instrumenting context or data quality metrics (accuracy, freshness, compliance, lineage) as measurable platform health signals - Experience with evaluation-driven and specification-driven development practices for AI agents - Experience standing up or scaling an AI center of excellence, platform governance function, or standards program with measurable adoption outcomes - Experience leading and mentoring a technical team spanning standards and data/context disciplines Now Required Skills list (long). We need to capture them. The list includes many items separated by commas. We'll need to turn into

• items. Probably each item is a skill. Let's extract: "Agentic AI Standards, AI Governance, AI Playbook Development, Change Management, Context Engineering, Cross-Functional Collaboration, Generative AI (GenAI), Governance Frameworks, Knowledge Graphs & Ontology, Large Language Models (LLMs), Multi-Agent Systems, People Leadership, Program Management, Responsible AI, Retrieval-Augmented Generation (RAG), Semantic Layer Design, Stakeholder Relationship Management, Standards Adoption, Strategic Communications, Technical Leadership" That's required skills. Preferred Skills list: "Access-Aware Retrieval, Agent Evaluation, Agent Observability, Business Glossary & Metric Registry Design, Context Health Metrics (Accuracy, Freshness, Compliance), Data Governance for AI, Enterprise Architecture Influence, MLOps / LLMOps, Prompt Engineering Libraries, Regulated-Industry AI Experience" Then there is another block: "Required Skills: Business Informatics, Business Informatics, Business Insights, Business Intelligence (BI), Business Metrics, Computer Science, Content Development, Content Management, Content Marketing, Database Design, Data Engineering, Data Modeling, Data Science, Data Visualization, Design for Maintainability, Developer Tools, Engineering Leadership, First Order Logic, Life Cycle Planning, Machine Learning (ML), Progress Monitoring, Software Agent, Software Development, Stakeholder Relationship Management, Standards Compliance {+ 3 more} Preferred Skills: Current Employees apply HERE Current Contingent Workers apply HERE ..." That seems like duplicate or noise. Likely that part is boilerplate or misformatted. We should ignore that as it's likely not substantive? But it includes many skills like Business Informatics etc. However the instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "Required Skills: Business Informatics, ..." appears after the Preferred Skills block? Actually the text shows: "Required Skills Agentic AI Standards, AI Governance, AI Playbook Development, Change Management, Context Engineering, Cross-Functional Collaboration, Generative AI (GenAI), Governance Frameworks, Knowledge Graphs & Ontology, Large Language Models (LLMs), Multi-Agent Systems, People Leadership, Program Management, Responsible AI, Retrieval-Augmented Generation (RAG), Semantic Layer Design, Stakeholder Relationship Management, Standards Adoption, Strategic Communications, Technical Leadership Preferred Skills Access-Aware Retrieval, Agent Evaluation, Agent Observability, Business Glossary & Metric Registry Design, Context Health Metrics (Accuracy, Freshness, Compliance), Data Governance for AI, Enterprise Architecture Influence, MLOps / LLMOps, Prompt Engineering Libraries, Regulated-Industry AI Experience Required Skills: Business Informatics, Business Informatics, Business Insights, Business Intelligence (BI), Business Metrics, Computer Science, Content Development, Content Management, Content Marketing, Database Design, Data Engineering, Data Modeling, Data Science, Data Visualization, Design for Maintainability, Developer Tools, Engineering Leadership, First Order Logic, Life Cycle Planning, Machine Learning (ML), Progress Monitoring, Software Agent, Software Development, Stakeholder Relationship Management, Standards Compliance {+ 3 more} Preferred Skills: Current Employees apply HERE Current Contingent Workers apply HERE US And Puerto Rico Residents Only: ..." It looks like the posting may have duplicated sections. The first Required Skills and Preferred Skills are likely the correct ones. The later "Required Skills: Business Informatics..." seems like maybe a generic list from the system, not specific to this role. Might be considered boilerplate? However it's still substantive info about skills. But the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This duplicated skills list might be considered duplicated lines? It's similar to the earlier skills but different content. Hard to know. Given the instruction to preserve ALL substantive information, we should include the skills that are explicitly listed under Required Skills and Preferred Skills as they appear first. The later list might be considered generic and possibly not specific to this role; but it's still under "Required Skills:" heading. However the posting may have errors. To be safe, we could include both sets? But that would be duplicative and maybe not intended. I think we should include the first Required Skills and Preferred Skills as they are directly under the heading "Required Skills" and "Preferred Skills". The later "Required Skills:" line might be a mistake; but it's still part of the posting. However it's followed by "Preferred Skills: Current Employees apply HERE..." which is clearly application instruction boilerplate. So we should stop before that. Thus we will include: Required Skills: list as above. Preferred Skills: list as above. Now Benefits: we have paragraph about benefits. Pay: salary range and bonus. Now we need to output HTML fragment with

  headings and

  • for lists,

    for prose. We must not include or . We'll produce something like: