Developer GTM Strategy Manager, Technical Programs

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Desirable Skills, Knowledge, And Experience), Benefits, Pay (Compensation), maybe Schedule not present. Also include About Us? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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 include sections that have real content: About The Role, Responsibilities, Desirable Skills, Knowledge, And Experience (could be Requirements or Skills), Compensation (Pay), Benefits. Also maybe "About Us" is not required but could be considered as a section? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but we should follow that pattern. "About Us" maybe not needed; but we could include as a brief paragraph? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Us content somewhere. Could be placed as a

before sections, not as a heading. Since they said 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. So we can include About Us as a

(or maybe as a

About Us? Not in list but could be okay? Safer to not create extra heading not in list. We'll just put About Us as a

before sections. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is a lot of EEO statement, accommodation request, etc. Those should be removed. Also the "Please note that applicants who progress..." etc is application instructions; remove. Also the "Sound like something you’d like to be a part of? We’d love to hear from you!" etc is application instruction; remove. Also the "What Makes Cloudflare Special?" section includes some content about mission etc. That's substantive? It's about company culture; maybe keep as part of About Us? It's not boilerplate; it's describing company's special aspects. Could keep as part of About Us paragraph. We need to preserve all substantive information: So we need to keep the mission description, the culture, the AI-native curiosity, etc. Also the "Available Locations" list: Austin, US New York, US San Francisco, US. That's location info; could be placed as a

maybe. We need to include Compensation section with the salary ranges for Bay Area and NYC. Also mention Equity eligibility. Benefits section: list of benefits as described. We need to format lists with

• . For responsibilities, we have a list of responsibilities (multiple paragraphs). We'll turn each bullet into
• . The responsibilities section includes multiple sentences each starting with a verb. We'll extract each as list item. Similarly for Desirable Skills, Knowledge, And Experience: list of items. For Benefits: list of benefits categories. We need to avoid filler like "Compensation may be adjusted depending on work location." That's substantive; we can keep as a

  inside Pay section. We need to avoid placeholder like "Equity This role is eligible to participate in Cloudflare’s equity plan." That's substantive; we can include as a

  maybe under Pay or separate? The instruction says only create Pay/Schedule/Benefits sections if posting actually states them. It does state compensation and equity and benefits. So we can have Pay section includes compensation and equity. Or we could have separate Equity section but not in list; better to include under Pay. We need to ensure we don't include sections with only filler. All sections we create have content. Now produce HTML fragment. Structure:

  About Us paragraph(s) maybe combine. Then

  About the role

  with paragraph(s) describing role. Then

  Responsibilities

  with
  • ... items. Then

    Requirements

    or

    Desirable Skills, Knowledge, And Experience

    . The instruction list includes Requirements, Qualifications, Skills. We'll use

    Requirements

    (or Skills). Since the content is "Desirable Skills, Knowledge, And Experience". We'll put that under

    Requirements

    . Provide list. Then

    Pay

    with paragraphs: compensation ranges, equity eligibility. Then

    Benefits

    with
    • items. We should not include Schedule. Now need to ensure we removed duplicated lines. The posting had duplicated lines? Not obvious. Now craft content. About Us: combine the mission paragraph, the culture paragraph, the "Available Locations" maybe separate. Let's draft:

      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.

      Available Locations: Austin, US; New York, US; San Francisco, US.

      Now About the role: combine paragraphs. Paragraph: "Cloudflare is looking for a Strategy Manager to join the Developer GTM Strategy & Incubation team, focused on Technical Programs. This person will help Solutions Architects, Forward Deployed Engineers, Professional Services, and Developer GTM leadership identify the right customer opportunities, organize technical GTM work, and turn high-value customer engagement into repeatable programs and operating rhythms. The Developer GTM Strategy & Incubation function exists to evolve the way the Developer GTM team works, designing systems, processes, and GTM motions that accelerate consumption at Cloudflare. This role is focused on the technical side of that motion: where we should spend time, how we coordinate technical resources, how we run customer-facing programs, and how we measure whether technical work is driving the right business outcomes. The right person is a high-agency operator with strong technical fluency. They do not need to be a Solutions Architect, but they should be comfortable working with technical products, customer architectures, implementation workflows, developer platforms, and customer-facing technical teams." Now Responsibilities list items: - Build and scale technical programs: Design proactive programs for Solutions Architects, Forward Deployed Engineers, and related technical GTM teams. Turn ad hoc motions into repeatable playbooks, operating rhythms, and ownership models where it makes sense. - Coordinate strategic customer engagement: Project manage high-priority customer initiatives that require technical GTM support. Clarify goals, stakeholders, timelines, resourcing, risks, success criteria, and follow-up. - Plan and scale technical onsite visits: Build the planning model for strategic customer onsites, including intake, agenda design, staffing, prep, execution, post-onsite follow-up, and measurement. - Improve prioritization and visibility: Own a clear view of active technical engagements, upcoming opportunities, blockers, outcomes, and resourcing needs. Partner with Revenue Engineering, Data, Sales Strategy, and technical leaders on account propensity, engagement tracking, dashboards, and operating reviews. - Support Professional Services packaging and commercialization: Partner with Professional Services, Finance, Product, Sales Strategy, and GTM leaders on pricing, packaging, business cases, rollout plans, and feedback loops for technical services offerings. - Incubate and launch new technical programs: Lead high-priority projects across Developer GTM, support team planning and process improvements, turn technical activity into clear business narratives, and incubate new motions until they are measurable and ready for durable ownership. Examples of projects this person may own: we could include as sub-items? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include the examples as part of responsibilities maybe as separate list items. Could add as separate bullet points under Responsibilities. Examples: - Build a proactive SA/FDE engagement program for a priority customer segment or product motion. - Partner on an account propensity model that helps determine SA/FDE prioritization, resourcing, and account coverage. - Stand up a technical engagement tracker for active customer work, resourcing, blockers, and outcomes. - Design the planning and follow-up model for technical onsite visits with strategic customers. - Partner with Professional Services to package a repeatable services motion and build the business case for rollout. We'll include them as list items. Now Requirements (Desirable Skills, Knowledge, And Experience) list: - 6+ years of experience in GTM strategy, business operations, revenue operations, technical program management, solutions strategy, consulting, or a similar cross-functional execution role. - Experience working with technical customer-facing teams such as Solutions Architects, Sales Engineers, Forward Deployed Engineers, Professional Services, Customer Engineering, Developer Relations, or Product. - Strong technical fluency, including the ability to understand customer architecture discussions, implementation tradeoffs, developer platform concepts, and the operating needs of technical GTM teams. - Strong program management ability, including managing complex work streams, driving accountability without direct authority, and keeping teams aligned under pressure. - Strong sense of ownership; someone who takes initiative, works independently, and manages time effectively. - Excellent cross-functional communication skills and the ability to influence and align stakeholders at all levels. - Highly customer-centric, with natural curiosity about technical products and a strategic mindset for solving complex problems. - Comfortable working under pressure and adjusting priorities to meet deadlines in a fast-moving environment. - Strong analytical skills, including comfort using spreadsheets, CRM data, and business dashboards to prioritize work and inform decisions. - Prior experience with Salesforce CRM, Tableau, BigQuery, or BoostUp is a plus. - Background in SaaS or Product-Led Growth (PLG) is a strong plus. Now Pay section: Paragraph: "Compensation may be adjusted depending on work location. For Bay Area based hires: Estimated annual salary of $161,000 - $221,000. For NYC based hires: Estimated annual salary of $153,000 - $210,000." Then maybe a paragraph: "This role is eligible to participate in Cloudflare’s equity plan." Now Benefits