Account Executive

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Intro: "If you are looking to be part of a company focused on making our roads and communities safer, apply to join our team of talented individuals today! *Please note - The pay rate will be based on experience*" This is a note about pay. - "What TAPCO has to offer you" then list: Aggressive Industry OTE paid monthly, 10 Paid Holidays, Paid Vacation and Personal Time (starting day one), Four Weeks of Paid Parental Leave with no waiting period, 401K Plan with Employer Match (fully vested on day one), Company-Funded Short-Term Disability, Health, Vision, and Dental insurance, Quarterly Company Events and Lunches, Have a say in TAPCO Happenings by joining the Fun or Safety Committee. That's benefits. - "What you will accomplish as a Account Executive at TAPCO:" then description of role. - Then "Duties and Responsibilities" with bullet points (some repeated). We need to extract duties. - Then "Key Success Metrics" with primary metrics and additional metrics. - Then "Knowledge/Skill/Ability:" list. - Then "About Us" paragraph. - Then EEO statement etc which we should remove (boilerplate). Also contact info maybe remove. We need sections: About the role (maybe the description under "What you will accomplish as a Account Executive at TAPCO:"), Responsibilities (duties), Requirements (maybe knowledge/skill/ability?), Qualifications (maybe not separate), Skills (maybe part of knowledge/skill/ability), Benefits (list), Pay (note about pay rate based on experience), Schedule (maybe not present). We should only include sections with real content. Pay: The posting says "*Please note - The pay rate will be based on experience*". That's specific enough? It's not a number but says based on experience. According to instruction: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay rate will be based on experience, so we can include Pay section with that sentence. Schedule: No mention of schedule (hours, remote, etc). So omit Schedule. Benefits: we have list. About the role: we have description of what you will accomplish. Responsibilities: duties and responsibilities. Requirements: maybe knowledge/skill/ability? Could be considered Requirements. Also there is "Knowledge/Skill/Ability:" which includes required skills. We'll put that under Requirements or Skills? The instruction says use headings for Requirements, Qualifications, Skills. We need to decide which to use. We have both knowledge/skill/ability list and maybe also "About Us" not needed. We could put the list under Requirements (or Skills). Since they ask for Skills heading as well, we could split: Requirements: experience selling into municipal/government, travel willingness, etc. Skills: proven success, hunter mindset, CRM knowledge, etc. But we need to avoid thin sections. Better to combine into one Requirements section that includes both knowledge/skill/ability and maybe qualifications. But we have to follow instruction: use headings for those categories if we have content. We could have Requirements and Skills both with content. Let's extract. Knowledge/Skill/Ability list: - Proven success in an outside sale, hunter-focused role. - Demonstrated experience selling complex solutions, including hardware and SaaS offerings. - Strong working knowledge of CRM systems with consistent and accurate usage (non-negotiable). - Experience selling into municipal, government, or public-sector environments preferred. - Willingness and ability to travel within assigned territory and attend industry events and trade shows. - Hunter mindset with strong prospecting, negotiation, and closing skills. - Strategic account growth with disciplined pipeline and opportunities management. - Effective cross-functional collaboration and territory execution. - Customer-focused, results-driven approach. That's a mix of skills and abilities. Could be placed under Skills. Requirements maybe: "Experience selling into municipal, government, or public-sector environments preferred." plus maybe "Willingness and ability to travel". But those are also in list. We could make Requirements: "Experience selling into municipal, government, or public-sector environments preferred. Willingness and ability to travel within assigned territory and attend industry events and trade shows." And Skills: the rest. But we need to avoid duplication. Let's decide to put all under Skills heading, and maybe not have Requirements. But we need to follow instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can choose which to include. It's okay to omit Requirements if we don't have distinct content. However we have some content that could be considered Requirements. But we can also put them under Skills. The instruction says "Prefer a few substantive sections over many thin ones." So better to combine into one section like "Requirements & Skills" but we don't have that heading. We could use "Requirements" and put all there. That would be substantive. Thus we will have sections: - About the role (description) - Responsibilities (duties) - Requirements (knowledge/skill/ability list) - Benefits (list) - Pay (note) We'll omit Qualifications and Schedule. Now we need to extract duties from "Duties and Responsibilities". The text includes repeated lines. Let's extract unique duties: - New Business & Expansion: Sell into white-space accounts using the full TAPCO-Logix product catalogue (hardware and SaaS). Own and expand A-tier accounts through land-and-expand strategies across all product lines. Partner with Inside Sales to elevate B-tier accounts into A-tier status. - Pipeline & CRM Accountability: (same as above? Actually repeats same lines). Might be duplicate; we can keep once. - Cloud & Saas Support: Position cloud/SaaS as a core component of the solution at point of sale. Support the SaaS Revenue Team during renewals and account lifecycle management. - Territory Representation: Serve as the ambassador for assigned territory and represent TAPCO-Logix at local trade shows, regional events, and industry forums. Conduct field visits to A-tier accounts and opportunistic visits to B/C-tier accounts while in market. - Contract Strategy: Utilize existing state, municipal, and co-op contracts to accelerate sales and streamline procurement. Proactively seek to establish new contracts with customers to enable long-term scale and simplified purchasing. - Cross-Functional Collaboration: Work in partnership with Inside Sales, SaaS team, and Specialist Teams (ASE, Parking, Wrong-Way, etc.) to maximize wallet share per account. We should keep each as bullet points. Now "Key Success Metrics": Could be considered part of Responsibilities or maybe separate but we don't have a heading for metrics. Could incorporate into Responsibilities as additional bullet? But we might add a separate section "Performance Metrics" but not in allowed headings. Better to incorporate into Responsibilities as bullet points. But we need to preserve all substantive information. So we need to include metrics somewhere. Could add under Responsibilities as bullet points: "Primary metrics: Bookings vs. Target; Pipeline Generation, Growth, and Velocity." and "Additional metrics: Minimum 8 new qualified meetings per week; Expansion revenue generated within A-tier accounts; Conversion rate of B accounts to A accounts; SaaS attach rate at initial point of sale; Increased product penetration per customer." We'll add those. Now "About Us": paragraph about TAPCO mission. Could be included under About the role? Actually About the role is about the role itself. About Us is company description. Could be a separate section "About the company" but not in allowed headings. Could incorporate into About the role? Might be okay to add a brief paragraph under About the role? But the instruction says About the role heading for section headings like About the role, Responsibilities, etc. So we can put company description under About the role? Might be confusing. Perhaps we can treat "About Us" as part of About the role? But better to have a section "About the company" but not allowed. However we could omit it as it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. We could put it under a heading "About the role" but that would misrepresent. Maybe we can add a section "About the company" using

