Data Analytics Senior Lead

We need to output HTML fragment with sections only if content present. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract relevant content. Job posting includes: "About Salesforce" description, "The Experience" description, bullet list of responsibilities (What You’ll Be Doing) with items. Then "You’re Our Person If..." with Professional Experience etc. Then "Even Better If..." with additional preferences. Then benefits description: "Unleash Your Potential..." includes benefits mention but not specific list; later there is a paragraph about benefits: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also salary range info: "The typical base salary range for this position is $150,100 - $227,000 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $180,200 - $247,900 annually." So we have Pay section. Schedule not mentioned. So we should not include Schedule heading. We need sections: About the role (maybe combine About Salesforce and The Experience?), Responsibilities (the bullet list), Requirements (maybe "You’re Our Person If..."), Qualifications (maybe "Even Better If..."?), Skills (maybe technical competencies?), Benefits, Pay. But we must follow instruction: Use headings only when posting has real, specific content for it. Avoid filler. So we need to decide which sections to include. We have content for About the role: we can put description about Salesforce and The Experience under About the role. Responsibilities: we have bullet list under "What You’ll Be Doing". Use

• . Requirements: maybe "You’re Our Person If..." includes Professional Experience etc. That's qualifications/requirements. Could be Requirements. Qualifications: maybe "Even Better If..." could be Qualifications or Preferred Qualifications. But we have only one Qualifications heading allowed; we could put "Even Better If..." under Qualifications. Skills: we have technical competencies: proficiency in SQL and Tableau, Snowflake, behavioral analytics concepts. Could be Skills. Benefits: we have benefits list. Pay: we have salary range. Schedule: none -> omit. We must not repeat job title as heading. No Job ID. We must remove boilerplate: accommodations, AI tools note, privacy statement, EEO, etc. Also remove "To get the best candidate experience..." line, "Job Category Data Job Details". Also remove "Apply today..." etc. Also remove "Accommodations" etc. Also remove "Posting Statement" etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." maybe keep? It's EEO/legal boilerplate; should remove. Also remove "At Salesforce, we believe in equitable compensation practices..." maybe part of Pay? It's about compensation practices; but we already have Pay. Might keep as part of Pay? It's not specific salary; it's general statement. Probably remove as boilerplate. We need to preserve all substantive information: responsibilities, requirements, qualifications, skills, benefits, pay. Let's extract specifics. About the role: combine: "Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. The Experience The Messaging Platform Analytics & Operations (MPAO) organization establishes global analytical standards and drives data-informed decision-making across messaging capabilities deployed on Marketing Cloud. We are seeking a Data Analytics Senior Lead to govern the product-driven analytics roadmap for enterprise's marketing email and push messaging platform. Positioned at the nexus of marketing strategy, product management, and technical execution, this role is accountable for translating ambiguous business requirements into prioritized analytics strategies, standardized data architectures, and scalable reporting solutions—ranging from Tableau visualizations to Agentforce AI applications. The Senior Lead acts as the primary connective tissue between business stakeholders and data engineering teams, ensuring end-to-end alignment without direct software pipeline implementation." We can keep that as prose under About the role. Responsibilities: list items: - Strategic Roadmap Governance: Author, sequence, and manage the analytics backlog for Messaging Platform capabilities; evaluate trade-offs based on business value, engineering effort, and dependency risks to secure cross-functional consensus. - Requirements Architecture & Data Taxonomy: Define standardized business dimensions, data schemas, logging protocols, and ingestion cadences; produce developer-ready technical specs that set the architectural standard engineering teams build against. - Audit & Performance Frameworks: Drive ongoing gap analyses across platform capabilities to surface untracked events and schema blind spots; design and deploy standardized KPI frameworks that define how platform health and feature adoption are measured enterprise-wide. - Cross-Functional Program Leadership: Partner with Data Engineering and Data Science leadership to shape pipeline design and system architecture at the platform level, proactively resolving blockers before they reach delivery. - Launch Quality Standards: Set the standard for how platform analytics deployments are validated before launch — defining the UAT framework, business-rule checks, and sign-off criteria that engineering and QA execute against. - Organizational Enablement & Governance: Own the requirements and reporting-spec source of truth for the platform; design enablement programs that raise data literacy and elevate self-serve analytics adoption across marketing and operations. We'll put each as
• . Requirements (You’re Our Person If...): - Professional Experience: 8–12+ years in business intelligence, data analytics, or data product management, with a demonstrated record of defining and delivering enterprise-grade data platform roadmaps. - Roadmap & Strategic Ownership: Proven track record independently owning an analytics or data platform roadmap, including identifying investment white space and building the business case for it. - Technical & Analytical Competency: Proficiency in SQL and Tableau, supported by a strong foundational understanding of Snowflake data warehousing architectures and behavioral analytics concepts (event tracking, funnel analysis, and usage metrics). - Executive Communication: Excellent written and verbal communication skills; proven capability to influence executive leadership (VP+), facilitate cross-departmental collaboration and drive strategic alignment across Marketing, Product, and Engineering. We could treat these as Requirements. Qualifications (Even Better If...): - Salesforce Ecosystem Experience: Direct professional experience with Salesforce products, including Marketing Cloud, Data Cloud, Agentforce, or Slack. - Domain Knowledge: Specialized background in enterprise (B2B) marketing operations, messaging architecture, or digital campaign analytics. - Global Operations: Experience collaborating across complex, matrixed global organizations and geographically distributed teams. Skills: maybe we already covered technical competency under Requirements; but we could separate Skills: proficiency in SQL, Tableau, Snowflake, behavioral analytics concepts. However we already have that under Requirements. To avoid duplication, maybe we put Skills as separate section listing those technical skills. But we must not repeat content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to avoid redundancy. However we need a Skills section only if we have specific content for it. We have technical competencies already listed under Requirements; we could still have Skills section with those same items, but that would be duplication. Might be okay but better to assign them to Skills and move them out of Requirements? But Requirements also includes Professional Experience etc. We could split: Requirements: Professional Experience, Roadmap & Strategic Ownership, Executive Communication. Skills: Technical & Analytical Competency (SQL, Tableau, Snowflake, behavioral analytics). That seems reasonable. Thus: Requirements (

  Requirements

  ) with list items for Professional Experience, Roadmap & Strategic Ownership, Executive Communication. Skills (

  Skills

  ) with list items for Proficiency in SQL and Tableau, strong foundational understanding of Snowflake data warehousing architectures, behavioral analytics concepts (event tracking, funnel analysis, usage metrics). Qualifications (

  Qualifications

  ) with list items for Salesforce Ecosystem Experience, Domain Knowledge, Global Operations. Benefits (

  Benefits

  ) with list: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program. Pay (

  Pay

  ) with prose: The typical base salary range for this position is $150,100 - $227,000 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $180,200 - $247,900 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable. We could also include note about equitable compensation practices but that's boilerplate; omit. Schedule: none. Now produce HTML fragment: start with

  About the role

  then

  ...

  . Then

  Responsibilities

  ...
  . Then

  Requirements

  ...
  . Then

  Skills

  ...
  . Then

  Qualifications

  ...
  . Then

  Benefits

  ...
  . Then

  Pay

  ...

  . Make sure no extra whitespace? It's fine. Check that we didn't include any boilerplate like "Accommodations", "AI tools", "EEO", "Privacy Statement", "Posting Statement", "Pursuant to...", "At Salesforce, we believe in equitable compensation practices". Also removed "To get the best candidate experience...", "Job Category Data Job Details", "Apply today...", etc. Check that we kept all substantive info: About Salesforce description, The Experience description, responsibilities list, requirements (professional experience, roadmap, executive communication), skills (SQL, Tableau, Snowflake, behavioral analytics), qualifications (Salesforce ecosystem, domain knowledge, global operations), benefits list, pay range. We omitted "Even Better If..." heading but we used its content under Qualifications. Good. We omitted "You’re Our Person If..." heading but used its content under Requirements and Skills. Check that we didn't lose any piece: The "Professional Experience: 8–12+ years..." is under Requirements. "Roadmap & Strategic Ownership: Proven track record independently owning an analytics or data platform roadmap..." under Requirements. "Technical & Analytical Competency: Proficiency in SQL and Tableau..." under Skills. "Executive Communication: Excellent written and verbal communication skills..." under Requirements. Check that we didn't lose "Even Better If..." items: Salesforce Ecosystem Experience, Domain Knowledge, Global Operations under Qualifications. Check benefits: we captured list from "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Good. Check pay: we captured both ranges and note about base salary only. Check that we didn't include "The typical base salary range for this position is $150,100 - $227,000 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $180,