Director- Digital Insights & Optimization

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes a job summary, responsibilities, qualifications, preferred qualifications, maybe benefits? There's a pay range mentioned: "Pay is competitive... The starting pay rate/range at time of hire for this position in the posted location is $141,372.00 - $201,960.00 / year." So we need a Pay section with that info. Also schedule? Not mentioned. Benefits? Not mentioned. So we include sections: About the role (maybe from the introductory paragraph?), Responsibilities, Qualifications (including required and preferred?), Pay. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to preserve all substantive info, remove boilerplate (EEO, legal, etc). Also remove duplicated lines, navigation, cookie, application instructions. The posting includes a lot of fluff at start: "Are you looking to Optimize your life? Start your exciting path to a rewarding career today! We are Optimum..." That's marketing fluff but it's substantive? It's about company culture. We can include as part of About the role? Probably we can include a short paragraph summarizing company description. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that introductory marketing text? It's not boilerplate; it's describing the company and role. We'll include it in About the role section. We need to avoid repeating job title as heading. So we will not have a heading for "Director, Digital Insights & Optimization". We'll just have sections. We need to use

• for any list of duties/requirements/benefits. So responsibilities list: each bullet is a responsibility. We'll convert each responsibility paragraph into list items. Qualifications: list of required qualifications bullet points. Preferred qualifications also list. Pay: just a paragraph with the pay range. We must not include sections with filler like "commensurate with experience". Not present. We need to remove EEO etc. Also remove "All job descriptions and required skills..." etc. Also remove "We appreciate your interest..." etc. Also remove "Applicants must be authorized..." etc. Also remove "Please note that at this time, we do not provide visa sponsorship..." etc. Also remove "Pay is competitive..."? Actually we need to keep pay range but the sentence "Pay is competitive and based on a number of job-related factors..." is generic; we can keep the pay range but maybe we can keep the sentence that includes the range. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The sentence about pay being competitive is somewhat generic but still part of the posting. However we might consider it boilerplate? It's not EEO/legal. It's about pay. We'll keep it but we can condense? The instruction says do not summarize away detail; but we can keep the sentence as is. However we need to output only HTML fragment; we can include a

  with that sentence. We also need to remove duplicated lines. There's no duplication obvious. Let's extract content. Introductory fluff: "Are you looking to Optimize your life? Start your exciting path to a rewarding career today! We are Optimum, a leader in the fast-paced world of connectivity, and we're seeking driven and enthusiastic professionals to join our team, empower lives, fuel businesses, and drive innovation. Connectivity is now longer a luxury, but a necessity. A career at Optimum means you'll be enabling progress and enhancing lives by providing reliable, high-speed connectivity solutions that keep the world connected. Our successes, now and in the future, are powered by our amazing product, a commitment to our people and culture, and the connections we make in our communities. If you are resourceful, collaborative, and passionate about delivering consistent excellence, Optimum is for you!" Then "Job Summary" heading (but we should not repeat job title as heading; we can treat Job Summary as part of About the role). The Job Summary paragraph: "The Director, Digital Insights & Optimization is responsible for leading a team that will drive digital growth through data-driven insights, experimentation, and conversion rate optimization (CRO) across the Optimum digital ecosystem. This leader owns website analytics, customer journey performance, testing strategy, and optimization efforts across acquisition and existing customer experiences. The role serves as the central point of accountability for understanding website performance, identifying growth opportunities, quantifying business impact, and translating insights into actionable recommendations. Success requires deep expertise in digital analytics, experimentation platforms, conversion rate optimization, forecasting, and cross-functional collaboration across Product, Technology, Marketing, Merchandising, Data and Analytics and base management teams. This position reports to the Vice President of Digital Commerce and acts as a strategic partner to business, product, and technology leaders, ensuring decisions are informed by data and measurable business outcomes." We'll include that as About the role paragraph(s). Could be multiple paragraphs; we can combine into one

  . Responsibilities: list under heading "Responsibilities". The text includes two main sections: "Conversion Optimization & Experimentation", "Analytics & Insights Leadership", "Product Strategy & Feature Scoping", "Cross-Functional Leadership". Each has multiple sentences. We'll turn each sentence into a list item? The instruction: Use

  • for any list of duties/requirements/benefits. So we need to make a list. We can break each bullet as a separate
  • . We'll need to parse the responsibilities text. Let's extract responsibilities: "Conversion Optimization & Experimentation Own the A/B testing and experimentation roadmap across acquisition funnels, landing pages, checkout flows, and self-service journeys — from conversion rate optimization frameworks and prioritization through execution and results. Drive measurable improvement in conversion, revenue, and engagement metrics based on customer behavior and expected ROI. Set testing and measurement best practices across the Digital Commerce org." "Analytics & Insights Leadership Serve as the organization's expert on digital analytics, customer behavior, and conversion funnel performance. Develop proactive insights that identify opportunities, risks, and emerging trends across digital properties. Own Adobe Analytics strategy and governance, including dashboards that give stakeholders real-time visibility into acquisition, conversion, retention, and feature performance. Turn complex, multi-source data – including customer journey analytics – into clear, executive-ready insights and recommendations Build measurement frameworks and automated alerting for new launches and website changes, so tracking issues and performance drops get caught early. Establish standards for attribution, tracking, and reporting consistency across teams and Promote adoption of a data-driven culture across Digital Commerce and partner organizations." "Product Strategy & Feature Scoping Partner closely with Product and Technology teams to define requirements and measurement plans for new initiatives. Provide sizing, segmentation, and performance projections to inform prioritization decisions. Build forecasts, business cases, and impact projections that inform roadmap prioritization and technology investment decisions. Make sure analytics requirements are built into feature design during implementation" "Cross-Functional Leadership Act as a trusted advisor to Digital Commerce leadership, translating data into strategic recommendations. Partner across Media, Merchandising, Product, Go-to-Market, Technology, and CX to align optimization work with commercial priorities." We'll create a
    with each of these sentences as
    • . Ensure we keep the content exactly. Qualifications: list under "Qualifications". The text includes bullet-like sentences each starting with a capital letter. We'll extract each line. Qualifications list: "8+ years of experience in Digital Analytics, Conversion Rate Optimization (CRO), Digital Product Analytics, eCommerce, or related disciplines. Proven experience optimizing acquisition funnels, landing pages, checkout experiences, and customer self-service journeys. Deep expertise with Adobe Analytics and digital reporting platforms. Strong experience with A/B testing, multivariate testing, experimentation methodologies, and attribution frameworks. Demonstrated success building business cases, forecasts, and ROI models to support prioritization decisions. Experience partnering closely with Product and Technology teams in an agile development environment. Advanced analytical capabilities with the ability to synthesize large, complex datasets into actionable insights. Strong understanding of customer segmentation, digital marketing performance, and eCommerce KPIs. Exceptional executive communication and stakeholder management skills. Ability to influence cross-functional teams and drive outcomes without direct authority. Experience leading teams and managing multiple concurrent priorities in a fast-paced environment." Preferred Qualifications: we could include under Qualifications as a separate subsection? The instruction says use headings like Qualifications, Skills, etc. We could have a separate "Preferred Qualifications" heading but not in the list of example headings; but we can still use

      for any section heading. The examples include Qualifications, Skills, etc. We could treat "Preferred Qualifications" as part of Qualifications section, maybe as a sub-list. But we need to decide: The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the pattern. It says "include a section ONLY when the posting has real, specific content for it". So we could have a section "Preferred Qualifications" as a heading if we want. However the examples list didn't include Preferred Qualifications but it's similar to Qualifications. Safer to include under Qualifications heading with two sub-lists: Required and Preferred. But we need to use

      • for any list. We could have a

        introducing then two

        lists. That's fine. Pay: we have a paragraph: "Pay is competitive and based on a number of job-related factors, including skills and experience. The starting pay rate/range at time of hire for this position in the posted location is $141,372.00 - $201,960.00 / year. The rate/range provided herein is the anticipated pay at the time of hire, and does not reflect future job opportunity." We'll keep that as a

        under Pay section. We must remove boilerplate: EEO, legal, fraud FAQ, etc. Also remove "All job descriptions and required skills..." etc. Also remove "We appreciate your interest..." etc. Also remove "Applicants must be authorized..." etc. Also remove "Please note that at this time, we do not provide visa sponsorship..." etc. Now construct HTML. We'll start with

        About the role

        then

        containing the intro fluff and job summary? Might be too long; better to split into two

        paragraphs: one for the marketing fluff, one for job summary. Both are substantive. Then

        Responsibilities

        then
        with each responsibility as
        • . Then

          Qualifications

          then maybe

          for required qualifications heading? Could just have

          for required, then another

          Preferred Qualifications

          then
          . But we are only allowed to use

          for section headings; using

          might be okay but not specified. Safer to keep within

          sections only. We could have two

          lists under Qualifications, with a

          separating them: "Required Qualifications:" and "Preferred Qualifications:" as

          (not heading). That's acceptable. Thus:

          Qualifications

          Required Qualifications:

          ...

          Preferred Qualifications:

          ...
          Then

          Pay

          then

          with pay sentences. Make sure not to include any extra whitespace? It's fine. Now let's craft the HTML. We need to ensure we escape any special characters? Not needed. Let's write. Check for any leftover boilerplate: The phrase "At Optimum, every action and interaction we take part in, is driven by our three Guiding Principles: Do What’s Right, Drive One Optimum, and Make It Happen." That's marketing fluff but still part of posting; we could include it in About the