Principal Campaign Manager

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Do"), Requirements (Qualifications), Skills? The posting includes "Required Qualifications" and "Preferred Qualifications". Also "Compensation", "Benefits", "What Makes Cloudflare Special?" maybe not needed but could be a section? The instruction: include a section ONLY when posting has real, specific content for it. We have content for About the role (the paragraph after "About The Role"). Responsibilities: "What You'll Do" list. Requirements: "Required Qualifications" list. Skills: maybe not separate; but we could embed within qualifications. Benefits: there is a Benefits section with details. Compensation: there is Compensation section with salary ranges. Schedule: not mentioned. Pay: we have compensation. So we can include sections: About the role, Responsibilities, Requirements, Benefits, Compensation. Also maybe "About Us" is not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says e.g., but we can use those. We'll include About the role, Responsibilities, Requirements, Benefits, Compensation. For Requirements we could combine Required and Preferred? Could separate but better to have one Requirements section with both required and preferred? The instruction: prefer a few substantive sections over many thin ones. So we can have Requirements covering both required and preferred qualifications. Benefits section with list. Compensation section with salary ranges. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, etc. Also remove "Available Locations:" maybe we could keep as a short paragraph? It's metadata; we could fold into a short

or drop it. Probably drop it as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop Available Locations. We need to preserve all substantive information. So we need to keep the description of About Us? That's not required as a heading; we could include as a short paragraph before sections? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having a preamble paragraph. But we should include the About Us content? It's substantive but not under a heading. Could be a

before sections. However the instruction about sections: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other content. So we can include a brief intro paragraph about About Us (maybe as

). But we need to preserve ALL substantive information; we should not drop the About Us description. So include it as a paragraph before sections. Similarly "What Makes Cloudflare Special?" is substantive; we could include as a section maybe "What Makes Cloudflare Special?" but not in the list of headings; but we could still include as

maybe? 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 we should follow the pattern. Safer to include it as a

or maybe as a section "What Makes Cloudflare Special?" but that's not in the list; but it's okay to add? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could still use other headings but better to stick to those. However "What Makes Cloudflare Special?" is substantive; we could incorporate into a

after benefits. We must not include boilerplate like EEO, equal-opportunity, scam-warning, etc. Also remove duplicated lines, application instructions. At the end there is a paragraph about in-person interview, export control, EEO, etc. Remove those. Now craft HTML. We'll start with a

for About Us description (the first paragraph up to "Available Locations:" maybe we drop that line). Actually About Us includes multiple paragraphs. We'll keep all that text except the "Available Locations:" line. Let's extract About Us text: "At Cloudflare, we are on a mission to help build a better Internet. Today the company runs one of the world’s largest networks that powers millions of websites and other Internet properties for customers ranging from individual bloggers to SMBs to Fortune 500 companies. Cloudflare protects and accelerates any Internet application online without adding hardware, installing software, or changing a line of code. Internet properties powered by Cloudflare all have web traffic routed through its intelligent global network, which gets smarter with every request. As a result, they see significant improvement in performance and a decrease in spam and other attacks. Cloudflare was named to Entrepreneur Magazine’s Top Company Cultures list and ranked among the World’s Most Innovative Companies by Fast Company. At Cloudflare, we’re not looking for people who wait for a polished roadmap; we’re looking for the builders who see the cracks in the Internet that everyone else has simply learned to live with. We value candidates who have the instinct to spot a "normalized" problem and the AI-native curiosity to create a solution using the latest tools. Our culture is built on iteration, leveraging AI to ship faster today to make it better tomorrow, while ensuring that every improvement, no matter how small, is shared across the team to lift everyone up. If you’re the type of person who values curiosity over bureaucracy, and that AI is a partner in solving tough problems to keep the Internet moving forward, you’ll fit right in." Then "Available Locations: San Francisco, New York, Seattle, Austin, Chicago" we drop. Now after that we have "About The Role" heading; we will make

About the role

then paragraph(s) describing role. The role description: "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

. Next "What You'll Do" is responsibilities. We'll make

Responsibilities

then a

with each bullet. List items: - 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 keep the content exactly; we can split into separate
• for each major bullet (the bold headings). The original had headings then sentences. We'll keep each heading as part of the
• text. Now "Required Qualifications" and "Preferred Qualifications". We'll combine into

  Requirements

  then a
  with required and preferred maybe separate subheadings? But we can just list all items. However we need to preserve distinction? Not required but we could keep as separate
  • with label. We'll list required qualifications items: - 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 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 We'll put them all in one list; maybe we can add a note but not needed. Now Benefits:

    Benefits

    then
    with items: - 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 - Short and Long Term Disability Insurance - Life & Accident Insurance - 401(k) Retirement Savings Plan - Employee Stock Participation Plan - Flexible paid time off covering vacation and sick leave - Leave programs, including parental, pregnancy health, medical, and bereavement leave We could also include the descriptive sentence: "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." We could include that as a

    before the list. Now Compensation:

    Compensation

    then

    with salary ranges per location. We need to preserve the text: "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 mention equity: "This role is eligible to participate in Cloudflare’s equity plan." Could include that as part of compensation. We'll put that in a

    . Now we should not include schedule or pay separate. Now ensure we removed boilerplate: EEO, equal opportunity, etc. Also removed "Please note that applicants who progress to the offer stage..." etc. Also removed "More details about this will be available at that stage of the interview process." etc. Also removed "This position may require access to information protected under U.S. export control laws..." etc. Also removed "Cloudflare is proud to be an equal opportunity employer..." etc. Also removed "We are an AA/Veterans/Disabled Employer." etc. Also removed