Senior Customer Engineer

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 as heading. We must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Preserve all substantive info. We need to parse the posting. First part: "About Us At Cloudflare, we are on a mission..." That's about company, not needed? The instruction: we should include sections only when posting has real specific content. The "About Us" could be considered "About the role"? Actually there is a section "About The Role". The "About Us" is generic company description; we could maybe include as part of "About the role"? But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have "About The Role" heading in the posting. So we can output

About the role

with the paragraph(s) under it. Then "What you’ll do as a Senior Customer Engineer SLED" then "Key Responsibilities". So we can have

Responsibilities

with list. Then "Minimum Qualifications" and "Strongly Preferred Qualifications (The "Good-to-Haves")". Those could be combined into Requirements and Qualifications? The instruction: Use headings Requirements, Qualifications, Skills. We need to decide mapping. "Minimum Qualifications" likely correspond to Requirements. "Strongly Preferred Qualifications" could be Qualifications or Skills. Also there is a list of technical acumen etc. Could be Skills. We need to preserve all substantive info. So we need to extract bullet points. Let's extract content. From posting: About Us: (maybe ignore as not needed for role). But could be part of "About the role"? The "About The Role" section repeats some of that but we can use that. About The Role paragraph: "At Cloudflare, we are on a mission to help build a better Internet. As the architectural complexity of enterprise solutions scales, we are evolving how we partner with our customers. The Customer Engineer (CE) represents the core driver of our technical go-to-market strategy: a trusted advisor who owns the technical relationship from the initial discovery phase through to long-term adoption and ongoing account expansion. Sitting within the GTM organization and reporting to the Regional Customer Engineering Leader, this specialized role will focus heavily on our SLED (State, Local, and Education) and Local Government sectors. You will not hand off your customers once an initial agreement is reached. Instead, you will operate as a quota-carrying technologist, utilizing AI-augmented workflows to eliminate administrative toil so you can focus on high-value architectural design and driving measurable business outcomes across the entire public sector customer journey." That's the content for About the role. Now Responsibilities: Under "Key Responsibilities" there are bullet-like paragraphs each starting with a bold heading? Actually they are: Technical Validation: Partner closely with Account Executives to lead technical discovery, build bespoke architectures, and deliver compelling product demonstrations and Proof of Concepts (PoCs) across Cloudflare’s portfolio (Security, Networking, and Developer Platforms) tailored to public sector procurement and compliance standards. Customer Adoption & Value Realization: Lead and/or provide oversight to technical onboarding and implementation, serving as the primary executive and engineering contact for the customer. You will partner with Account Executives to own discovery, demos, onboarding, technical health, risk, and expansion strategy. You will proactively monitor dynamic customer health scores and telemetry to ensure rapid time-to-value and resolve integration bottlenecks common in municipal and educational IT infrastructures. Commercial Accountability & Expansion: Carry a variable quota tied directly to new business acquisition and/or ongoing account growth. You will be commercially accountable for ensuring deep platform adoption, retaining revenue, and identifying strategic cross-sell and up-sell opportunities based on product usage data. Lead technical Quarterly Business Reviews (QBRs) to translate platform capabilities into return on investment for C-level executives. Trusted Advisory: Act as a trusted technical advisor throughout the entire customer lifecycle, maintaining a continuous, deep relationship with key stakeholders from initial onboarding through maturity, renewal, and expansion. AI Orchestration & Workflow Automation: Act as an "AI-Augmented" engineer. Leverage AI agents and internal platforms to automate routine tasks such as RFP/Security Questionnaire responses, sandbox provisioning, and basic telemetry monitoring, reclaiming your time for strategic customer advisory. We need to output as

