Vice President, Consumer Products & Growth - CouponFollow

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, maybe Skills? The posting includes "About The Role", "Responsibilities", "Required Qualifications", "Nice To Have", "What We Have To Offer". Also "About CouponFollow" is intro but we should not repeat job title. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to include sections only if there is real specific content. The posting includes: - About CouponFollow (intro) – maybe we can include as a paragraph before sections? Not a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? Probably we should only use those headings. The intro could be a

  without heading. - About The Role: we have a paragraph describing role. That's content for "About the role". So we should have

  About the role

  then a

  with that prose. - Responsibilities: multiple bullet points. We'll make

  Responsibilities

  then
  • each bullet. - Required Qualifications: list of qualifications. Could be under

    Requirements

    or

    Qualifications

    . The instruction mentions both. We'll choose Requirements (or Qualifications). Since they said "Required Qualifications", we can put under

    Requirements

    . Provide
    • each. - Nice To Have: could be under

      Skills

      maybe? Or we could combine with Requirements? The instruction says prefer few substantive sections over many thin ones. Nice To Have is not required but still substantive. Could be a separate section "Skills" or "Preferred Qualifications". Since they gave a list, we can include as

      Skills

      with
      . - What We Have To Offer: benefits. So

      Benefits

      with
      each benefit. - Pay: not specified (they said Competitive salary + bonus + equity but no numbers). That's vague but still mentions competitive salary + bonus + equity. Is that considered specific? It says "Competitive salary + bonus + equity". That's not a number but it's a statement. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (they list). Pay: they mention competitive salary + bonus + equity. That is a statement about pay, though not specific numbers. Should we include Pay section? The instruction says prefer few substantive sections over many thin ones. Could combine Pay into Benefits? But they said Benefits section for benefits. Pay is separate. However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary + bonus + equity". That's a statement about pay. So we could include a Pay section with that sentence. But they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary + bonus + equity" is not filler; it's a statement. So we could include Pay. But we also have Benefits already listing many items. Could we combine Pay and Benefits? The instruction says prefer a few substantive sections over many thin ones. Having both Pay and Benefits may be thin but still substantive. However we could incorporate Pay into Benefits as a bullet? But they said Benefits section for benefits. Pay is separate concept. I'd include both. Schedule: not mentioned (they said fully-remote role, can work in certain states). That's location, not schedule. No schedule info. So we omit Schedule. We must remove EEO boilerplate, security notice, etc. We need to preserve all substantive information: include the intro paragraph about CouponFollow, the About The Role paragraph, responsibilities list, required qualifications list, nice to have list, benefits list, pay statement. We must not repeat job title. The job title is "Vice President, Consumer Products & Growth". Not to be used as heading. We must not include Job ID etc. We must output only HTML fragment, no /, no markdown fences. Let's extract content. Intro: "About CouponFollow At CouponFollow (NextGen), a System1 company (NYSE: SST), we help over 25 million monthly users save money by connecting them with real, verified coupon codes from thousands of leading retailers. As one of the world’s leading organic coupon sites, CouponFollow.com, we're rapidly expanding our product offerings, user experience, and strategic partnerships." We can make that a

      . About The Role: "We are looking for a Vice President, Consumer Products & Growth to take end-to-end ownership of our browser extension and related mobile apps business, as well as new strategic growth products in the deals and savings space. This is a hybrid business owner / growth / product-owner role. You'll set the strategy for how we grow these businesses: marketing, installs, retention, and monetization, own the partner relationships that make that growth possible, and work hand-in-hand with product and engineering to ship the roadmap that gets us there. You will be the single point of accountability for the business's performance and growth trajectory." Make that a

      under

      About the role

      . Responsibilities: list bullet points from the "Responsibilities" section. Let's extract each bullet: - Strategy & Business Ownership - Own the extension and related business plans and operating cadence, with accountability for revenue, forecasting, KPI performance, and resource allocation; identify performance gaps early and lead corrective actions across the organization. - Define the growth strategy for the consumer product portfolio, setting the strategic priorities, growth levers, and market-positioning choices that will drive sustainable scale. - Set strategic product direction and roadmap priorities to enhance the product experience and business metrics. - Source and prioritize new business opportunities, evaluating build-vs-partner tradeoffs and sizing potential impact. - Build and scale a high-performing team to drive the business, establishing clear processes, staffing models, and quality standards to maintain strong user experience as volume grows. - Performance & Analytics - Own performance management of the CouponFollow browser extensions and mobile apps — analyzing, interpreting, and reporting on funnel, acquisition, retention, and cashback performance data. - Establish the reporting cadence and metrics framework the business is run against, surfacing insights and recommendations to leadership. - Growth Partnerships & Distribution - Own the strategy and execution for performance-based CPA/CPI partnerships that drive installs, activation, and monetization. - Manage the creator/UGC growth function against clear performance targets. - Build and grow high-value partner distribution relationships across affiliate networks, merchants, and other distribution partners, with a clear focus on scalable, pay-for-performance models. - Design, test, and optimize CPA (cost per action) and CPI (cost per install) offers, payout structures, and tracking frameworks to maximize efficient growth and LTV. - Work closely with the partnerships team to align affiliate network and merchant relationships with the extension/app business, ensuring clear KPIs, attribution, and payout accountability. - Define and track partner performance metrics (e.g., eCPI, eCPA, ROAS, retention cohorts) and run regular partner reviews to scale winners and cut underperformers. - Compliance & Risk - Ensure compliance with tracking technologies, digital marketing standards, and affiliate network stand-down rules. - Collaborate with product, data, and legal to ensure compliant tracking, fraud prevention, and clean integration of partner-sourced traffic into the extension funnel. - Cross-functional Execution - Manage and develop the paid growth function responsible for day-to-day channel execution - approve budgets, targets, and LTV-based guardrails while holding the team accountable for efficient, scalable growth. - Partner closely with product and engineering to translate strategy into a shipped roadmap. - Act as the connective tissue between partnerships, product, engineering, and leadership to keep the extension business aligned and moving. We need to decide how to format. Could just list each bullet as
      • with the full sentence. The headings like "Strategy & Business Ownership" are subheadings inside responsibilities; we could keep them as part of the bullet text or maybe as . But instruction: Use
        • for any list of duties/requirements/benefits. So we can just put each duty as a
        • . The subheadings can be included as part of the text. Thus we will create a
          with many
          • items, each containing the full sentence. Similarly for Required Qualifications: list: - 8+ years of relevant experience with responsibility for consumer and product activities (e.g. product growth, product management, GM or P&L owner). - Demonstrated success developing and scaling performance-based growth programs, including CPA/CPI partnerships, affiliate channels, or other pay-for-performance distribution models. - Proven track record building, launching, and maintaining high-scale, successful products. - Experience strategically influencing and aligning senior stakeholders and key partners to consistently drive action, results, and change. - Hands-on, "roll up your sleeves" mindset, with the ability to be a driver and change agent in an organization. - Strong business acumen and data analytics proficiency. - Bachelor's degree in business, engineering, marketing, or a related field (or equivalent practical experience). We'll put each as
          • . Nice To Have (Skills): - Experience managing app and/or browser extension products. - Experience in affiliate marketing or digital partnerships. - Experience in the shopping and deals space. We'll put as
          • under

            Skills

            . Benefits (What We Have To Offer): - Competitive salary + bonus + equity - Generous PTO + 11 company holidays - Open sick time - 100% covered Medical, Dental, Vision for employees - 401k with match - Health & Dependent Care Flex Spending Account - Paid professional development - Leadership & growth opportunities - Virtual company and team building events We'll put each as
          • under

            Benefits

            . Pay: The posting says "Competitive salary + bonus + equity" which is already in Benefits list. Actually that's duplicated. The benefits list includes that as first item. So we might not need a separate Pay section; we can just include that as part of Benefits. The instruction says prefer few substantive sections over many thin ones. So we can combine Pay into Benefits. However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated. Pay is also stated but it's same as first benefit. To avoid duplication, we can just have Benefits section that includes that item. No separate Pay. Schedule: not stated. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to ensure we don't include any boilerplate like EEO, Security Notice,