Senior Manager, Customer Marketing
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 decide which sections to include. The posting includes:
- About SecurityScorecard (company overview). Could be considered "About the company" but not listed as a standard heading; we could include as a
maybe before sections. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should include sections: About the role (the description after "About the Role:"), Responsibilities (maybe the duties listed under Required Qualifications? Actually Required Qualifications includes many duties; we could treat that as Responsibilities/Requirements). Then Qualifications (maybe split Required and Preferred). Benefits (they have a Benefits paragraph). Pay (they have compensation range). Schedule (they have hybrid work model). So we can include sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Or combine Requirements and Qualifications.
We need to use - for any list of duties/requirements/benefits. So we need to extract lists.
Let's parse content.
About SecurityScorecard: paragraph about company. We'll keep as
maybe before sections.
About the Role: paragraph describing role: "We are looking for a strategic and highly collaborative Senior Manager, Customer Marketing to lead our customer lifecycle, retention, and advocacy initiatives. In this role, you will be the voice of the customer within the marketing team, designing campaigns and programs that drive engagement, loyalty, cross-sell/upsell revenue, and brand advocacy. You will partner closely with Customer Success, Sales, and Product teams to ensure our customers are extracting maximum value from our offerings and turning into our biggest champions. This role inherits and scales a live program portfolio: the GRR campaign supporting our 85% gross revenue retention target, an installed-base upsell motion (Ratings → MAX, Driftnet, and TITAN), and a growing customer reference engine. You will own these from day one. This role follows a hybrid work model based on proximity to our office locations. Employees who live within 75 miles of our Midtown NYC or Downtown Austin office are required to work onsite 1–2 days per week. Employees who live outside a 75-mile radius of both offices are eligible for fully remote work."
We could split: About the role (first sentences) and then maybe Schedule/hybrid work model as separate Schedule section. But the instruction says include a section only when posting has real specific content. The hybrid work model is specific, so we can have Schedule section.
Responsibilities: The duties listed under Required Qualifications (the bullet-like sentences). They are not formatted as bullet list but each sentence starts with a bold heading? Actually they are like:
Customer Strategy & Lifecycle Marketing Own the customer journey: Map and optimize the post-purchase journey — onboarding, adoption, renewal, and expansion — including the freemium-to-paid conversion path (email drip journey and conversion optimization program currently in flight).Own the GRR campaign portfolio: Run and scale the retention programs already in motion, including the 50 Customer Forums series with Cyber Rescue Alliance, the Platform Pulse "what's new at SSC" webinar series, the Behind the Score educational webinar series (201 registrants in its first run), Arcade clickable product demos, and the GRR Activities by Motion tracker as the operating system for all of it.Drive expansion revenue with signal-based triggers: Partner with Sales and Customer Success to build campaigns triggered by product and portfolio signals — vendor score drops, new critical vendor findings, fourth-party incidents in a customer's ecosystem, questionnaire/assessment volume growth, approaching renewals, and usage patterns that indicate MAX, Driftnet, or TITAN fit. Convert these triggers into qualified upsell pipeline routed to CSMs and AEs, aligned to the CRO's installed-base cross-sell motion.Reduce churn: Develop proactive retention plays for at-risk accounts — including re-engagement programs for dark or non-operationalized accounts — using customer health, engagement, and support signals to intervene before renewal risk becomes renewal loss. Advocacy, References & Community Build the reference engine: Identify, nurture, and mobilize customers for case studies, testimonials, webinars, speaking slots, and peer reviews (G2, Peerspot). Scale the current case-study pipeline (recent examples: MRS, Cedia, Axia, Sistecredito internationally; HYPR and Jappware testimonials) into a systematic program with regional coverage, and feed named references into ABM plays — one anchor customer per vertical unlocks the whole segment.Peer-to-peer selling: Run customers-only forums and roundtables where current customers present value to peers (the Cyber Rescue Alliance forum model), and place customer champions into field events, CISO dinners, and Odyssey.Foster community: Launch and manage user groups, exclusive events, and community programs — with Odyssey (our annual customer conference) as the flagship advocacy moment of the year. Cross-Functional Collaboration & Insights Sales & CS enablement: Create customer-centric collateral, EBR decks, ROI artifacts (e.g., the MAX Questionnaire ROI Calculator), and toolkits that help customer-facing teams drive adoption and secure renewals.Product marketing alignment: Act as the feedback loop between customers and Product; coordinate with PMM on release communications, the monthly product newsletter, and Scorecard Digest.AI-assisted lifecycle: Work with Marketing AI Ops to automate trigger detection and nurture (Maxine email workflows, Marketo journeys, Pocus playbooks), so lifecycle coverage scales without linear headcount. Measurement & Reporting Own the numbers: GRR (85% target), NRR, upsell/cross-sell pipeline sourced from customer marketing, reference/advocacy pipeline, customer health and NPS, webinar and forum engagement-to-expansion conversion.Data-driven optimization: Report weekly into the CMO update; analyze campaign performance per motion in the GRR tracker and continuously test and improve.
These are essentially responsibilities. We can break them into a
- list, each responsibility as a list item. However the instruction: Use
- for any list of duties/requirements/benefits. So we should create a list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each responsibility as a list item, preserving the details.
We also have Required Qualifications section: It lists items like:
- Customer Strategy & Lifecycle Marketing (but that seems overlapping with responsibilities). Actually the Required Qualifications section appears to be a list of responsibilities again? Wait the text after "Required Qualifications:" seems to be a continuation of responsibilities but formatted as headings. Actually the posting may have mislabeled; but we need to treat Required Qualifications as a section with bullet points. However the content under Required Qualifications is essentially the same as responsibilities (maybe they intended to list responsibilities). But we must not duplicate content. We need to preserve ALL substantive information; if we treat Required Qualifications as a section, we must include its content. But if we already included responsibilities, we might duplicate. However the instruction says do not repeat the job title as a heading, but doesn't forbid repeating content. However we should avoid duplication if possible. But we need to preserve all substantive information; if we omit the Required Qualifications section, we lose that content (though it's similar to responsibilities). But maybe the responsibilities are under "About the Role" and the Required Qualifications are separate list of qualifications (like experience, skills). Actually reading: After "About the Role:" there is a paragraph describing role. Then "Required Qualifications:" then a bunch of bullet-like items that start with bold headings like "Customer Strategy & Lifecycle Marketing Own the customer journey: ..." Those look like responsibilities, not qualifications. Then after that, "Preferred Qualifications:" then list of experience etc.
Thus the posting seems to have mislabeled: Required Qualifications actually are responsibilities/duties. Preferred Qualifications are actual qualifications.
Thus we should treat:
- About the role: paragraph (maybe combine with About SecurityScorecard? but we can have About the role section).
- Responsibilities: list of items under Required Qualifications.
- Qualifications: list under Preferred Qualifications (maybe also include any required qualifications like experience? but there are none explicit besides the Preferred). Could also include "Required Qualifications" as a section but we already used that for responsibilities; maybe rename to Responsibilities.
- Benefits: paragraph.
- Pay: compensation range.
- Schedule: hybrid work model.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only.
Let's extract each piece.
About SecurityScorecard: we can keep as a
before sections.
About the role: we have paragraph: "We are looking for a strategic and highly collaborative Senior Manager, Customer Marketing to lead our customer lifecycle, retention, and advocacy initiatives. In this role, you will be the voice of the customer within the marketing team, designing campaigns and programs that drive engagement, loyalty, cross-sell/upsell revenue, and brand advocacy. You will partner closely with Customer Success, Sales, and Product teams to ensure our customers are extracting maximum value from our offerings and turning into our biggest champions. This role inherits and scales a live program portfolio: the GRR campaign supporting our 85% gross revenue retention target, an installed-base upsell motion (Ratings → MAX, Driftnet, and TITAN), and a growing customer reference engine. You will own these from day one."
We could keep that as
under
About the role
.
Responsibilities: list items from Required Qualifications.
Let's break each responsibility:
1. Customer Strategy & Lifecycle Marketing: Own the customer journey: Map and optimize the post-purchase journey — onboarding, adoption, renewal, and expansion — including the freemium-to-paid conversion path (email drip journey and conversion optimization program currently in flight).
2. Own the GRR campaign portfolio: Run and scale the retention programs already in motion, including the 50 Customer Forums series with Cyber Rescue Alliance, the Platform Pulse "what's new at SSC" webinar series, the Behind the Score educational webinar series (201 registrants in its first run), Arcade clickable product demos, and the GRR Activities by Motion tracker as the operating system for all of it.
3. Drive expansion revenue with signal-based triggers: Partner with Sales and Customer Success to build campaigns triggered by product and portfolio signals — vendor score drops, new critical vendor findings, fourth-party incidents in a customer's ecosystem, questionnaire/assessment volume growth, approaching renewals, and usage patterns that indicate MAX, Driftnet, or TITAN fit. Convert these triggers into qualified upsell pipeline routed to CSMs and AEs, aligned to the CRO's installed-base cross-sell motion.
4. Reduce churn
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 decide which sections to include. The posting includes: - About SecurityScorecard (company overview). Could be considered "About the company" but not listed as a standard heading; we could include as a
maybe before sections. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should include sections: About the role (the description after "About the Role:"), Responsibilities (maybe the duties listed under Required Qualifications? Actually Required Qualifications includes many duties; we could treat that as Responsibilities/Requirements). Then Qualifications (maybe split Required and Preferred). Benefits (they have a Benefits paragraph). Pay (they have compensation range). Schedule (they have hybrid work model). So we can include sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Or combine Requirements and Qualifications.
We need to use - for any list of duties/requirements/benefits. So we need to extract lists.
Let's parse content.
About SecurityScorecard: paragraph about company. We'll keep as
maybe before sections.
About the Role: paragraph describing role: "We are looking for a strategic and highly collaborative Senior Manager, Customer Marketing to lead our customer lifecycle, retention, and advocacy initiatives. In this role, you will be the voice of the customer within the marketing team, designing campaigns and programs that drive engagement, loyalty, cross-sell/upsell revenue, and brand advocacy. You will partner closely with Customer Success, Sales, and Product teams to ensure our customers are extracting maximum value from our offerings and turning into our biggest champions. This role inherits and scales a live program portfolio: the GRR campaign supporting our 85% gross revenue retention target, an installed-base upsell motion (Ratings → MAX, Driftnet, and TITAN), and a growing customer reference engine. You will own these from day one. This role follows a hybrid work model based on proximity to our office locations. Employees who live within 75 miles of our Midtown NYC or Downtown Austin office are required to work onsite 1–2 days per week. Employees who live outside a 75-mile radius of both offices are eligible for fully remote work."
We could split: About the role (first sentences) and then maybe Schedule/hybrid work model as separate Schedule section. But the instruction says include a section only when posting has real specific content. The hybrid work model is specific, so we can have Schedule section.
Responsibilities: The duties listed under Required Qualifications (the bullet-like sentences). They are not formatted as bullet list but each sentence starts with a bold heading? Actually they are like:
Customer Strategy & Lifecycle Marketing Own the customer journey: Map and optimize the post-purchase journey — onboarding, adoption, renewal, and expansion — including the freemium-to-paid conversion path (email drip journey and conversion optimization program currently in flight).Own the GRR campaign portfolio: Run and scale the retention programs already in motion, including the 50 Customer Forums series with Cyber Rescue Alliance, the Platform Pulse "what's new at SSC" webinar series, the Behind the Score educational webinar series (201 registrants in its first run), Arcade clickable product demos, and the GRR Activities by Motion tracker as the operating system for all of it.Drive expansion revenue with signal-based triggers: Partner with Sales and Customer Success to build campaigns triggered by product and portfolio signals — vendor score drops, new critical vendor findings, fourth-party incidents in a customer's ecosystem, questionnaire/assessment volume growth, approaching renewals, and usage patterns that indicate MAX, Driftnet, or TITAN fit. Convert these triggers into qualified upsell pipeline routed to CSMs and AEs, aligned to the CRO's installed-base cross-sell motion.Reduce churn: Develop proactive retention plays for at-risk accounts — including re-engagement programs for dark or non-operationalized accounts — using customer health, engagement, and support signals to intervene before renewal risk becomes renewal loss. Advocacy, References & Community Build the reference engine: Identify, nurture, and mobilize customers for case studies, testimonials, webinars, speaking slots, and peer reviews (G2, Peerspot). Scale the current case-study pipeline (recent examples: MRS, Cedia, Axia, Sistecredito internationally; HYPR and Jappware testimonials) into a systematic program with regional coverage, and feed named references into ABM plays — one anchor customer per vertical unlocks the whole segment.Peer-to-peer selling: Run customers-only forums and roundtables where current customers present value to peers (the Cyber Rescue Alliance forum model), and place customer champions into field events, CISO dinners, and Odyssey.Foster community: Launch and manage user groups, exclusive events, and community programs — with Odyssey (our annual customer conference) as the flagship advocacy moment of the year. Cross-Functional Collaboration & Insights Sales & CS enablement: Create customer-centric collateral, EBR decks, ROI artifacts (e.g., the MAX Questionnaire ROI Calculator), and toolkits that help customer-facing teams drive adoption and secure renewals.Product marketing alignment: Act as the feedback loop between customers and Product; coordinate with PMM on release communications, the monthly product newsletter, and Scorecard Digest.AI-assisted lifecycle: Work with Marketing AI Ops to automate trigger detection and nurture (Maxine email workflows, Marketo journeys, Pocus playbooks), so lifecycle coverage scales without linear headcount. Measurement & Reporting Own the numbers: GRR (85% target), NRR, upsell/cross-sell pipeline sourced from customer marketing, reference/advocacy pipeline, customer health and NPS, webinar and forum engagement-to-expansion conversion.Data-driven optimization: Report weekly into the CMO update; analyze campaign performance per motion in the GRR tracker and continuously test and improve.
These are essentially responsibilities. We can break them into a
- list, each responsibility as a list item. However the instruction: Use
- for any list of duties/requirements/benefits. So we should create a list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each responsibility as a list item, preserving the details.
We also have Required Qualifications section: It lists items like:
- Customer Strategy & Lifecycle Marketing (but that seems overlapping with responsibilities). Actually the Required Qualifications section appears to be a list of responsibilities again? Wait the text after "Required Qualifications:" seems to be a continuation of responsibilities but formatted as headings. Actually the posting may have mislabeled; but we need to treat Required Qualifications as a section with bullet points. However the content under Required Qualifications is essentially the same as responsibilities (maybe they intended to list responsibilities). But we must not duplicate content. We need to preserve ALL substantive information; if we treat Required Qualifications as a section, we must include its content. But if we already included responsibilities, we might duplicate. However the instruction says do not repeat the job title as a heading, but doesn't forbid repeating content. However we should avoid duplication if possible. But we need to preserve all substantive information; if we omit the Required Qualifications section, we lose that content (though it's similar to responsibilities). But maybe the responsibilities are under "About the Role" and the Required Qualifications are separate list of qualifications (like experience, skills). Actually reading: After "About the Role:" there is a paragraph describing role. Then "Required Qualifications:" then a bunch of bullet-like items that start with bold headings like "Customer Strategy & Lifecycle Marketing Own the customer journey: ..." Those look like responsibilities, not qualifications. Then after that, "Preferred Qualifications:" then list of experience etc.
Thus the posting seems to have mislabeled: Required Qualifications actually are responsibilities/duties. Preferred Qualifications are actual qualifications.
Thus we should treat:
- About the role: paragraph (maybe combine with About SecurityScorecard? but we can have About the role section).
- Responsibilities: list of items under Required Qualifications.
- Qualifications: list under Preferred Qualifications (maybe also include any required qualifications like experience? but there are none explicit besides the Preferred). Could also include "Required Qualifications" as a section but we already used that for responsibilities; maybe rename to Responsibilities.
- Benefits: paragraph.
- Pay: compensation range.
- Schedule: hybrid work model.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only.
Let's extract each piece.
About SecurityScorecard: we can keep as a
before sections.
About the role: we have paragraph: "We are looking for a strategic and highly collaborative Senior Manager, Customer Marketing to lead our customer lifecycle, retention, and advocacy initiatives. In this role, you will be the voice of the customer within the marketing team, designing campaigns and programs that drive engagement, loyalty, cross-sell/upsell revenue, and brand advocacy. You will partner closely with Customer Success, Sales, and Product teams to ensure our customers are extracting maximum value from our offerings and turning into our biggest champions. This role inherits and scales a live program portfolio: the GRR campaign supporting our 85% gross revenue retention target, an installed-base upsell motion (Ratings → MAX, Driftnet, and TITAN), and a growing customer reference engine. You will own these from day one."
We could keep that as
under
About the role
.
Responsibilities: list items from Required Qualifications.
Let's break each responsibility:
1. Customer Strategy & Lifecycle Marketing: Own the customer journey: Map and optimize the post-purchase journey — onboarding, adoption, renewal, and expansion — including the freemium-to-paid conversion path (email drip journey and conversion optimization program currently in flight).
2. Own the GRR campaign portfolio: Run and scale the retention programs already in motion, including the 50 Customer Forums series with Cyber Rescue Alliance, the Platform Pulse "what's new at SSC" webinar series, the Behind the Score educational webinar series (201 registrants in its first run), Arcade clickable product demos, and the GRR Activities by Motion tracker as the operating system for all of it.
3. Drive expansion revenue with signal-based triggers: Partner with Sales and Customer Success to build campaigns triggered by product and portfolio signals — vendor score drops, new critical vendor findings, fourth-party incidents in a customer's ecosystem, questionnaire/assessment volume growth, approaching renewals, and usage patterns that indicate MAX, Driftnet, or TITAN fit. Convert these triggers into qualified upsell pipeline routed to CSMs and AEs, aligned to the CRO's installed-base cross-sell motion.
4. Reduce churn
maybe before sections. About the Role: paragraph describing role: "We are looking for a strategic and highly collaborative Senior Manager, Customer Marketing to lead our customer lifecycle, retention, and advocacy initiatives. In this role, you will be the voice of the customer within the marketing team, designing campaigns and programs that drive engagement, loyalty, cross-sell/upsell revenue, and brand advocacy. You will partner closely with Customer Success, Sales, and Product teams to ensure our customers are extracting maximum value from our offerings and turning into our biggest champions. This role inherits and scales a live program portfolio: the GRR campaign supporting our 85% gross revenue retention target, an installed-base upsell motion (Ratings → MAX, Driftnet, and TITAN), and a growing customer reference engine. You will own these from day one. This role follows a hybrid work model based on proximity to our office locations. Employees who live within 75 miles of our Midtown NYC or Downtown Austin office are required to work onsite 1–2 days per week. Employees who live outside a 75-mile radius of both offices are eligible for fully remote work." We could split: About the role (first sentences) and then maybe Schedule/hybrid work model as separate Schedule section. But the instruction says include a section only when posting has real specific content. The hybrid work model is specific, so we can have Schedule section. Responsibilities: The duties listed under Required Qualifications (the bullet-like sentences). They are not formatted as bullet list but each sentence starts with a bold heading? Actually they are like: Customer Strategy & Lifecycle Marketing Own the customer journey: Map and optimize the post-purchase journey — onboarding, adoption, renewal, and expansion — including the freemium-to-paid conversion path (email drip journey and conversion optimization program currently in flight).Own the GRR campaign portfolio: Run and scale the retention programs already in motion, including the 50 Customer Forums series with Cyber Rescue Alliance, the Platform Pulse "what's new at SSC" webinar series, the Behind the Score educational webinar series (201 registrants in its first run), Arcade clickable product demos, and the GRR Activities by Motion tracker as the operating system for all of it.Drive expansion revenue with signal-based triggers: Partner with Sales and Customer Success to build campaigns triggered by product and portfolio signals — vendor score drops, new critical vendor findings, fourth-party incidents in a customer's ecosystem, questionnaire/assessment volume growth, approaching renewals, and usage patterns that indicate MAX, Driftnet, or TITAN fit. Convert these triggers into qualified upsell pipeline routed to CSMs and AEs, aligned to the CRO's installed-base cross-sell motion.Reduce churn: Develop proactive retention plays for at-risk accounts — including re-engagement programs for dark or non-operationalized accounts — using customer health, engagement, and support signals to intervene before renewal risk becomes renewal loss. Advocacy, References & Community Build the reference engine: Identify, nurture, and mobilize customers for case studies, testimonials, webinars, speaking slots, and peer reviews (G2, Peerspot). Scale the current case-study pipeline (recent examples: MRS, Cedia, Axia, Sistecredito internationally; HYPR and Jappware testimonials) into a systematic program with regional coverage, and feed named references into ABM plays — one anchor customer per vertical unlocks the whole segment.Peer-to-peer selling: Run customers-only forums and roundtables where current customers present value to peers (the Cyber Rescue Alliance forum model), and place customer champions into field events, CISO dinners, and Odyssey.Foster community: Launch and manage user groups, exclusive events, and community programs — with Odyssey (our annual customer conference) as the flagship advocacy moment of the year. Cross-Functional Collaboration & Insights Sales & CS enablement: Create customer-centric collateral, EBR decks, ROI artifacts (e.g., the MAX Questionnaire ROI Calculator), and toolkits that help customer-facing teams drive adoption and secure renewals.Product marketing alignment: Act as the feedback loop between customers and Product; coordinate with PMM on release communications, the monthly product newsletter, and Scorecard Digest.AI-assisted lifecycle: Work with Marketing AI Ops to automate trigger detection and nurture (Maxine email workflows, Marketo journeys, Pocus playbooks), so lifecycle coverage scales without linear headcount. Measurement & Reporting Own the numbers: GRR (85% target), NRR, upsell/cross-sell pipeline sourced from customer marketing, reference/advocacy pipeline, customer health and NPS, webinar and forum engagement-to-expansion conversion.Data-driven optimization: Report weekly into the CMO update; analyze campaign performance per motion in the GRR tracker and continuously test and improve. These are essentially responsibilities. We can break them into a
- list, each responsibility as a list item. However the instruction: Use
- for any list of duties/requirements/benefits. So we should create a list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each responsibility as a list item, preserving the details.
We also have Required Qualifications section: It lists items like:
- Customer Strategy & Lifecycle Marketing (but that seems overlapping with responsibilities). Actually the Required Qualifications section appears to be a list of responsibilities again? Wait the text after "Required Qualifications:" seems to be a continuation of responsibilities but formatted as headings. Actually the posting may have mislabeled; but we need to treat Required Qualifications as a section with bullet points. However the content under Required Qualifications is essentially the same as responsibilities (maybe they intended to list responsibilities). But we must not duplicate content. We need to preserve ALL substantive information; if we treat Required Qualifications as a section, we must include its content. But if we already included responsibilities, we might duplicate. However the instruction says do not repeat the job title as a heading, but doesn't forbid repeating content. However we should avoid duplication if possible. But we need to preserve all substantive information; if we omit the Required Qualifications section, we lose that content (though it's similar to responsibilities). But maybe the responsibilities are under "About the Role" and the Required Qualifications are separate list of qualifications (like experience, skills). Actually reading: After "About the Role:" there is a paragraph describing role. Then "Required Qualifications:" then a bunch of bullet-like items that start with bold headings like "Customer Strategy & Lifecycle Marketing Own the customer journey: ..." Those look like responsibilities, not qualifications. Then after that, "Preferred Qualifications:" then list of experience etc.
Thus the posting seems to have mislabeled: Required Qualifications actually are responsibilities/duties. Preferred Qualifications are actual qualifications.
Thus we should treat:
- About the role: paragraph (maybe combine with About SecurityScorecard? but we can have About the role section).
- Responsibilities: list of items under Required Qualifications.
- Qualifications: list under Preferred Qualifications (maybe also include any required qualifications like experience? but there are none explicit besides the Preferred). Could also include "Required Qualifications" as a section but we already used that for responsibilities; maybe rename to Responsibilities.
- Benefits: paragraph.
- Pay: compensation range.
- Schedule: hybrid work model.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only.
Let's extract each piece.
About SecurityScorecard: we can keep as a
before sections. About the role: we have paragraph: "We are looking for a strategic and highly collaborative Senior Manager, Customer Marketing to lead our customer lifecycle, retention, and advocacy initiatives. In this role, you will be the voice of the customer within the marketing team, designing campaigns and programs that drive engagement, loyalty, cross-sell/upsell revenue, and brand advocacy. You will partner closely with Customer Success, Sales, and Product teams to ensure our customers are extracting maximum value from our offerings and turning into our biggest champions. This role inherits and scales a live program portfolio: the GRR campaign supporting our 85% gross revenue retention target, an installed-base upsell motion (Ratings → MAX, Driftnet, and TITAN), and a growing customer reference engine. You will own these from day one." We could keep that as
under
About the role
. Responsibilities: list items from Required Qualifications. Let's break each responsibility: 1. Customer Strategy & Lifecycle Marketing: Own the customer journey: Map and optimize the post-purchase journey — onboarding, adoption, renewal, and expansion — including the freemium-to-paid conversion path (email drip journey and conversion optimization program currently in flight). 2. Own the GRR campaign portfolio: Run and scale the retention programs already in motion, including the 50 Customer Forums series with Cyber Rescue Alliance, the Platform Pulse "what's new at SSC" webinar series, the Behind the Score educational webinar series (201 registrants in its first run), Arcade clickable product demos, and the GRR Activities by Motion tracker as the operating system for all of it. 3. Drive expansion revenue with signal-based triggers: Partner with Sales and Customer Success to build campaigns triggered by product and portfolio signals — vendor score drops, new critical vendor findings, fourth-party incidents in a customer's ecosystem, questionnaire/assessment volume growth, approaching renewals, and usage patterns that indicate MAX, Driftnet, or TITAN fit. Convert these triggers into qualified upsell pipeline routed to CSMs and AEs, aligned to the CRO's installed-base cross-sell motion. 4. Reduce churn
- for any list of duties/requirements/benefits. So we should create a list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each responsibility as a list item, preserving the details.
We also have Required Qualifications section: It lists items like:
- Customer Strategy & Lifecycle Marketing (but that seems overlapping with responsibilities). Actually the Required Qualifications section appears to be a list of responsibilities again? Wait the text after "Required Qualifications:" seems to be a continuation of responsibilities but formatted as headings. Actually the posting may have mislabeled; but we need to treat Required Qualifications as a section with bullet points. However the content under Required Qualifications is essentially the same as responsibilities (maybe they intended to list responsibilities). But we must not duplicate content. We need to preserve ALL substantive information; if we treat Required Qualifications as a section, we must include its content. But if we already included responsibilities, we might duplicate. However the instruction says do not repeat the job title as a heading, but doesn't forbid repeating content. However we should avoid duplication if possible. But we need to preserve all substantive information; if we omit the Required Qualifications section, we lose that content (though it's similar to responsibilities). But maybe the responsibilities are under "About the Role" and the Required Qualifications are separate list of qualifications (like experience, skills). Actually reading: After "About the Role:" there is a paragraph describing role. Then "Required Qualifications:" then a bunch of bullet-like items that start with bold headings like "Customer Strategy & Lifecycle Marketing Own the customer journey: ..." Those look like responsibilities, not qualifications. Then after that, "Preferred Qualifications:" then list of experience etc.
Thus the posting seems to have mislabeled: Required Qualifications actually are responsibilities/duties. Preferred Qualifications are actual qualifications.
Thus we should treat:
- About the role: paragraph (maybe combine with About SecurityScorecard? but we can have About the role section).
- Responsibilities: list of items under Required Qualifications.
- Qualifications: list under Preferred Qualifications (maybe also include any required qualifications like experience? but there are none explicit besides the Preferred). Could also include "Required Qualifications" as a section but we already used that for responsibilities; maybe rename to Responsibilities.
- Benefits: paragraph.
- Pay: compensation range.
- Schedule: hybrid work model.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only.
Let's extract each piece.
About SecurityScorecard: we can keep as a