System Sales Executive

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: 1. About the Role - this is prose, should be

2. Key Responsibilities - has subsections with lists 3. Qualifications - has Required and Preferred lists 4. What We Offer - list of benefits Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Looking at the content: - "About the Role" - prose paragraph - "Key Responsibilities" - has 4 subsections with bullet points - "Qualifications" - has Required and Preferred lists - "What We Offer" - list of benefits - There's a "#HireFinder" and AI disclaimer at the end - this is boilerplate, should be removed I need to structure this properly. For Responsibilities, I could either make each subsection a separate

  or keep as one Responsibilities section with sub-lists. The rules say use

  for section headings like "Responsibilities". The subsections (Business Development, Project Evaluation, etc.) could be

  but the rules only mention

  . I'll use

  for main sections and maybe

  for subsections? The rules don't specify

  , but they say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use

  for those main sections. For subsections within Responsibilities, I could use

  or just make them part of the list. Since the rules don't forbid

  , but they only mention

  , I'll use

  for main sections and for subsections I'll use

  or just bold text? Better to use semantic HTML:

  for main sections,

  for subsections. But the example only lists

  for those specific headings. I think I should use

  for each major section: About the Role, Responsibilities, Qualifications, Benefits. Then within Responsibilities, the four areas could be

  or just list items with bold labels. Since the rules say "use

  • for any list of duties/requirements/benefits", I can make each responsibility area a list item with a bold label and then sub-list. But that might be messy. Better: For Responsibilities section, have an

    Responsibilities

    , then for each subsection, use an

    (though not explicitly allowed, but semantic) or just a

    Business Development & Opportunity Creation

    followed by

    . But the rules say use
    • for any list of duties. The duties are listed as bullet points under each subsection. So I'll do:

      Responsibilities

      Business Development & Opportunity Creation

      • ...

      Project Evaluation & Proposal Development

      • ...
      etc. But the rules don't mention

      . However, they don't forbid it. They say "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That implies those are the only headings needed. But the content has subsections. I think using

      is fine for subsections. Alternatively, I could make each subsection a separate

      but that would be too many headings. The example list includes "Responsibilities" as one heading. So I'll keep Responsibilities as one

      and use

      for subsections. Similarly for Qualifications:

      Qualifications

      then

      Required

      and

      Preferred

      with lists. For What We Offer:

      Benefits

      (since Benefits is in the example list) with a list. Now, the "About the Role" is prose, so

      About the Role

      then

      ...

      . The AI disclaimer and #HireFinder are boilerplate, remove. Also, note: "Do NOT repeat the job title as a heading (the page already shows it)" - the job title isn't in the provided text, so fine. No Job ID/requisition numbers. Now, let's write the HTML. I'll start with

      About the Role

      The company is seeking a commercially driven System Sales Executive to develop and close complex Fire Alarm and Life Safety system opportunities across the construction market. This role is ideal for a disciplined, technically credible sales professional who thrives in competitive environments and is motivated by winning projects. You will engage directly with General Contractors, Electrical Contractors, Engineers, and Building Owners to deliver code-compliant system solutions. Success requires strong prospecting discipline, technical credibility, and the ability to manage multi-stakeholder sales cycles that often span several months.

      Then

      Responsibilities

      Business Development & Opportunity Creation

      • Identify, qualify, and pursue new Fire Alarm and Life Safety system opportunities
      • Build relationships with contractors, engineers, developers, and building owners
      • Source opportunities via bid invitations, networking, referrals, and construction intelligence platforms
      • Attend pre-bid meetings, site walks, and design coordination sessions

      Project Evaluation & Proposal Development

      • Review drawings, specifications, and code requirements
      • Collaborate with Estimating and Engineering teams to develop competitive proposals
      • Ensure proposals are accurate, compliant, and complete
      • Identify value-engineering opportunities to optimize cost and compliance

      Sales Execution & Contract Award

      • Navigate complex, multi-stakeholder sales cycles
      • Lead negotiations on scope, pricing, and commercial terms
      • Position NY Fire Detection as a consultative partner
      • Drive opportunities from discovery through contract award

      Client Relationship Management

      • Serve as primary commercial contact during preconstruction phases
      • Maintain ownership of client relationships through pursuit and award
      • Transition awarded projects cleanly to Project Management and Engineering
      • Build long-term client relationships for repeat business and referrals

      Pipeline Management & Sales Discipline

      • Maintain accurate CRM pipeline reflecting opportunities, forecasts, and project status
      • Track bid activity, follow-ups, and pursuit strategies
      • Manage multiple pursuits simultaneously with attention to detail
      • Provide accurate forecasting and pipeline visibility to leadership
      Then

      Qualifications

      Required

      • 7+ years of quota-carrying B2B sales experience
      • Minimum 5 years in outside, hunter-style sales roles
      • Proven success closing complex, multi-stakeholder deals with long sales cycles
      • Demonstrated ability to develop new business through proactive prospecting
      • Experience in competitive bid environments or negotiated project sales
      • Strong pipeline management and organizational discipline
      • Professional communication and influencing skills

      Preferred

      • Experience in Fire Alarm, Life Safety Systems, Building Automation, Security Systems, HVAC, or Electrical Systems
      • Background selling into construction, engineering, or contractor-driven environments
      • Ability to review construction drawings, specifications, and technical documentation
      • Promotion history reflecting strong performance and growth
      • Familiarity with CRM tools and pipeline management
      Then

      Benefits

      • Competitive base salary with uncapped commission potential
      • Career development and leadership growth opportunities
      • Health, dental, vision, and flexible spending benefits
      • Paid time off and holidays
      • Vehicle reimbursement
      • A culture that values ownership, accountability, and operational excellence
      Note: The "What We Offer" section includes "Competitive base salary with uncapped commission potential" which is pay-related. The rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Competitive base salary with uncapped commission potential" under What We Offer. That is pay information. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay (base salary with commission). However, the example headings include "Pay" and "Benefits". The posting has "What We Offer" which includes both pay and benefits. I could split into Pay and Benefits, but the rules say "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". The posting has a list under "What We Offer" that includes both compensation and benefits. I think it's fine to have a single "Benefits" section that includes the compensation line, or create a "Pay" section for the salary/commission and "Benefits" for the rest. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Competitive base salary with uncapped commission potential" - that's pay. It also states health, dental, etc. - benefits. It also states "career development", "paid time off", "vehicle reimbursement", "culture". So there is specific content for both Pay and Benefits. However, the example headings list "Pay" and "Benefits" separately. I could create two sections:

      Pay

      and

      Benefits

      . But the posting groups them under "What We Offer". The rules say "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So both are allowed. I'll split them: Pay section for the salary/commission line, Benefits for the rest. But the salary line is just one item. That might be a thin section. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep as one Benefits section including the pay line. However, the pay line is specifically about compensation. I'll include it in Benefits but label the section "Benefits" (since the example includes Benefits). The posting says "What We Offer". I'll use

      Benefits

      and list all items. Alternatively, I could use

      What We Offer

      but the example headings don't include that; they include Benefits, Pay. I'll follow the example headings: use Benefits. Now, check for any other sections: Skills? Not explicitly.