even though not listed; but 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 exclusive list. So we can use other headings as long as they are

. So we can add

About TAPCO

with that paragraph. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, About TAPCO. Now we need to format lists with

• . For prose use

  . We need to ensure we don't include boilerplate: EEO statement, contact info, etc. Now craft HTML. Let's write:

  About the role

  The Account Executive exists to drive new revenue growth and strategic account expansion across all TAPCO-Logix product lines and cloud services. This role directly supports the company’s growth objectives by capturing white-space opportunities, increasing penetration within strategic accounts, and enabling cross-sell execution across hardware and SaaS offerings. This role is responsible for identifying, developing, and closing new businesses while expanding existing A-tier accounts using a land-and-expand strategy. Success is measured equally by bookings versus target and by pipeline generation, growth, and velocity. Pipeline performance is considered a core output of the role.

  Responsibilities

  • New Business & Expansion: Sell into white-space accounts using the full TAPCO-Logix product catalogue (hardware and SaaS). Own and expand A-tier accounts through land-and-expand strategies across all product lines. Partner with Inside Sales to elevate B-tier accounts into A-tier status.
  • Pipeline & CRM Accountability: Sell into white-space accounts using the full TAPCO-Logix product catalogue (hardware and SaaS). Own and expand A-tier accounts through land-and-expand strategies across all product lines. Partner with Inside Sales to elevate B-tier accounts into A-tier status.
  • Cloud & SaaS Support: Position cloud/SaaS as a core component of the solution at point of sale. Support the SaaS Revenue Team during renewals and account lifecycle management.
  • Territory Representation: Serve as the ambassador for assigned territory and represent TAPCO-Logix at local trade shows, regional events, and industry forums. Conduct field visits to A-tier accounts and opportunistic visits to B/C-tier accounts while in market.
  • Contract Strategy: Utilize existing state, municipal, and co-op contracts to accelerate sales and streamline procurement. Proactively seek to establish new contracts with customers to enable long-term scale and simplified purchasing.
  • Cross-Functional Collaboration: Work in partnership with Inside Sales, SaaS team, and Specialist Teams (ASE, Parking, Wrong-Way, etc.) to maximize wallet share per account.
  • Key Success Metrics: Primary (Equally Weighted) – Bookings vs. Target; Pipeline Generation, Growth, and Velocity. Additional Metrics – Minimum 8 new qualified meetings per week; Expansion revenue generated within A-tier accounts; Conversion rate of B accounts to A accounts; SaaS attach rate at initial point of sale; Increased product penetration per customer.

  Requirements

  • Proven success in an outside sale, hunter-focused role.
  • Demonstrated experience selling complex solutions, including hardware and SaaS offerings.
  • Strong