Enterprise Sales Director (Ongoing Recruitment)

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Fuel Cycle (company description), Overview, Key Responsibilities, Your Success Metrics, Who you’ll work with?, Core Skills, Competencies & Attributes, What You’ll Bring, Benefits & Perks, Compensation Overview. Also location and work arrangement details. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Commitment To Diversity, Equity, And Equal Opportunity" etc. Also remove "If you require accommodations..." etc. We must preserve all substantive information. So we need to include company description, overview, responsibilities, success metrics, who you'll work with, core skills/competencies/attributes, what you'll bring (qualifications), benefits & perks, compensation overview. Also location and work arrangement maybe as a short paragraph. We must not create sections for Pay/Schedule/Benefits unless posting actually states them. Benefits are stated, so we can have Benefits section. Pay is stated (Compensation Overview) so we can have Pay section (maybe heading "Compensation" or "Pay"? 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 when appropriate. For compensation we can use "Pay". For benefits we use "Benefits". For schedule we only include if posting states schedule; it does: Work Arrangement: onsite role requiring five days per week in the office. So we can include Schedule section. We need to decide which sections to include: About the role? Could be overview. But we have "Overview" section. Could map to "About the role". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings exactly if we have content. For "About the role" we can put the overview paragraph. For "Responsibilities" we list key responsibilities. For "Requirements" maybe we have qualifications (What You'll Bring). For "Skills" we have core skills/competencies/attributes. For "Benefits" we list benefits. For "Pay" we list compensation overview. For "Schedule" we list work arrangement. We must not repeat job title as heading. Also not put Job ID/requisition numbers as headings. We need to preserve all substantive information. Let's extract. Company description: "About Fuel Cycle Fuel Cycle empowers leading organizations with agile research solutions that deliver decision-ready insights — fast, flexible, and fully integrated. As a market research disruptor, our AI-powered Insights Platform is built for speed, precision, and scale. With cutting-edge tools and seamless audience connectivity, we help brands ditch the guesswork and make smarter, customer-led decisions at lightning speed. Why work at Fuel Cycle? Join a high-growth team where curiosity is valued, ownership is encouraged, and your work drives real-world impact. Whether you’re based at our Los Angeles HQ, New York City hub, working remotely across the U.S., or part of our global team in India, you’ll help shape the future of decision intelligence for some of the world’s most iconic brands." Overview: "We are seeking a dynamic and results-driven Enterprise Sales Director to join our high-performing sales team during an exciting period of growth. This role can be based anywhere in the US and involves building a sales pipeline and driving new business revenue across various industries within your regional territory. As an individual contributor, you will lead and manage efforts from lead generation through to sales close. The ideal candidate is a true sales hunter with market research knowledge, a passion for technology, and a proven track record of exceeding revenue goals. Fuel Cycle fosters a customer-obsessed culture, empowering each team member to work passionately and make a significant impact." Location: "Location: Los Angeles, CA Work Arrangement: This is an onsite role requiring five days per week in the office." Key Responsibilities: bullet list under headings: Sales Pipeline Development & Management, Deal Leadership & Conversion, Revenue Growth & Executive Relationships, Cross-Functional Partnership, Strategic Account Penetration. Each has sub-bullets. Your Success Metrics: list of metrics. Who you’ll work with?: list: VP, Customer Experience; Director, Customer Experience; Marketing, Business Development Reps, and Product teams. Core Skills, Competencies & Attributes: sections: Competencies (list), Technical Skills (list), Personal Attributes (list). What You’ll Bring: list: Bachelor’s degree required; 5+ years of experience in technology sales (SaaS and Market Research sales preferred); Prior experience selling Market Research or Consumer Insights tools; Proven track record of excellence with year-over-year quota attainment. Benefits & Perks: list items. Compensation Overview: paragraph about salary range and commission etc. We need to output HTML with

  headings and appropriate

  or

  • . We must not include boilerplate like "Commitment To Diversity..." etc. We need to ensure we don't create empty sections. Let's craft. Structure:

    About the role

    Overview paragraph (maybe combine About Fuel Cycle and Overview? Actually About the role should be overview of role. The company description could be placed before? The instruction says use

    for section headings (e.g. About the role, Responsibilities...). It didn't say we must include company description anywhere. But we need to preserve ALL substantive information. So we need to include company description somewhere. Could be a

    before the first heading? The instruction says output ONLY the HTML fragment — no /. It didn't forbid having a

    before first heading. So we can put a

    with company description, then

    About the role

    with overview paragraph. Alternatively we could treat company description as part of About the role? But the heading "About the role" is for role overview, not company. Safer to put company description as a preceding

    . Let's do:

    About Fuel Cycle ... (the paragraph).

    Then

    About the role

    Overview paragraph.

    Then location and work arrangement maybe as a

    after overview? Could be part of About the role? But we have Schedule section later. So we can put location and work arrangement in Schedule section. Thus after About the role, we have

    Responsibilities

    with
    • ... each responsibility as a list item, with sub-items maybe as nested
      ? The instruction: use
      • for any list of duties/requirements/benefits. It didn't forbid nested lists. We can embed sub-bullets as
        • inside each
        • . That's okay. Similarly for Success Metrics:
          • . Who you’ll work with?: could be a
            • . Core Skills, Competencies & Attributes: we have three subcategories: Competencies, Technical Skills, Personal Attributes. Could be separate headings? But we only have Skills heading allowed. Could combine all under Skills heading with subheadings as or maybe separate

              ? Not allowed? Only

              for section headings. We could keep under Skills heading and separate with

              bold labels. But we need to preserve structure. Perhaps we can make three separate sections: Competencies, Technical Skills, Personal Attributes each as

              ? But the instruction gave examples but not strict; we can use other headings? It says use

              for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should map content to those headings. So we need to fit Competencies, Technical Skills, Personal Attributes under Skills heading. Could do a

              • where each
              • contains a label and then a list. Similarly Requirements/Qualifications: we have What You'll Bring (qualifications). Could map to Requirements or Qualifications. We have both headings allowed. Choose Qualifications for what you bring. Requirements maybe not needed. We'll use Qualifications. Thus sections: - About the role (overview) - Responsibilities - Qualifications (What You'll Bring) - Skills (Core Skills, Competencies & Attributes) - Benefits - Pay - Schedule We also need to include Who you’ll work with? maybe under Responsibilities? Or could be a separate section like "Team" but not in allowed headings. Could incorporate into Responsibilities as a bullet? But it's substantive. Could add a section "About the team"? Not allowed. Maybe we can put it under Responsibilities as a bullet "Collaborate with..." but it's already in Responsibilities under Cross-Functional Partnership includes collaboration with Marketing, Business Development, Product teams. The "Who you’ll work with?" list is more specific: VP, Customer Experience; Director, Customer Experience; Marketing, Business Development Reps, and Product teams. Could be considered part of Responsibilities (Cross-Functional Partnership). We'll incorporate that into the Responsibilities bullet for Cross-Functional Partnership. Thus we may not need separate Who you’ll work with. Success Metrics: we could put under Responsibilities? Or maybe under Requirements? Not exactly. Could be its own section but not in allowed headings. However we could treat it as part of Responsibilities? Might be okay to add a section "Performance Metrics" but not allowed. The instruction says prefer a few substantive sections over many thin ones. So we could incorporate Success Metrics into Responsibilities or Qualifications? Probably better to have a separate section but we need to stick to allowed headings. Could we use "Requirements" for success metrics? Not really. Could we use "Skills"? Not really. Maybe we can add a section "Performance" but not in list. The instruction says use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive? It says use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be implying those are the headings we should use when appropriate. It didn't say we cannot use other headings, but to follow the pattern. Safer to stick to those. Thus we need to fit Success Metrics somewhere. Could be under Responsibilities as a bullet "Your Success Metrics". Or under Qualifications? I'd put under Responsibilities as a subheading maybe

                Success Metrics:

                then a

                . That's okay. Similarly, "Who you’ll work with?" we can incorporate into Responsibilities. Thus final sections: - About the role (company description + overview? Actually we already have company description separate

                . Then About the role heading with overview paragraph.) - Responsibilities (includes all responsibility bullets, plus success metrics, plus who you'll work with maybe) - Qualifications (What You'll Bring) - Skills (Core Skills, Competencies & Attributes) - Benefits - Pay - Schedule Now we need to ensure we don't include boilerplate like "Commitment To Diversity..." etc. Let's craft the HTML. We'll start with a

                for company description. Then

                About the role

                overview paragraph.

                Then

                Responsibilities

                • ... each main bullet. We need to include sub-bullets. Let's list responsibilities: Sales Pipeline Development & Management - Proactively identify and pursue new business opportunities, mapping key stakeholders and decision-makers within target accounts. - Build and maintain a robust pipeline through outbound prospecting, industry