Customer Solution Strategy Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. We must not include Job ID etc. Remove boilerplate. Use

for headings. Use

• for lists,

  for prose. We need to extract content from posting. Let's parse. The posting includes: - About Us (company description) – but we should not include as a section unless it's "About the role"? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About The Role" heading. So we can have About the role section. Responsibilities: There's "What You'll Do" and "Core Accountabilities" etc. So we can create Responsibilities section. Requirements: There's "The Profile" with Architectural Command etc. Also "Desirable Skills, Knowledge And Experience". Could be Requirements or Qualifications. We need to decide. Qualifications: maybe "The Profile" is qualifications. Skills: "Desirable Skills, Knowledge And Experience". Benefits: there is a Benefits section. Pay: there is Compensation section with salary range for NYC. Schedule: not mentioned. So we should not include Schedule. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details. We need to format as HTML fragment only. Let's extract content. About Us: Not needed as a section? The instruction says use headings for sections like About the role etc. About Us is company overview; maybe we could include as part of About the role? But likely we should not include About Us as separate heading because not in list. 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 says use those for section headings. Probably we should only output those sections if they have content. So we will output About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Not Schedule. Now extract each. About the role: The text under "About The Role" paragraph: "The Pre-Sales Customer Engineering organization owns the technical sale of the Cloudflare solution portfolio, ensuring maximal business value, fit-for-purpose solution design and adoption roadmap for our customers. Customer Engineering is made up of individuals from a wide range of backgrounds - from Financial Consulting to Product Management, Customer Support to Software Engineering, and we are serious about building a diverse, experienced and curious team." That's the content. Responsibilities: Under "What You'll Do" and "Core Accountabilities". Let's gather. What You'll Do paragraph: "As a Solution Strategy Lead Scaling Cloudflare’s most complex and critical accounts requires unparalleled focus. While Client Directors own the commercial relationships and Customer Engineers drive pre-sales, this role serves as the essential strategic link bridging the two. As a dedicated trusted advisor for 1–5 of our highest-value accounts, you will take a deeply consultative approach to map the customer's entire technical ecosystem. You will drive enterprise-wide transformation from initial strategic positioning through the complete customer lifecycle. You are the single thread connecting high-level strategy to flawless execution, orchestrating cross-functional teams to deliver exceptional outcomes. While not a "hands-on-keyboard" engineering role, you possess the technical acumen to proactively steer complex engagements and step in decisively when it matters most." Then "Platform Focus Areas" with sub-bullets: App Modernization Scope, Developer Scope, AI Scope. Each includes description and stakeholders. Those are responsibilities. Then "Core Accountabilities" with bullet list: Platform Adoption Roadmapping, Cross-Functional Coordination, Technical Executive Relationships, Expansion Development, Voice of Customer to Product, Success Metrics (list of metrics), Customer-Facing Positioning. We need to preserve all substantive information. So we need to include these as list items. We can structure Responsibilities as a

  with
  • items covering each bullet. We need to include the Platform Focus Areas as part of responsibilities? Probably yes. Let's extract each bullet. Platform Focus Areas: - App Modernization Scope: Migration from legacy application architectures to Cloudflare's edge platform. Includes moving workloads from on-premise or hyperscale compute to Workers, consolidating storage on R2, and modernizing data layers with D1 and Durable Objects, all while considering security posture. Stakeholders: VP Engineering, Platform Architects, Infrastructure leads, CISO - Developer Scope: Adoption of Cloudflare's developer platform for new application development. Workers, Workers KV, Pages, Queues, Durable Objects, R2, D1. Positioning Cloudflare as the compute and storage layer for net-new projects. Stakeholders: VP Engineering, Developer Experience leads, Platform teams - AI Scope: Adoption of Cloudflare's AI infrastructure for inference and orchestration. Workers AI, Vectorize, AI Gateway. Positioning Cloudflare as the AI inference layer at the edge. Stakeholders: CTO, Head of AI/ML, Data Platform leads Core Accountabilities: - Platform Adoption Roadmapping: Develop account-specific adoption plans across App Modernization, Developer, and AI. Map customer workloads to Cloudflare capabilities. Define sequencing and milestones. - Cross-Functional Coordination: Coordinate SE, CS, and Product resources against adoption milestones. Run account team operating rhythm. Ensure internal alignment on customer priorities. - Technical Executive Relationships: Build relationships with CTOs, VPs of Engineering, and Platform Architects. Engage technical decision-makers on platform strategy. CD retains procurement and CFO relationships. - Expansion Development: Identify and qualify platform expansion opportunities. Hand off to CD when commercial-ready. This individual builds the case; CD closes the deal. - Voice of Customer to Product: Bring strategic customer requirements into Product roadmap discussions. Provide quarterly briefings on adoption patterns, blockers, and feature needs. - Success Metrics: Platform Adoption Products per account: Number of Cloudflare products in production per strategic account; Developer platform adoption: Strategic accounts with Workers, R2, or D1 in production; AI adoption: Strategic accounts with Workers AI or AI Gateway in production; Revenue Influence Expansion pipeline: Dollar value of platform expansion opportunities developed and handed to CD; Net Revenue Retention: NRR on strategic account portfolio (shared metric with CD); Product Feedback Requirements submitted: Strategic customer requirements brought to Product quarterly; Adoption blockers resolved: Product or engineering issues addressed that were blocking adoption. - Customer-Facing Positioning: To customer executives, this role helps them realize value from Cloudflare's entire platform: An expert and trusted advisor; peer to their architects and technical leads; Focused on Platform adoption and business outcomes, not transactions; Turns platform capabilities into production workloads and business value. We need to include all. Now Requirements: The posting has "The Profile" with bullet points: Architectural Command: 10+ years of experience in Customer Engineering Leadership, Product Management, Consulting, or Technical Strategy within a global SaaS or infrastructure environment. Executive Presence: Exceptional communication skills with the ability to influence C-level executives and internal product leads simultaneously. Relentless Curiosity: A natural obsession with "How it works" and "How it could be better." You are driven to discover the architectural truth behind every customer challenge. Bias for Action: You don't just identify problems; you build the "Formation" to solve them. You are comfortable in high-pressure, ambiguous environments. That seems like qualifications. Then "Desirable Skills, Knowledge And Experience": list of items. We could treat "The Profile" as Requirements (or Qualifications). The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. We could put "Requirements" for the mandatory experience (The Profile) and "Qualifications" for desirable skills. Or vice versa. Let's see typical: Requirements often are mandatory; Qualifications often are preferred. The posting has "The Profile" (maybe required) and "Desirable Skills, Knowledge And Experience" (desirable). So we can map The Profile to Requirements, and Desirable Skills to Qualifications. Thus: Requirements (

    Requirements

    ) with list items from The Profile. Qualifications (

    Qualifications

    ) with list items from Desirable Skills. Skills section: maybe we could combine but we already have Qualifications. The instruction includes Skills as a possible heading. Could we also have Skills? Might be redundant. Better to follow instruction: we can include Skills if we have specific skill content not covered elsewhere. But we already have Desirable Skills under Qualifications. Could we instead put Desirable Skills under Skills and keep Qualifications for something else? But we don't have other qualifications. The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid having both Qualifications and Skills if they overlap. We could choose to use Skills for the Desirable Skills list, and Requirements for The Profile. Then we omit Qualifications. Or we could use Qualifications for The Profile and Skills for Desirable Skills. Either is fine. Let's decide: Use Requirements for The Profile (mandatory). Use Skills for Desirable Skills. Omit Qualifications. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Now Benefits: The posting has a Benefits section with sub-bullets: Health & Welfare Benefits (list), Financial Benefits (list), Time Off (list). We need to preserve all substantive information. So we need to list those benefits. We should not include the introductory fluff like "Cloudflare offers a complete package of benefits and programs to support you and your family." but we can keep as prose? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the description but we can condense? It says do not summarize away detail. So we need to keep the detail but we can keep the prose as is. However we can remove boilerplate like "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!" That's maybe not boilerplate but still part of benefits description. It's okay to keep. We need to output as
    • for any list of duties/requirements/benefits. So for Benefits we should output a
      with each benefit item as
      • . The subcategories like Health & Welfare Benefits could be a heading? But we only allowed

        for section headings. Inside a section we can have

        for prose and

        • for lists. We could have a

          describing benefits then a

          for each category? But the instruction: Use
          • for any list of duties/requirements/benefits. So we need to turn each benefit item into a list item. We could have nested lists? Probably okay to have
            • with sub-items as
              • . But we need to preserve all detail. Simplify: We'll create a
                where each top-level
                • is a benefit category with its sub-items as a nested
                  . That preserves detail. Now Pay: The posting has Compensation section: "Compensation may be adjusted depending on work location. This role is eligible to earn incentive compensation under Cloudflare’s Sales Compensation Plan. The estimated annual salary range includes the on-target incentive compensation that may be attained in this role under the Sales Compensation Plan. For New York City based hires: Estimated annual salary of $273,000.00 to $341,000.00". Also "Equity This role is eligible to participate in Cloudflare’s equity plan." That's also compensation/equity. We should include that. We need to output Pay section with that info. Could be a

                  with the details. Now we must not include Schedule. Now we need to ensure we don