AEO and GEO Marketing Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: Who we are (About Stripe), About The Team, What you’ll do (Responsibilities), Who you are (Minimum Requirements, Preferred Qualifications), Hybrid work at Stripe (Schedule?), Pay and benefits (Pay, Benefits). Also maybe "About the role" not present. We'll follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We'll map: - About the role? Not explicit heading but we have "Who we are About Stripe" and "About The Team". Could combine as "About the role"? But we have "About Stripe" and "About The Team". Probably better to have sections: About Stripe, About the Team, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule (Hybrid work). However "Requirements" and "Qualifications" both exist: Minimum Requirements and Preferred Qualifications. We can have

Requirements

for minimum, and

Qualifications

for preferred? Or combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (minimum) and Qualifications (preferred). Also Skills maybe not present; we can omit. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. At end there is "Please find our California applicant personal information notice here. The application window will remain open for 100 days..." That's boilerplate/application instructions; remove. We must preserve all substantive information. So we need to include all content from the posting except removed boilerplate. Let's extract substantive paragraphs: - Who we are About Stripe: paragraph about Stripe mission etc. - About The Team: paragraph about Growth Marketing team. - What you’ll do: paragraph about role scope and bullet list of responsibilities (Lead the growth..., Optimize..., Spearhead..., Deliver..., Partner...). Those are bullet points. - Who you are: paragraph about minimum/preferred qualifications. - Minimum Requirements: list of bullet points (5+ years..., Proven technical..., Experience analyzing..., Experience applying..., Proven ability..., Experience leading...). - Preferred Qualifications: list of bullet points (Experience or familiarity with NLP..., Experience managing..., Experience working within..., Experience writing SQL..., Bachelor's degree or 4 years...). - Hybrid work at Stripe: paragraphs about remote/in-office expectations. - Pay and benefits: paragraph about salary range, note about sales roles, additional benefits list. We need to format as HTML with

headings and

• for lists,

  for prose. We must not include sections with filler like "commensurate with experience". Not present. We need to decide which headings to use: - About Stripe (maybe "About the role"? but we have "About Stripe" and "About The Team". Could use "About the company" but not in list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those specific headings when applicable. So we should map content to those headings. Thus: - About the role: could combine Who we are About Stripe and About The Team? But "About the role" is more about the role itself, not company. However we have no explicit "About the role" section. Might be okay to omit About the role and instead use About Stripe and About the Team as separate sections? But instruction says use those headings for section headings (e.g...). It doesn't say we cannot use other headings, but suggests those are typical. Safer to stick to those headings where we have content. We have content for: - Responsibilities (What you’ll do) - Requirements (Minimum Requirements) - Qualifications (Preferred Qualifications) - Benefits (Additional benefits) - Pay (salary range) - Schedule (Hybrid work at Stripe) We might also have "About the role" maybe we can put the introductory paragraphs (Who we are About Stripe, About The Team) under "About the role". That seems plausible: "About the role" could include company description and team description. We'll do that. Thus:

  About the role

  Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career.

  About The Team Growth Marketing is a team of performance-driven marketers and channel specialists. We partner closely with growth, creative, analytics, and regional marketing to drive revenue through self-serve and sales motions. We work globally, across all Stripe offerings and with all company segments - from startups to the largest enterprises. In this role, you’d be joining a global, cross-functional team dedicated to testing and scaling cutting-edge acquisition channelsOur team helps Stripe increase the GDP of the internet by ensuring our web presence is perfectly optimized for the next generation of artificial intelligence and search technologies

  Note: there is a missing space between "channelsOur". We'll keep as is. Then Responsibilities:

  Responsibilities

  • Lead the growth and user acquisition strategy for the Answer Engine Optimization channel
  • Optimize Stripe.com so artificial intelligence agents can efficiently access and take action on behalf of users
  • Spearhead the development and integration of artificial intelligence capabilities to improve the efficiency of search and answer engine channels
  • Deliver regular reports and updates on channel performance to track progress and identify new opportunities
  • Partner with content, engineering, and data analytics teams to build a comprehensive testing roadmap
  Then Requirements (minimum):

  Requirements

  • 5+ years of experience creating and executing search engine optimization strategies, with direct experience with answer engine optimization and generative engine optimization
  • Proven technical experience making websites SEO and AEO-friendly
  • Experience analyzing data and in dashboards and reporting software such as Tableau, Looker, Adobe Analytics, or Google Analytics to drive growth decisions
  • Experience applying user intent analysis to prioritize actions that deliver measurable outcomes
  • Proven ability to take initiative, independently problem-solve, and drive tasks to completion
  • Experience leading project roadmaps across cross-functional stakeholders, including engineering and content teams
  Then Qualifications (preferred):

  Qualifications

  • Experience or familiarity with Natural Language Processing (NLP), vector search, and Retrieval-Augmented Generation (RAG)
  • Experience managing search optimization in-house for business-to-business (B2B) software-as-a-service (SaaS) companies
  • Experience working within the fintech, payments, billing, accounting, or startup industries
  • Experience writing SQL queries to extract and gather data independently
  • Bachelor's degree or 4 years of additional relevant professional experience
  Then Pay:

  Pay

  The annual US base salary range for this role is $143,400 - $215,200. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process.

  Then Benefits:

  Benefits

  • equity
  • company bonus or sales commissions/bonuses
  • 401(k) plan
  • medical, dental, and vision benefits
  • wellness stipends
  • . We'll do that. Then Schedule (Hybrid work):

    Schedule

    This role is available either in an office or a remote location (35+ miles or 56+ km from a Stripe office). In-office expectations Office-assigned Stripes spend at least 50% of the time in a given month in their local office or with users. This hits a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility about how to do this in a way that makes sense for individuals and their teams. Working remotely at Stripe A remote location is defined as being 35 miles (56 kilometers) or more from one of our offices. While you would be welcome to come into the office for team/business meetings, on-sites, meet-ups, and events, our expectation is you would regularly work from home rather than a Stripe office. Stripe does not cover the cost of relocating to a remote location. We encourage you to apply for roles that match the location where you currently live or plan to live.

    We should ensure no duplicate lines. Also remove any boilerplate like "We look forward to hearing from you. At Stripe, we're looking for people with passion, grit, and integrity..." That's after Pay and benefits; that is motivational boilerplate; should we remove? It's not specifically listed as boilerplate but seems like generic encouragement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The motivational paragraph may be considered boilerplate? Not sure. It's not EEO or legal. It's more like closing encouragement. Might be considered part of posting but could be removed as it's not substantive? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That paragraph is substantive? It's generic fluff but still part of posting. However they said remove duplicated lines; this is not duplicated. I'd keep it? But they also said "Prefer a few substantive sections over many thin ones." Might be okay to keep as a paragraph under Benefits or separate? There's no heading for it. Could add a

    after Benefits before closing. But we have no heading for it. Could incorporate into Benefits section as extra

    . However they said use

    for prose. So we could add a

    after Benefits list: "We look forward to hearing from you. At Stripe, we're looking for people with passion, grit, and integrity. You're encouraged to apply even if your experience doesn't precisely match the job description. Your skills and passion will stand out—and set you apart—especially if your career has taken some extraordinary twists and turns. At Stripe, we welcome diverse perspectives and people who think rigorously and aren't afraid to challenge assumptions. Join us." That's a lot of prose. Might be considered substantive? It's encouraging but not required. I'd keep it as a

    after Benefits. But we must not include application instructions like "Apply now". There's "Join us. Apply now Please find our California applicant personal information notice here. The application window will remain open for 100 days after the Job Post is published. However, this opportunity will remain open based on the needs of the business, which