Senior Director, Generative & Answer Engine Optimization (GEO/AEO)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description about role, responsibilities, requirements, qualifications, preferences, benefits, pay. No schedule mentioned. So we should include About the role (intro), Responsibilities, Requirements (basic requirements), Qualifications (maybe additional preferences?), Skills (maybe preferences?), Benefits, Pay. We must not repeat job title. Must not include metadata like Job ID. Remove boilerplate like EEO, accommodation request, etc. Also remove application instructions. Keep all substantive info. We need to parse the posting. Let's extract sections: Intro: "At Lilly, the work is demanding because patients are waiting. We unite caring with discovery to help make life better for people around the world, knowing that every decision, every detail, and every day matters. Headquartered in Indianapolis, Indiana, our over 50,000 employees around the globe take on complex challenges to discover and deliver life-changing medicines, strengthen how health is understood and managed, and support the communities we serve. This is hard, urgent, selfless work—but it’s work worth doing. If you’re driven by purpose and ready to bring your best to work that truly matters for patients, we invite you to join us." Then description of role: "Build the function that determines how the enterprise is represented across AI-driven search. Generative AI platforms — ChatGPT, Gemini, Claude, Google AI Overviews — are becoming a primary channel through which patients, caregivers, and healthcare professionals find information. Most companies, including most competitors in this space, do not yet have a defined strategy for how their brands are surfaced, cited, or recommended inside these tools. This role builds that capability from the ground up. This is a newly created role inheriting an existing team of GEO practitioners. The mandate is to define the strategy, evolve the operating model, and scale the team and tools for one of the largest and most complex organizations in the industry. This role sets the standard for an emerging discipline, building on an established team rather than starting from zero. This Role Owns Enterprise strategy and execution for AI/LLM visibility across commercial, medical, and communications functions, in the US and international markets The measurement layer — evaluating and selecting the tools and platforms that track AI-surface performance, and building the dashboards that report performance to the business Hiring, budget, and vendor decisions for the function Cross-functional alignment across Search Capabilities, Medical Affairs Strategy, Evidence Intelligence, and Site teams — driving one unified enterprise approach rather than fragmented efforts The team is built, not inherited. This role carries explicit mandate and budget to hire and develop a group of GEO practitioners as the function scales." Then "Core Responsibilities" with bullet points: - Strategy & Enterprise Leadership: Define and lead the enterprise GEO/AI-visibility strategy. Set the operating model and governance for how this work is prioritized and resourced. Translate a broader search vision into a concrete roadmap. Track a fast-moving landscape and resolve implications for the business, in partnership with brand, medical, and communications leadership. - AI Visibility Insights & Measurement: Build and evolve the dashboards and reporting that give teams a real-time view of AI-surface performance. Set technical content standards that improve how content is surfaced and cited. Audit gated content to confirm high-value material is accessible to AI engines. Run pilots and scaled rollouts across international markets. - Cross-Functional Partnership & Vendor Management: Align with peer leads across Commercial, Medical, and International teams on a unified strategy. Partner with Technology and Site teams on structured data, schema markup, and site architecture that support AI crawlability. Own vendor relationships and tool evaluation in the AI-visibility space — platforms such as Semrush, Bluefish AI, Profound, or Athena. Represent this work in cross-functional AI strategy forums. - Team Leadership: Build a team of GEO practitioners. Set goals, provide direction, and establish clear development paths as the field matures. Then "Basic Requirements": Bachelors degree 7–10+ years leading search or digital marketing. Hands-on experience building AI/LLM visibility, GEO, or AEO programs. Extensive tenure specifically in GEO is not expected, given the discipline's recency; direct execution experience is required. Qualified applicants must be authorized to work in the United States on a full-time basis. Lilly will not provide support for or sponsor work authorization or visas for this role, including but not limited to F-1 CPT, F-1 OPT, F-1 STEM OPT, J-1, H-1B, TN, O-1, E-3, H-1B1, or L-1. Then "Additional Preferences": Experience leading and developing people, including running specialists through ambiguity in a fast-changing space Strong analytical skills — experience building and interpreting visibility dashboards and performance data to drive decisions Ability to communicate a new, technical topic clearly to senior leaders and align cross-functional teams without formal authority over them Experience in pharma, healthcare, or another regulated industry. Deep pharmaceutical experience is not required at the outset; onboarding includes direct partnership with Medical, Legal, and Regulatory teams, and the ability to learn a regulated environment quickly is expected. Direct experience with AI-visibility platforms (Semrush, Bluefish AI, Profound, Athena, Otterly) or major AI surfaces (ChatGPT, Gemini, Claude, Google AI Overviews, Open Evidence) Experience implementing structured data, schema markup, or technical SEO at scale Experience scaling a marketing capability across global or international markets A clearly articulated point of view on Agentic Search and how brands should prepare for it Demonstrated ability to operate effectively in ambiguity, as the discipline will continue to evolve Then compensation: "Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is $166,500 - $244,200 Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance). In addition, Lilly offers a comprehensive benefit program to eligible employees, including eligibility to participate in a company-sponsored 401(k); pension; vacation benefits; eligibility for medical, dental, vision and prescription drug benefits; flexible benefits (e.g., healthcare and/or dependent day care flexible spending accounts); life insurance and death benefits; certain time off and leave of absence benefits; and well-being benefits (e.g., employee assistance program, fitness benefits, and employee clubs and activities). Lilly reserves the right to amend, modify, or terminate its compensation and benefit programs in its sole discretion and Lilly’s compensation practices and guidelines will apply regarding the details of any promotion or transfer of Lilly employees." We need sections: About the role (intro + role description?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Qualifications and Skills? The instruction: use headings for those sections if they have real specific content. We have Basic Requirements (requirements). Additional Preferences could be split into Qualifications and Skills. But we need to decide. We could treat "Basic Requirements" as Requirements. "Additional Preferences" could be split into Qualifications (education/experience) and Skills (specific abilities). However the posting doesn't label them as such; we just need to create sections only if there is real specific content. We could create a "Qualifications" section for the additional preferences that are about experience/background, and a "Skills" section for abilities like analytical, communication, etc. But we must not invent filler. We need to ensure content is substantive. Let's parse Additional Preferences list: - Experience leading and developing people, including running specialists through ambiguity in a fast-changing space - Strong analytical skills — experience building and interpreting visibility dashboards and performance data to drive decisions - Ability to communicate a new, technical topic clearly to senior leaders and align cross-functional teams without formal authority over them - Experience in pharma, healthcare, or another regulated industry. Deep pharmaceutical experience is not required at the outset; onboarding includes direct partnership with Medical, Legal, and Regulatory teams, and the ability to learn a regulated environment quickly is expected. - Direct experience with AI-visibility platforms (Semrush, Bluefish AI, Profound, Athena, Otterly) or major AI surfaces (ChatGPT, Gemini, Claude, Google AI Overviews, Open Evidence) - Experience implementing structured data, schema markup, or technical SEO at scale - Experience scaling a marketing capability across global or international markets - A clearly articulated point of view on Agentic Search and how brands should prepare for it - Demonstrated ability to operate effectively in ambiguity, as the discipline will continue to evolve These are a mix of experience and skills. Could split: Qualifications (experience-based) and Skills (ability-based). But we need to avoid creating sections with little content. We could just have one "Additional Preferences" section but the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So likely they expect those specific headings. We should map content to those headings. Thus: - About the role: intro paragraph(s) describing Lilly and the role purpose. - Responsibilities: the Core Responsibilities bullet points. - Requirements: Basic Requirements. - Qualifications: maybe the "Additional Preferences" that are about experience/background (like leading people, pharma experience, experience with platforms, structured data, scaling globally, point of view on Agentic Search). Could be considered qualifications. - Skills: the abilities like analytical skills, communication ability, ability to operate in ambiguity. - Benefits: the benefit program description. - Pay: the anticipated wage and bonus info. - Schedule: not present, so omit. We must not include filler like "commensurate with experience". We have specific pay range. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format them into lists and paragraphs. We must not repeat job title. Not include Job ID etc. We must remove boilerplate: EEO, accommodation request, ERG list, etc. Also remove the line about Lilly reserves right to amend compensation etc? That's part of benefits/compensation; it's substantive? It's about compensation practices; we could keep it as part of Pay/Benefits. It's not boilerplate; it's about compensation policy. Might keep. We must remove duplicated lines. Now craft HTML. Structure:

  About the role

  At Lilly, the work is demanding because patients are waiting. We unite caring with discovery to help make life better for people around the world, knowing that every decision, every detail, and every day matters. Headquartered in Indianapolis, Indiana, our over 50,000 employees around the globe take on complex challenges to discover and deliver life-changing medicines, strengthen how health is understood and managed, and support the communities we serve. This is hard, urgent, selfless work—but it’s work worth doing. If you’re driven by purpose and ready to bring your best to work that truly matters for patients, we invite you to join us.

  Build the function that determines how the enterprise is represented across AI-driven search. Generative AI platforms — ChatGPT, Gemini, Claude, Google AI Overviews — are becoming a primary channel through which patients, caregivers, and healthcare professionals find information. Most companies, including most competitors in this space, do not yet have a defined strategy for how their brands are surfaced, cited, or recommended inside these tools. This role builds that capability from the ground up. This is a newly created role inheriting an existing team of GEO practitioners. The mandate is to define the strategy, evolve the operating model, and scale the team and tools for one of the largest and most complex organizations in the