Senior Marketing Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. Let's parse the posting. First paragraph: company description, not needed for role sections. Then "About The Role & Team": description of role. That's about the role. Then bullet list: "As a Senior Marketing Analyst, You Will" with items. Those are responsibilities. Then "You'll be a great addition to the team if you have:" bullet list of desired traits (skills? maybe qualifications). Then "At a Minimum, You Need To Have" bullet list of minimum requirements (qualifications). Then "Our Values" etc. Then benefits section: "We care about the well-being of our team: We offer competitive pay and benefits packages..." then list of benefits. Pay: later "Based on legislation in California, the following details are for individuals who will work for Amplitude in San Francisco Bay Area of California. Salary range: $167,000 - $251,000 total target cash (inclusive of bonus or commission)". So we have pay info. Schedule: not mentioned. No schedule info. So we should not include Schedule section. We need headings:

for each section. We need to use

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

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to include sections only when posting has real specific content. Thus sections: About the role, Responsibilities, Requirements (maybe combine minimum requirements?), Qualifications (maybe the "great addition if you have" could be qualifications or skills). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which to use based on content. We have: - About the role: paragraph from "About The Role & Team". We'll put that in

  . - Responsibilities: the bullet list under "As a Senior Marketing Analyst, You Will". Use

  • . - Requirements: maybe the "At a Minimum, You Need To Have" list. That's minimum requirements. - Qualifications: maybe the "You'll be a great addition to the team if you have:" list could be qualifications or skills. The instruction separate Qualifications and Skills. We could treat that list as Qualifications (experience, skills). Or we could split: Qualifications = experience/education; Skills = technical skills. But we don't have explicit education. The list includes: experience in B2B SaaS, analytical, curiosity, ambiguity, communication, partnering cross-functionally. Those are more like skills/qualities. Could treat as Skills. But we also have "At a Minimum..." which includes experience, SQL, Python/R, data from multiple systems, dashboards, analytical concepts, leveraging AI. Those are also qualifications/skills. We need to decide mapping to avoid duplication. Perhaps we can combine: Use Qualifications for the minimum requirements (education/experience) and Skills for the "great addition if you have" (soft skills). However the minimum list also includes skills like SQL, Python, etc. Could treat that as Skills. But we need both sections if content exists. Let's examine: Minimum list includes: 5+ years experience, strong SQL skills, experience with Python/R, experience working with data from multiple systems, experience building dashboards, strong foundation in analytical/statistical concepts, experience leveraging AI. Those are technical qualifications/skills. The "great addition if you have" list includes: experience working in B2B SaaS and understand how Marketing teams think about pipeline, funnel performance, marketing attribution, ROI; highly analytical and naturally curious; comfortable with ambiguity; communicate complex analytical concepts clearly; enjoy partnering cross-functionally. Those are more like soft skills / qualities. Thus we can assign: - Qualifications: the minimum requirements list (experience, SQL, etc.) - Skills: the "great addition if you have" list (analytical, curiosity, communication, partnering). But the instruction says we can have both sections; we should not create empty sections. Both have content. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We might also include Requirements? The minimum list could be considered Requirements. But we already used Qualifications for that. To follow instruction, we could use Requirements for minimum list and Qualifications for the "great addition if you have". But then Skills would be empty. Better to follow the instruction's headings but we can omit sections if no content. So we need to decide which headings to use. We have content for: About the role, Responsibilities, Requirements (minimum), Qualifications (maybe the "great addition" list), Skills (maybe technical skills like SQL, Python, etc.), Benefits, Pay. We have overlapping content; we need to split logically. Let's assign: - Requirements: the "At a Minimum, You Need To Have" list (experience, SQL, etc.) as requirements. - Qualifications: maybe the "You'll be a great addition to the team if you have:" list as qualifications (desired qualifications). - Skills: maybe we could list specific technical skills like SQL, Python/R, Tableau, etc. But those are already in requirements. Could we separate? The instruction says use headings for Skills; we could put technical skills there. But we already used them in Requirements. Might duplicate. Better to not duplicate; we can put technical skills under Skills and keep Requirements for experience/education. However the minimum list includes experience (5+ years) and SQL, Python, etc. Could split: Requirements: 5+ years experience in marketing analytics, business analytics, GTM analytics, or related analytical role, ideally within B2B SaaS. Qualifications: strong SQL skills, experience with large datasets, experience with Python/R, experience working with data from multiple systems, experience building dashboards, strong foundation in analytical/statistical concepts, experience leveraging AI. Skills: maybe the soft skills list. But then we have three sections for similar content. Given the instruction to prefer a few substantive sections over many thin ones, we should combine where possible. So maybe we just have About the role, Responsibilities, Requirements (covering both minimum and desired), Benefits, Pay. And omit Qualifications and Skills if they'd be thin. But we need to follow the instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can choose which headings to use based on content. Thus we can have: - About the role - Responsibilities - Requirements (maybe combine minimum and desired) - Benefits - Pay We could also have Qualifications if we want to separate desired qualifications, but that might be thin. However the desired list has several bullet points, not thin. So we could have Qualifications for that list. Then Requirements for minimum list. Skills maybe we could omit because we already covered technical skills in Requirements or Qualifications. But we could put technical skills under Skills. However that would split the minimum list across two sections, causing duplication. Better: Let's treat: - Requirements: the minimum experience (5+ years experience, ideally B2B SaaS). That's a requirement. - Qualifications: the technical skills (SQL, Python/R, Tableau, data from multiple systems, dashboards, analytical concepts, leveraging AI). That's qualifications. - Skills: the soft skills (analytical, curiosity, communication, partnering). That's skills. Thus we have three sections with substantive content. Check if any of those sections would be thin: each has multiple bullet points. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll omit Schedule. Now we need to extract exact bullet points. Let's copy the relevant text. About The Role & Team paragraph: "Amplitude’s Commitment to Diversity Equity & Inclusion (DEI): ..." that's before About The Role. Actually after company description, there is "Amplitude’s Commitment to Diversity Equity & Inclusion (DEI): ..." then "About The Role & Team". The About The Role & Team paragraph: "About The Role & Team The Senior Marketing Analyst will be a strategic analytics partner to the Marketing organization, helping leaders understand performance, identify opportunities, and make better decisions through data. Reporting to the Director of Marketing Operations, you'll bring strong B2B SaaS analytics expertise to marketing planning, performance measurement, and business insights. You'll work closely with Marketing, GTM Analytics, Sales Analytics, Customer Success Analytics, and FP&A to connect data across the funnel and translate it into actionable recommendations. This is an opportunity to have a meaningful impact on how Amplitude measures and drives efficient GTM growth." We'll put that as prose in

    . Now Responsibilities bullet list under "As a Senior Marketing Analyst, You Will": - Turn data into actionable marketing insights: Analyze marketing performance and funnel trends to identify what's working, what's not, and where we should adjust our strategy or investment. - Partner with Marketing leadership: Develop reporting, analysis, and recommendations that help Marketing leaders evaluate performance, set priorities, and make informed short- and long-term decisions. - Own marketing analytics and reporting: Build and maintain dashboards, reporting, and analytical frameworks that give Marketing teams clear visibility into performance, pipeline, productivity, and ROI. - Drive analytical projects from end to end: Translate ambiguous business questions into analytical approaches, conduct rigorous analysis, communicate findings clearly, and turn insights into recommendations and action. - Improve our data and analytics foundation: Partner with Marketing Operations and cross-functional analytics teams to improve data quality, governance, processes, and the systems that power Marketing reporting and decision-making. We need to preserve all detail. Each bullet is a sentence with colon then explanation. We'll keep as

    items. Now Requirements (minimum) list under "At a Minimum, You Need To Have": - You have 5+ years of experience in marketing analytics, business analytics, GTM analytics, or a related analytical role, ideally within B2B SaaS. - You have strong SQL skills and experience working with large, complex datasets. - Experience with Python, R, or similar analytical tools is a plus. - You have experience working with data from multiple systems and translating it into meaningful business insights. - You have experience building and maintaining dashboards and reporting in tools such as Tableau, CRMA, or equivalent. - You have a strong foundation in analytical and statistical concepts, including hypothesis development, experimentation, data analysis, and translating findings into actionable recommendations. - You have experience leveraging AI to drive effective analysis and understand the importance of the underlying data quality Note: The third bullet says "Experience with Python, R, or similar analytical tools is a plus." That's a plus, not a requirement. But it's still part of the minimum list; we keep as is. Now Qualifications list under "You'll be a great addition to the team if you have:": - You have experience working in B2B SaaS and understand how Marketing teams think about pipeline, funnel performance, marketing attribution, and ROI. - You are highly analytical and naturally curious, with the ability to dig into complex data, identify meaningful patterns, and connect the dots across multiple sources. - You are comfortable working with ambiguity and can take a loosely defined business question and independently turn it into a clear analytical approach and actionable recommendation. - You communicate complex analytical concepts clearly to both technical and non-technical audiences and can tailor your storytelling to the audience. - You enjoy partnering cross-functionally and can build strong relationships with stakeholders across Marketing, Sales, Customer Success, Finance, and Analytics. Now Skills: we haven't assigned yet. If we treat the technical skills as Qualifications, we need a Skills section for something else. But we already used technical skills in Qualifications? Actually we put technical skills in Qualifications? Wait we assigned Qualifications to