Senior Account Executive, Marketing Engineer

We need to output HTML fragment with sections: About the role? The posting includes description about company and role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have: - About the role: we have description of company and role: "Golin Ketchum is looking for a Senior Account Executive, Marketing Engineer..." plus description of what they do. Could be "About the role" includes overview. - Responsibilities: The "What You'll Do" section with subparts: STRATEGY & INSIGHT, TECHNICAL SEO & WEBSITE OPTIMIZATION, BUILDING & AUTOMATION, CROSS-FUNCTIONAL COLLABORATION. Those are responsibilities. - Requirements: The "What You Have" section lists qualifications: experience, skills, etc. Could be Requirements. - Qualifications: maybe same as Requirements? But we can separate: Requirements (experience) and Qualifications (education?). However posting says "Any combination of education and experience providing the required skills and knowledge for successful performance would qualify. Typical qualifications would be equivalent to:" then list. So we could treat that as Qualifications. - Skills: maybe list specific technical skills: hands-on technical SEO skills, HTML/CSS/JS, scripting language, APIs, LLMs, analytical skills, writing, curiosity, CMS experience plus, AI visibility platforms plus, agency experience plus. Could be separate Skills section. - Benefits: Not mentioned besides maybe culture? No explicit benefits. So we should not create Benefits section. - Pay: "$70,000 - $85,000" present. So include Pay section. - Schedule: "Omnicom’s policy requires employees to work in the office for a minimum of three days a week..." So schedule info present. Include Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, privacy notice link, etc. Also remove duplicated lines like "$70,000 - $85,000" appears twice; we keep once. We must preserve all substantive information. So we need to include all details from responsibilities, requirements, qualifications, skills, pay, schedule, about the role. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what goes into lists vs prose. Responsibilities: we have bullet-like items under each subheading. Could make a list of responsibilities, maybe grouping. We could create a

  with each responsibility as
  • . But we also have subcategories; we could keep them as prose within
  • maybe. Simplify: For Responsibilities, create a
    with each major bullet: Strategy & Insight, Technical SEO & Website Optimization, Building & Automation, Cross-functional Collaboration. Inside each
    • we can have

      describing details? But rule: Use

      • for any list of duties/requirements/benefits, and

        for prose. So if we have a list, each

      • can contain prose? Probably okay. But we could also just put each duty as a
      • with the description inside. Similarly for Requirements/Qualifications/Skills: we can make lists. We need to avoid filler like "commensurate with experience". Not present. Let's extract content. About the role: We'll write a paragraph summarizing: Golin Ketchum is looking for a Senior Account Executive, Marketing Engineer to join Generative Engine Operations team! Golin Ketchum is the most awarded PR agency of the decade... etc. We'll include all that description. Responsibilities: list items: - Strategy & Insight: * Benchmark how brands appear across AI platforms such as ChatGPT, Gemini, Perplexity, Claude, and Google AI Overviews, including visibility, sentiment, accuracy, and which sources get cited. * Translate citation and visibility data into clear recommendations that connect content, earned media, and technical fixes to business goals. * Help build client strategies, briefs, and presentations that make technical findings easy for communications and marketing leaders to act on. * Track how AI search platforms and models are changing, and flag what that means for our clients. - Technical SEO & Website Optimization: * Audit client websites for AI and search readiness: crawlability, indexation, site architecture, page speed, rendering, and bot access rules (robots.txt, llms.txt, and similar). * Implement and validate structured data and schema markup so brand facts, products, and experts are machine readable. * Partner with client web, IT, and CMS teams to prioritize and ship fixes, and write clear technical tickets and specs. * Optimize owned content (press rooms, product pages, FAQs, knowledge hubs) so it's easy for AI systems to find, understand, and cite. - Building & Automation: * Build tools, dashboards, and workflows that make GEO work faster and repeatable, using Python, JavaScript, APIs, and low-code platforms. * Design and prototype AI agents and prompt pipelines for tasks like citation tracking, content evaluation, and competitive monitoring. * Connect data from AI visibility platforms, analytics, and search tools into reporting that account teams can use without help. * Document what you build so it can scale across clients through the GEO Center of Excellence. - Cross-functional Collaboration: * Work side by side with integrated strategists, account, creative, earned media, and channel teams so technical work supports campaign goals. * Support new business pitches with audits, demos, and proof-of-concept builds. * Share what you learn through internal trainings, playbooks, and documentation. Requirements: maybe experience: 3-5 years of experience in technical SEO, marketing technology, web development, growth engineering, or a related role, ideally with some exposure to brand or communications strategy. Qualifications: maybe education? Not specified. Could treat the list after "Typical qualifications would be equivalent to:" as Qualifications. Skills: list specific skills: Hands-on technical SEO skills, including site audits, schema markup, crawl analysis, and tools like Screaming Frog, Google Search Console, Semrush, or Ahrefs. Working knowledge of HTML, CSS, and JavaScript, plus comfort with at least one scripting language (Python preferred). Experience working with APIs, data pipelines, or automation tools (such as Zapier, Make, n8n, or similar). Hands-on experience with large language models, including prompt design and building simple AI-powered tools or agents. Strong analytical skills and the ability to explain technical findings in plain language to non-technical audiences. Clear writing and a knack for turning data into a story. Curiosity about how AI is changing search, media, and reputation. Experience with CMS platforms (WordPress, Adobe Experience Manager, Sitecore, or similar) is a plus. Familiarity with AI visibility platforms (such as Profound, Bluefish, or similar) is a plus. Agency or consulting experience is a plus. Pay: $70,000 - $85,000 Schedule: Omnicom’s policy requires employees to work in the office for a minimum of three days a week, unless additional in-office days are directed by their agency or manager. Our objective is to increase this requirement over time, and many of our agencies as well as Omnicom’s corporate group already require five days of in-office attendance. We should not include EEO etc. Now produce HTML fragment. Structure:

        About the role

        ...

        Responsibilities

        • Strategy & Insight: ... (maybe we can keep as prose inside li). But we need to use
          • for list. Could embed

            inside li? Might be okay but not required. Simpler: each responsibility as

          • with the description. We'll break each bullet as separate
          • . But we have subheadings; we could make each subheading as
          • with inner
            . However that may be nested lists; still okay. Simplify: Provide a flat list of all duty sentences. But we risk losing grouping. However instruction: "Use
            • for any list of duties/requirements/benefits". It doesn't forbid nesting. We'll do nested lists for clarity. Thus:

              Responsibilities

              • Strategy & Insight
                • Benchmark how brands appear across AI platforms such as ChatGPT, Gemini, Perplexity, Claude, and Google AI Overviews, including visibility, sentiment, accuracy, and which sources get cited.
                • Translate citation and visibility data into clear recommendations that connect content, earned media, and technical fixes to business goals.
                • Help build client strategies, briefs, and presentations that make technical findings easy for communications and marketing leaders to act on.
                • Track how AI search platforms and models are changing, and flag what that means for our clients.
              • Technical SEO & Website Optimization
                • Audit client websites for AI and search readiness: crawlability, indexation, site architecture, page speed, rendering, and bot access rules (robots.txt, llms.txt, and similar).
                • Implement and validate structured data and schema markup so brand facts, products, and experts are machine readable.
                • Partner with client web, IT, and CMS teams to prioritize and ship fixes, and write clear technical tickets and specs.
                • Optimize owned content (press rooms, product pages, FAQs, knowledge hubs) so it's easy for AI systems to find, understand, and cite.
              • Building & Automation
                • Build tools, dashboards, and workflows that make GEO work faster and repeatable, using Python, JavaScript, APIs, and low-code platforms.
                • Design and prototype AI agents and prompt pipelines for tasks like citation tracking, content evaluation, and competitive monitoring.
                • Connect data from AI visibility platforms, analytics, and search tools into reporting that account teams can use without help.
                • Document what you build so it can scale across clients through the GEO Center of Excellence.
              • Cross-functional Collaboration
                • Work side by side with integrated strategists, account, creative, earned media, and channel teams so technical work supports campaign goals.
                • Support new business pitches with audits, demos, and proof-of-concept builds.
                • Share what you learn through internal trainings, playbooks, and documentation.
              Now Requirements: maybe experience.

              Requirements

              • 3-5 years of experience in technical SEO, marketing technology, web development, growth engineering, or a related role, ideally with some exposure to brand or communications strategy.
              Qualifications: maybe education? Not given. Could skip Qualifications if no specific content beyond the typical qualifications list which we already used for Requirements? Actually the "Typical qualifications would be equivalent to:" list includes experience and skills. We could treat that as Qualifications. But we already used experience for Requirements. Could combine? Better to have Requirements = experience, Qualifications = education/equivalent (maybe none). Since we have no explicit education, we could omit Qualifications section. Skills: list.

              Skills

              • Hands-on technical SEO skills, including site audits, schema markup, crawl analysis, and tools like Screaming Frog, Google Search Console, Semrush, or Ahrefs.
              • Working knowledge of HTML, CSS, and JavaScript, plus comfort with at least one scripting language (Python preferred).
              • Experience working with APIs, data pipelines, or automation tools (such as Zapier, Make, n