• each item. Probably each bullet as a list item containing the full sentence(s). We'll keep the bold headings inside li? Could keep as part of text. Now Minimum Qualifications: "Public Sector Expertise: Proven experience working with or selling into SLED, Local Government, or Municipal agencies, with a deep understanding of public sector buying cycles, compliance requirements, and unique government IT constraints. Experience: Experience in a customer-facing technical role, such as Solutions Engineering, Customer Engineering, Sales Engineering, or as a Forward Deployed Engineer (years of experience required will vary based on Associate, Senior, Staff, or Principal leveling). Technical Acumen: Broad technical expertise spanning web security, networking (routing, DNS, DDoS mitigation), cloud infrastructure, and enterprise architecture. Commercial Mindset: Proven track record of operating in a quota-carrying or revenue-aligned environment, with a strong understanding of SaaS metrics, business value translation, and public sector/enterprise sales cycles. Communication: Exceptional presentation and stakeholder management skills, capable of bridging the gap between deep technical implementation details and high-level government C-suite/elected official business strategy." These could be under Requirements heading. Now Strongly Preferred Qualifications (The "Good-to-Haves"): "Cloudflare AI Stack Experience: Hands-on experience building, deploying, or architecting solutions using Cloudflare's developer platform and AI ecosystem, specifically Workers AI, AI Gateway, and Vectorize. Applied AI Knowledge: Experience with prompt engineering, Large Language Model (LLM) orchestration, or Retrieval-Augmented Generation (RAG) architectures. Coding/Scripting: Proficiency in Python, JavaScript, or similar languages to write custom integration scripts, API connectors, and edge computing functions." These could be under Qualifications or Skills. Since we have both Qualifications and Skills headings available, we could put these under Qualifications (preferred) and maybe Skills under something else? But we also have Technical Acumen etc which could be Skills. However we already used Technical Acumen under Minimum Qualifications. Might be better to map: - Requirements: Minimum Qualifications (the required ones) - Qualifications: Strongly Preferred Qualifications (good-to-haves) - Skills: maybe we could extract from Technical Acumen etc but that's already in Requirements. Could also list skills like "web security, networking, cloud infrastructure, enterprise architecture, SaaS metrics, presentation, stakeholder management". But to avoid duplication, we could keep Skills empty? But we must not emit a heading with filler. So we should only include Skills if there is real specific content not already covered. Perhaps we can treat the "Technical Acumen" etc as Skills. But then Requirements would be something else like "Public Sector Expertise, Experience, Commercial Mindset, Communication". However the instruction says preserve ALL substantive information; we cannot drop any. So we need to include all info somewhere. We could create three sections: Requirements (Public Sector Expertise, Experience, Commercial Mindset, Communication), Qualifications (Technical Acumen, Cloudflare AI Stack Experience, Applied AI Knowledge, Coding/Scripting), Skills (maybe empty?). But we need to ensure we don't lose Technical Acumen. Let's think. Better: Use Requirements for the list of Minimum Qualifications (all five items). Use Qualifications for the Strongly Preferred Qualifications (three items). Use Skills for maybe a summary of technical skills like "web security, networking (routing, DNS, DDoS mitigation), cloud infrastructure, enterprise architecture, SaaS metrics, business value translation, presentation, stakeholder management, prompt engineering, LLM orchestration, RAG, Python, JavaScript". But that would be duplicating content from both sections. However the instruction says preserve ALL substantive information; duplication is allowed? It says do NOT invent or summarize away detail. Duplication might be okay but better to avoid redundancy. However we could keep them as is and not create Skills section if no unique content left. But we have to decide. Let's see if there is any other content for Benefits, Pay, Schedule. Benefits: There's a section "Benefits Cloudflare offers a complete package..." with list of benefits: 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). Also there is a paragraph about benefits may vary outside US. Thus we have specific benefits content. So we should include Benefits section with list. Pay: There's a "Compensation" subsection: "Compensation may be adjusted depending on work location. For San Francisco based hires: Estimated annual salary of $231,000-$275,000+ OTE, Base + Commissions Los Angeles based hires: Estimated annual salary of $221,000 - $267,000 OTE, Base + Commissions." Also mentions equity: "This role is eligible to participate in Cloudflare’s equity plan." So we have pay info. Should include Pay section. Schedule: There's mention: "Available Locations: Seattle OR PAC NW This is a work-from-home 100% remote role, but you should reside in one of the regions." That's about location and remote work. Not exactly schedule (like full-time, hours). There's no explicit schedule like "Full-time", "40 hours/week". So we should not create Schedule section because no specific schedule content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we skip Schedule. Now we need to output HTML fragment with headings and content. We must not include navigation, legal, EEO, etc. So we must cut out the "What Makes Cloudflare Special?" section, the equal opportunity employer text, etc. Also remove the "Please note that applicants..." etc. Also remove the "Available Locations:" line? That's location info; maybe we could include under Pay? Not needed. But location is not part of headings; we could 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 the location line or incorporate into a short p maybe under About the role? But it's not about role. Could drop. Also drop the "We’re not just a highly ambitious..." etc (What Makes Cloudflare Special). That's boilerplate? It's about company culture but maybe considered substantive? It's not under the defined headings; we could drop as it's not required. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What Makes Cloudflare Special?" is not exactly boilerplate but could be considered marketing fluff. However it's substantive about company mission. But we already have About the role covering mission. Might be duplicate. Safer to drop. Also drop the "Please note that applicants who progress..." etc (application instructions). Drop. Also drop the export control notice, EEO statement, accommodation request, etc. Now we need to format. We'll produce:

  About the role

  At Cloudflare, we are on a