Principal Campaign Manager

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes "About The Role" (which is about role description). Also "What You'll Do" (responsibilities). Also "Required Qualifications" and "Preferred Qualifications". Also "Compensation" (Pay). Also "Benefits". Also "What Makes Cloudflare Special?" maybe not a standard heading; but we could treat as maybe not needed. The instructions: Use headings for those specific labels; we should map content accordingly. We need to avoid repeating job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. So we need to strip out the "About Us" section? It's not a required heading; but we could include as maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." We can include sections: About the role (maybe combine About Us? Actually "About The Role" is a heading in posting). We'll output

About the role

then a

with the paragraph(s) describing the role. Then Responsibilities: from "What You'll Do" bullet points (though they are not bullet list but sentences). We'll convert to

• items. Then Requirements: maybe combine Required Qualifications and Preferred Qualifications? Could have separate sections: Requirements (maybe required) and Qualifications (maybe preferred). But we have both Required Qualifications and Preferred Qualifications. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put Required Qualifications under

  Requirements

  and Preferred Qualifications under

  Qualifications

  . Skills maybe not explicitly listed; we could omit if no specific skills list. Benefits: we have Benefits section. Pay: we have Compensation section. Schedule: not mentioned, so omit. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We must remove boilerplate like EEO etc. Also remove "Available Locations:" maybe we could keep as part of About the role? It's location info; but not under any heading. Could be placed in a short

  maybe under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So location is minor metadata; we could include a short

  after About the role maybe. We need to output only HTML fragment, no markdown fences. Let's extract content. About Us: we may drop as not needed; but could be considered "About the role"? Actually "About Us" is company overview; not required heading. Could drop. About The Role: text: "Cloudflare’s global campaigns team is seeking a highly motivated Principal Campaign Manager to join and drive end-to-end campaign strategy for one of Cloudflare's core solutions. In this pivotal role, you'll own the complete campaign lifecycle—from strategy and content development to launch, optimization, and measurement—driving awareness, engagement, and, ultimately, pipeline growth. In this role, you'll partner with regional teams across the world to identify market-specific challenges and opportunities, then craft campaign strategies that deliver pipeline on a global scale." We'll put that in a

  . What You'll Do: list of bullet-like sentences: - Own Campaign Strategy & Execution Lead the complete campaign lifecycle for a core Cloudflare solution, from initial planning through launch, measurement, and continuous optimization Define campaign narrative, target audiences, and success metrics - Drive Cross-Functional Collaboration Partner closely with Product Marketing, Regional Marketing, Brand and Digital Marketing teams Identify key customer business challenges and translate them into compelling campaign messages across the entire funnel Build strong relationships and influence stakeholders across the organization - Create & Manage Campaign Artifacts Develop and oversee creation of campaign content working with both internal teams and external resources Write compelling campaign copy while leveraging existing messaging frameworks and positioning documents Ensure content consistency and quality across all campaign touchpoints - Execute Multi-Channel Campaigns Launch and manage campaigns across content syndication, paid digital, email, direct mail, webinar, and sales and BDR channels Continuously monitor performance metrics and optimize campaigns for maximum impact and ROI - Deliver Data-Driven Insights Track key performance indicators (KPIs) for all campaigns Analyze campaign data to identify trends, opportunities, and areas for improvement Provide regular, actionable insights and recommendations to leadership and stakeholders We need to convert to

  • . Each top-level bullet could be a
  • containing maybe multiple sentences; we could keep as is. We'll produce something like:
    • Own Campaign Strategy & Execution – Lead the complete campaign lifecycle for a core Cloudflare solution, from initial planning through launch, measurement, and continuous optimization; Define campaign narrative, target audiences, and success metrics.
    • Drive Cross-Functional Collaboration – Partner closely with Product Marketing, Regional Marketing, Brand and Digital Marketing teams; Identify key customer business challenges and translate them into compelling campaign messages across the entire funnel; Build strong relationships and influence stakeholders across the organization.
    • Create & Manage Campaign Artifacts – Develop and oversee creation of campaign content working with both internal teams and external resources; Write compelling campaign copy while leveraging existing messaging frameworks and positioning documents; Ensure content consistency and quality across all campaign touchpoints.
    • Execute Multi-Channel Campaigns – Launch and manage campaigns across content syndication, paid digital, email, direct mail, webinar, and sales and BDR channels; Continuously monitor performance metrics and optimize campaigns for maximum impact and ROI.
    • Deliver Data-Driven Insights – Track key performance indicators (KPIs) for all campaigns; Analyze campaign data to identify trends, opportunities, and areas for improvement; Provide regular, actionable insights and recommendations to leadership and stakeholders.
    Now Required Qualifications: list: - 7-10 years of B2B marketing experience in Demand Generation, Field Marketing, Product Marketing, Account-Based Marketing, or Customer Marketing - Proven track record of successful end-to-end campaign management and optimization - Strong problem-solving abilities with experience finding creative solutions within operational constraints - Experience working with AI tools (OpenCode, Claude, Gemini) - Excellent communication and cross-functional collaboration skills, with demonstrated ability to build trust and influence stakeholders - Natural curiosity about people, products, processes, and technologies, with the ability to ask insightful questions to uncover key insights - Data-driven mindset with experience interpreting information to make smart business decisions - Hands-on experience with marketing technologies including Salesforce, Marketo, Demandbase, PFL, Goldcast, and Tableau - Bias for action and willingness to experiment with new approaches, tactics, and channels We'll put in
    . Preferred Qualifications: - Experience marketing for cloud services providers or cybersecurity companies (especially SASE / Zero Trust technologies) - Background marketing to IT, security, or other technical buyer personas - Experience designing and executing account-based marketing (ABM) programs and campaigns - Experience driving competitive and vertical marketing initiatives Now Compensation: details: "Compensation may be adjusted depending on work location. For San Francisco Bay Area based hires: Estimated annual salary of $164,000 - $226,000. For Seattle and New York City based hires: Estimated annual salary of $156,000 - $215,000. For Chicago based hires: Estimated annual salary of $139,000 - $191,000." Also "Equity This role is eligible to participate in Cloudflare’s equity plan." That's also compensation-related; we could include under Pay. We'll put under

    Pay

    a

    with that info. Benefits: The benefits section includes a paragraph and list of benefits. We need to preserve all substantive information. The benefits description: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S." Then list: Health & Welfare Benefits Medical/Rx Insurance Dental Insurance Vision Insurance Flexible Spending Accounts Commuter Spending Accounts Fertility & Family Forming Benefits On-demand mental health support and Employee Assistance Program Global Travel Medical Insurance Financial Benefits Short and Long Term Disability Insurance Life & Accident Insurance 401(k) Retirement Savings Plan Employee Stock Participation Plan Time Off Flexible paid time off covering vacation and sick leave Leave programs, including parental, pregnancy health, medical, and bereavement leave We'll put under

    Benefits

    a
    with items. We might also include the introductory paragraph as a

    before the list. Now "What Makes Cloudflare Special?" maybe not needed; but could be considered as extra; but not a standard heading; we could drop or include as a

    under maybe not heading. The instruction: Prefer few substantive sections; we could drop this as not required heading. It's not boilerplate but could be considered fluff; but we might keep as a

    under maybe not heading; but we have no heading for it; we could just include as a

    after Benefits? But that would be stray content not under a heading; maybe better to drop as not needed. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we drop that section, we lose substantive info about Cloudflare's special projects. That is substantive. So we need to include it somewhere. Since we don't have a heading for it, we could incorporate it under a generic

    maybe after Benefits, but not under a heading. The instruction says use headings for those specific labels; but doesn't forbid other headings? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also have other headings? Probably safer to stick to those headings only. However we need to preserve the info; we could embed it as a

    under Benefits or under About the role? Might be okay to add a

    after Benefits without a heading; but that might be considered stray content. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we cannot have stray

    not under heading. But earlier: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections; but not that we cannot have other elements. I'd include the special info as a

    after Benefits, maybe with a heading like "About Cloudflare" but that's not in list. Could we treat "What Makes Cloudflare Special?" as a heading? Not in the list but maybe acceptable as a section heading? The examples are not exhaustive; they say e.g. So we could add a heading for that. But safer to follow the instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. I'd add a heading

    What Makes Cloudflare Special?

    and then a

    with the description. That seems reasonable. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-op