Named Sales Director, East

We need to output HTML fragment with sections: About the role, Responsibilities, Desirable Skills, Knowledge, And Experience (maybe "Qualifications" or "Skills"), Compensation, Equity, Benefits, What Makes Cloudflare Special? Possibly also "About Us"? The instruction: 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. We need to include sections only when posting has real, specific content. So we need to parse the posting. Let's extract content: - About Us: description of Cloudflare mission, etc. This is substantive. Should we include as a section? The allowed headings list includes "About the role" but not "About Us". However we could still include a heading? 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 suggests those are typical. Probably we should include "About Us" as a section? The instruction: "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 can also have other headings if needed? Safer to stick to those headings. However "About Us" is not listed; maybe we can treat it as "About the role"? No, that's different. The posting includes "About Us" separate from "About The Role". We could include "About Us" as a

without heading? But we need to preserve all substantive info. Could embed it as a

before the role section. The instruction: "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." It doesn't forbid other headings. I'd include "About Us" as an

maybe? But the examples list only certain headings; but they say "e.g." meaning examples. So we can use other headings as needed. I'll include "About Us" as

. Then "About The Role": we have a paragraph. We'll put that under

About The Role

with

. Responsibilities: list of bullet points. We'll put

Responsibilities

then

• each. Desirable Skills, Knowledge, And Experience: list of bullet points. Could be under

  Qualifications

  or

  Skills

  . The heading list includes Skills, Qualifications. We'll use

  Qualifications

  maybe. But the content is "Desirable Skills, Knowledge, And Experience". We'll put under

  Qualifications

  and list items. Compensation: we have details: "Compensation will be adjusted based on location and level.For Washington DC Area based hires: Estimated On Target Earnings of $415,000 - 571,000 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." We'll put under

  Compensation

  with

  . Equity: "This role is eligible to participate in Cloudflare’s equity plan." We'll put under

  Equity

  with

  . Benefits: long list. We'll put under

  Benefits

  with
  • each benefit item. What Makes Cloudflare Special?: includes paragraphs and bullet-like list (though not bullet). We'll put under

    What Makes Cloudflare Special?

    with

    paragraphs and maybe

    for the sub-items (Project Galileo, Athenian Project, 1.1.1.1). The posting includes those as separate paragraphs with bold headings. We'll preserve as

    with maybe? But we should not invent tags beyond needed. We can keep as

    with the text. We need to remove boilerplate: EEO, equal opportunity, accommodation request, etc. Also remove "Please note that applicants who progress to the offer stage..." etc. Also remove "This position may require access to information protected under U.S. export control laws..." etc. Also remove "Cloudflare is proud to be an equal opportunity employer..." etc. Also remove "We are an AA/Veterans/Disabled Employer." etc. Also remove accommodation request details. Also remove "More details about this will be available at that stage of the interview process." etc. Also remove "Please note that any offer of employment may be conditioned..." etc. Also remove "Cloudflare provides reasonable accommodations..." etc. Also remove the email and mail address. Also remove duplicated lines? Not seeing duplicates. We need to preserve all substantive information: that includes the "Available Locations Washington DC, Raleigh, NC or Charlotte, NC". That's minor metadata; we can fold into a short

    maybe under About Us or About The Role. We'll include a short

    after About Us maybe. Also "About Us" includes location? Actually location appears after About Us paragraph: "Available Locations Washington DC, Raleigh, NC or Charlotte, NC". We'll include that as a

    . Now let's craft HTML. We'll start with

    About Us

    then

    ... mission description.

    then

    Available Locations: Washington DC, Raleigh, NC or Charlotte, NC

    maybe. Then

    About The Role

    ... paragraph.

    Then

    Responsibilities

    each bullet. We need to split responsibilities bullet points: The posting has a long paragraph with periods separating responsibilities but no bullet markers. We need to turn each sentence into
    • . Let's extract: - Accurately forecast commits by month and quarter, leveraging automated internal data layers and predictive metrics to consistently deliver attainment to quarterly and annual sales targets. - Oversee, coach, and motivate a team of 8 Account Executives, measuring success against overall quota attainment, new logo acquisition, and expansion tactics. - Develop and uplevel team selling abilities through consistent focus on enablement, solution selling, and interpreting automated, data-led customer insights. - Assist in the continued codification and execution of product-focused playbooks to connect platform data to Cloudflare solutions that solve critical business challenges. - Collaborate with Sales Enablement, Product, and Product Marketing to optimize sales training and accelerate execution around newly launched features and products. - Maintain a robust funnel of new hire candidates by continuously interviewing and building a strong network of potential talent. - Hold regular 1x1s with team members, maintaining open and transparent communication while monitoring the proficiency and adoption of sales enablement tooling and resources. We'll make each
    • . Now Desirable Skills, Knowledge, And Experience bullet list: - 5+ years of Sales Management experience leading high-performing sales teams at a high-growth SaaS company. - Proven record of high performance in consistently meeting and exceeding team plan through strategic acquisition and expansion tactics. - Experience developing relationships with highly technical customers and selling through modern, data-driven Product-Led Growth (PLG) models. - Coaching-level knowledge of Gap Selling, Sandler, Challenger, or other structured sales methodologies. - Strong talent for multi-threading across business units to identify, engage, and close new divisional buyers, as well as driving consensus among internal and external stakeholders. - Excellent written communication, presentation, and pipeline management skills. - Bonus Points - Experience leading sales teams specifically within Cloud Security or Hyperscaler ecosystems. - Experience navigating complex accounts undergoing Mergers & Acquisitions (M&A) to expand the partner ecosystem. We need to treat "Bonus Points" as maybe a heading? But we can keep as
    • with sub-items? Could make a
    • "Bonus Points" then nested
      . Simpler: keep as
      • "Bonus Points: Experience leading sales teams specifically within Cloud Security or Hyperscaler ecosystems; Experience navigating complex accounts undergoing Mergers & Acquisitions (M&A) to expand the partner ecosystem." But better to keep separate bullet points. We'll make two
      • under a subheading? The instruction: Use
        • for any list of duties/requirements/benefits. So we can have a list; "Bonus Points" could be a
        • with its own content. We'll just treat each bullet as separate
        • . So we will have: - 5+ years of Sales Management experience leading high-performing sales teams at a high-growth SaaS company. - Proven record of high performance in consistently meeting and exceeding team plan through strategic acquisition and expansion tactics. - Experience developing relationships with highly technical customers and selling through modern, data-driven Product-Led Growth (PLG) models. - Coaching-level knowledge of Gap Selling, Sandler, Challenger, or other structured sales methodologies. - Strong talent for multi-threading across business units to identify, engage, and close new divisional buyers, as well as driving consensus among internal and external stakeholders. - Excellent written communication, presentation, and pipeline management skills. - Experience leading sales teams specifically within Cloud Security or Hyperscaler ecosystems. - Experience navigating complex accounts undergoing Mergers & Acquisitions (M&A) to expand the partner ecosystem. We'll drop the "Bonus Points" label but keep the content. Now Compensation:

          Compensation

          Compensation will be adjusted based on location and level. For Washington DC Area based hires: Estimated On Target Earnings of $415,000 - $571,000. 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.

          Equity:

          Equity

          This role is eligible to participate in Cloudflare’s equity plan.

          Benefits: We need to list each benefit item. The posting lists: 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 make a single
          with all items, maybe grouped but not required. We'll just list each as
          • . We'll keep the headings as part of
          • text? Could embed strong. We'll just list each benefit as
          • with the benefit name. Thus:
          • 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 & Acc