Senior Product Marketing Manager (Temp)

We need to output HTML fragment with sections only if real content. No markdown fences. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. The posting includes: - Intro: "Presidio, Where Teamwork and Innovation Shape the Future At Presidio, we're at the forefront..." This is maybe about company, not a section. Could be "About the role"? Actually "The Role" heading appears. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has "The Role" (maybe treat as About the role). Then "Responsibilities Include". Then "Required Skills". Then "Your future at Presidio" (maybe about company). Then "About Presidio". Then EEO etc which we must remove. We need to preserve substantive info, not repeat job title. No Job ID. We need to decide which sections to include: - About the role: content from "The Role" paragraph: "The Senior Product Manager serves as leader within the Product Marketing organization, partnering with the Director of Product Marketing to lead strategic initiatives, help direct supplemental resources, and accelerate delivery of high-impact marketing messages, collateral and customer-facing materials." Also maybe "Your future at Presidio" and "About Presidio" could be considered "About the role"? But they are more about company. The instruction: use headings for sections like About the role, Responsibilities, etc. So we should map content accordingly. Responsibilities: list of duties. The posting has "Responsibilities Include" then a list of items separated by commas and line breaks. We need to extract each duty as

. Let's list them: - Translating strategic priorities into executable work plans – supporting Lighthouse and Security Sales Motions - Helping maintain dashboards and status reporting. - Focusing on sales and practice defined priorities - Directing and work with strategic design partners and product marketing execution resources. - Forecasting work efforts on assignments for accurate reporting on project delivery. - Reviewing work for quality and alignment with Product Marketing objectives. - Delivering value propositions, messaging frameworks, solution briefs, sales kits, executive presentations, sales enablement assets, marketing collateral, and AI marketing deliverables. - Partnering with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders - Developing repeatable workflows, dashboards, governance, and process improvements. - Key areas of focus (maybe duplicate) but we can treat as subpoints: Actually after responsibilities they repeat some items: "Key areas of focusTranslate strategic priorities into executable work plans – supporting Lighthouse and Security Sales MotionsHelp maintain dashboards and status reporting.Focus on sales and practice defined prioritiesProject orchestration with design team in India to translate messaging into customer facing materialsCross functional collaboration with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholdersMarketing DeliverablesDeliver value propositions, messaging frameworks, solution briefs, sales kits, executive presentations, sales enablement assets, marketing collateral, and AI marketing deliverables.Develop repeatable workflows, dashboards, governance, and process improvements with program managers." These seem like repeats; we should preserve all substantive info but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines are considered boilerplate? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate responsibilities. Thus we need to compile a unique set of responsibilities. Let's list unique responsibilities from the first block and second block, removing duplicates. First block items (I'll number): 1. Translating strategic priorities into executable work plans – supporting Lighthouse and Security Sales Motions 2. Helping maintain dashboards and status reporting. 3. Focusing on sales and practice defined priorities 4. Directing and work with strategic design partners and product marketing execution resources. 5. Forecasting work efforts on assignments for accurate reporting on project delivery. 6. Reviewing work for quality and alignment with Product Marketing objectives. 7. Delivering value propositions, messaging frameworks, solution briefs, sales kits, executive presentations, sales enablement assets, marketing collateral, and AI marketing deliverables. 8. Partnering with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders 9. Developing repeatable workflows, dashboards, governance, and process improvements. Second block items (after "Key areas of focus"): - Translating strategic priorities into executable work plans – supporting Lighthouse and Security Sales Motions (duplicate of 1) - Help maintain dashboards and status reporting. (duplicate of 2) - Focus on sales and practice defined priorities (duplicate of 3) - Project orchestration with design team in India to translate messaging into customer facing materials (new) - Cross functional collaboration with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders (similar to 8 but slightly different wording) - Deliver value propositions, messaging frameworks, solution briefs, sales kits, executive presentations, sales enablement assets, marketing collateral, and AI marketing deliverables. (duplicate of 7) - Develop repeatable workflows, dashboards, governance, and process improvements with program managers. (similar to 9 but adds "with program managers") Thus new unique items: - Project orchestration with design team in India to translate messaging into customer facing materials - Cross functional collaboration with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders (maybe we keep as is; it's similar to 8 but we can keep both? 8 says "Partnering with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders". Slight difference: "Partnering" vs "Cross functional collaboration". Both are substantive; we could keep both as they are not exact duplicates. But they convey similar idea. The instruction says remove duplicated lines; these are not exact duplicates, so keep both. - Develop repeatable workflows, dashboards, governance, and process improvements with program managers. (similar to 9 but adds "with program managers". Keep.) Thus responsibilities list will include all unique items. Now Requirements / Qualifications / Skills: The posting has "Required Skills" bullet list: - Bachelor's Degree or equivalent experience and / or military experience - Overall 10+ years of experience in B2B or Technology Product Marketing - 10-12 years of Product Marketing experience in enterprise technology. - Experience managing agencies, contractors, and cross-functional initiatives. - Excellent executive communication and presentation skills. - Experience with AI, cloud, infrastructure, cybersecurity, or managed services preferred. We need to decide which headings to use: Requirements, Qualifications, Skills. The instruction says use headings for those if content exists. We have content that could be split: maybe "Requirements" for education and years experience, "Qualifications" for managing agencies etc, "Skills" for communication and AI experience. But we could also just put all under "Skills" or "Requirements". However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we should combine into maybe one section "Requirements" or "Skills". Which heading is appropriate? The posting says "Required Skills". So we could use

Skills

and list items. Or we could use

Requirements

. Since they used "Required Skills", I'd use Skills. We also have "Your future at Presidio" and "About Presidio" which are descriptive about company; could be placed under "About the role"? But "About the role" is supposed to describe the role. The intro about Presidio could be considered "About the role"? Not exactly. However we have no specific heading for company info; we could omit as not required. The instruction: include a section ONLY when the posting has real, specific content for it. We have content for About the role (the role description). We have Responsibilities. We have Skills. We do not have explicit Benefits, Pay, Schedule. So we omit those. Thus output:

About the role

The Senior Product Manager serves as leader within the Product Marketing organization, partnering with the Director of Product Marketing to lead strategic initiatives, help direct supplemental resources, and accelerate delivery of high-impact marketing messages, collateral and customer-facing materials.

Responsibilities

• Translating strategic priorities into executable work plans – supporting Lighthouse and Security Sales Motions
• Helping maintain dashboards and status reporting.
• Focusing on sales and practice defined priorities
• Directing and work with strategic design partners and product marketing execution resources.
• Forecasting work efforts on assignments for accurate reporting on project delivery.
• Reviewing work for quality and alignment with Product Marketing objectives.
• Delivering value propositions, messaging frameworks, solution briefs, sales kits, executive presentations, sales enablement assets, marketing collateral, and AI marketing deliverables.
• Partnering with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders
• Developing repeatable workflows, dashboards, governance, and process improvements.
• Project orchestration with design team in India to translate messaging into customer facing materials
• Cross functional collaboration with Product Management, Sales, Solution Architects, SMEs, Creative Services, and executive stakeholders
• Develop repeatable workflows, dashboards, governance, and process improvements with program managers.

Skills

• Bachelor's Degree or equivalent experience and / or military experience
• Overall 10+ years of experience in B2B or Technology Product Marketing
• 10-12 years of Product Marketing experience in enterprise technology.
• Experience managing agencies, contractors, and cross-functional initiatives.
• Excellent executive communication and presentation skills.
• Experience with AI, cloud, infrastructure, cybersecurity, or managed services preferred.

We should ensure no extra whitespace issues. Output only HTML fragment. Check for any duplicated lines: we have "Develop repeatable workflows, dashboards, governance, and process improvements." and "Develop repeatable workflows, dashboards, governance, and process improvements with program managers." They are not exact duplicates; keep both. Check for any boilerplate: we removed EEO etc. Check for any mention of "Your future at Presidio" and "About Presidio": we omitted; is that substantive? It's about company culture; but we have no heading for company info. Could we put under "About the role"? Might be considered filler but it's substantive. However the instruction: "include a section ONLY when the posting has real, specific content for it". We have content but no appropriate heading; we could add a section "About Presidio" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading. So we must either incorporate that content into About the role or drop it. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Dropping company description would lose substantive info. But we could incorporate it into About the role section, expanding it. That would preserve info while using allowed heading. So we should merge "Your future at Presidio" and "About Presidio" into About the role paragraph. Thus About the role paragraph should include the role description plus company description. Let's extract those paragraphs: "The Role The Senior Product Manager serves as leader within the Product Marketing organization, partnering with the Director of Product Marketing to lead strategic initiatives, help direct supplemental resources, and accelerate delivery of high-impact marketing messages, collateral and customer-facing materials." "Your future at Presidio Joining Presidio means stepping into a culture of trailblazers - thinkers, builders