Marketing Analytics Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting: It includes a description of company, then role description. We need to decide sections. We have responsibilities listed under "Key Responsibilities". That's a list. So we can have

Responsibilities

with

• items. We have "Basic Qualifications" and "Preferred Qualifications". Those could be under Requirements or Qualifications. The instruction: Use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Basic and Preferred under Qualifications maybe. Or separate Requirements and Qualifications? The instruction says we can use those headings; we should include sections only when posting has real specific content. We have qualifications content. So we can have

  Qualifications

  with sub-sections? Probably just list items. We also have Pay: The posting includes base salary range $145,000 - $220,000 USD, plus bonus, commission, equity, benefits. So we have Pay info. So we should include

  Pay

  with that content. We have Benefits: The posting includes a "What We Offer" section describing benefits. So we can include

  Benefits

  with list. Schedule: The posting mentions hybrid work model, expected to come into SF office two times per week. That's schedule info. So we can include

  Schedule

  with that. We also might have About the role: The initial description about role could be under About the role. But we already have responsibilities etc. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could include About the role as a brief summary paragraph. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, legal, navigation, etc. Also remove duplicated lines, application instructions, cookie/navigation etc. We need to preserve all substantive information. So we need to include the responsibilities list exactly as given (but we can paraphrase? Must preserve all substantive information, not invent or summarize away detail. So we should keep the bullet points as they are, maybe slightly trimmed but not lose meaning. We should not omit any responsibility bullet. Similarly for qualifications: Basic Qualifications list and Preferred Qualifications list. We need to keep them. Benefits: list from "What We Offer". We need to keep all items. Pay: include base salary range and mention bonus, commission, equity, benefits. Schedule: mention hybrid, two times per week in SF office. About the role: we can summarize the initial paragraphs describing the role and team. Must preserve all substantive information; we can't omit details. But we can condense into a paragraph that captures the essence? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit any detail; we need to keep all information. However, we can rephrase but must keep all details. That's tough: we could include the original paragraphs as

  under About the role. That would preserve all info. That seems acceptable. Thus we will have sections:

  About the role

  ... (the initial descriptive paragraphs up to "Key Responsibilities")

  Then Responsibilities. Then Qualifications (maybe split into Basic and Preferred? Could have two subheadings? But only allowed headings are those listed; we could still include

  Basic Qualifications

  but that's not in the list. Better to combine under Qualifications and maybe separate with Basic and Preferred inside? But that might be considered adding structure not in list. However, we can still include

  Basic Qualifications

  and

  Preferred Qualifications

  as they are not prohibited; the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings; but we could still use others? Safer to stick to those. So we will have one Qualifications section containing both basic and preferred, maybe with subheadings using or

  ? But they said use

  for section headings; they didn't forbid other headings, but to be safe we can use

  for Qualifications and inside we can have

  for Basic and Preferred? That might be okay. But to avoid risk, we can just list all qualifications as a combined list, but we need to differentiate basic vs preferred? The instruction says preserve all substantive information; if we merge them, we lose the distinction between basic and preferred. That's substantive. So we need to keep that distinction. We could use

  Basic Qualifications

  and

  Preferred Qualifications

  as headings; they are not in the examples but still are section headings. The instruction didn't say we cannot use other headings; it gave examples. I think it's okay. Similarly for Skills: we could have a Skills section if there are specific skills listed; but we have skills embedded in qualifications. Might not need separate Skills. We also have Requirements heading; we could put Basic Qualifications under Requirements and Preferred under Qualifications? But we have both. Let's decide: Use sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Pay, Schedule. That covers all. Now we need to strip boilerplate: Remove EEO, legal, navigation, cookie, etc. Also remove "Where we work", "How We Work", "Our values", "Manager Expectations", "What We Offer" (we keep benefits but not the heading "What We Offer"? We'll keep benefits content). Also remove "About PagerDuty" duplicate description maybe; we already have About the role includes company description? The initial paragraph includes company overview; we can keep that as part of About the role. The later "About PagerDuty" repeats similar; we can omit duplicate. Also remove "Additional Information", "PagerDuty is an equal opportunity employer", etc. Also remove "Where we work" location restrictions etc. That's not needed for the role? Might be considered substantive? It's about location restrictions; could be relevant. But the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Location restrictions might be considered legal? It's about eligibility; maybe it's substantive? It's about where candidates can reside. Could be considered part of job posting. However, it's somewhat boilerplate but still specific. The instruction says remove duplicated lines, but not explicitly location restrictions. I'd keep it? Might be considered part of "Where we work". But it's a list of ineligible locations. Might be considered relevant. However, the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Location restrictions could be considered legal. I'd remove it to be safe. Also remove "How We Work", "Our values", "Manager Expectations", "What We Offer" (we keep benefits but not the heading). Actually "What We Offer" includes benefits list; we will extract benefits list and put under Benefits heading. So we can discard the surrounding text. Also remove "About PagerDuty" duplicate. Also remove "PagerDuty is Great Place to Work-certified™" etc. That's boilerplate? Might be considered marketing but still substantive? Could be considered fluff. I'd remove. Also remove "Additional Information", "PagerDuty is an equal opportunity employer", privacy, accommodation, E-Verify. Also remove "Where we work" location restrictions. Also remove "How We Work", "Our values", "Manager Expectations", "What We Offer" (we keep benefits but not the heading). Actually we need to keep benefits content; we can extract the bullet list under "What We Offer". We'll put that under Benefits. Now we need to ensure we don't include any application instructions like "Hesitant to apply? We encourage you to submit your resume..." etc. That's application instructions; remove. Also remove "If this just isn’t the right role or time - sign up for job alerts!" remove. Also remove "We encourage you to submit your resume even if you don't meet every requirement." That's application instruction; remove. Now we need to preserve all substantive information: responsibilities list, qualifications lists, benefits list, pay, schedule, about the role description. Let's extract the About the role text: From start: "PagerDuty, Inc. (NYSE: PD) is the global leader in AI-first digital operations. By automatically detecting, diagnosing, and remediating issues, the PagerDuty Platform orchestrates AI agents and automated workflows with context from over 750 integrations. Trusted by approximately two-thirds of the Fortune 100 and nearly half of the Fortune 500, PagerDuty is the industry standard for organizations scaling resilient, autonomous operations. Notable customers include Chipotle, Cloudflare, Docusign, Fox, Nvidia, Salesforce, Spotify, Zoom and more. We are growing rapidly and hiring top talent with leading AI skills across engineering, sales, product, marketing, and beyond as we build the leading digital operations platform. PagerDuty's Marketing Operations & Analytics team is the measurement backbone for the marketing organization. We define, produce, and defend the numbers that marketing and commercial leadership use to run the business, from funnel pacing and pipeline generation through ROI and closed-won contribution. We're hiring a Marketing Analytics Manager to own our recurring marketing and commercial performance reporting and become the reliable answer to "how are we pacing, and why?" You'll work primarily in Tableau, Snowflake, Salesforce, and Google Sheets, partnering closely with BI/Data, Finance, and Sales Operations. As a hands-on analyst you will own highly visible recurring deliverables from your first quarter, work directly with marketing leadership, and have real latitude to automate what's currently manual. You’ll have high visibility, real influence on how the org spends, and a short path from "this is broken" to "I fixed it."" That's the description before "Key Responsibilities". We'll put that in

  . Now Responsibilities: list items under "Key Responsibilities". We need to capture each bullet. Let's list them: - Produce weekly KPI updates: Pacing against funnel targets, pipeline generation, and bookings. Including calling out what's driving variances. - Deliver the monthly metrics, including plain-language explanation of what each metric means for a non-technical audience to drive program or leadership decision-making. - Support marketing leadership by providing accurate, up-to-date metrics needed for cross functional leadership meetings. - Support monthly and quarterly business review reporting, highlighting the most significant changes and data points from the period to enable strategic decisions and drive revenue generation. - Maintain recurring ROI reporting, including overall marketing ROI and event ROI based on marketing-contributed closed won - Maintain Tableau dashboards built on Snowflake, Salesforce, and billing data. Including our core marketing funnel metrics data source, with documented definitions and repeatable QA checks. - Write SQL to pull, validate, and reconcile data across sources, and diagnose the differences that may arise with them. - Identify data-quality problems like duplicate counting, incomplete data, level-of-grain mismatches and provide clear recommendations for resolution to the right owners. - Maintain documentation marketing leaders use for dashboards to answer questions. - Support the annual marketing funnel target-setting process: maintain source