Government Account Executive - SLED

We need to output HTML fragment with headings

for sections: About the 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. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Also remove physical tasks? The physical tasks are part of job description; they might be considered part of responsibilities or maybe schedule? The instructions: Use

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

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

  for prose. 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. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to parse the posting and extract sections. The posting includes: - Intro paragraph about Kinetic (company description). Could be "About the role"? Actually "About This Role" heading present. So we can have

  About the role

  with paragraph(s) describing the role. - Then "The Opportunity" maybe part of responsibilities? Could be part of About the role. - Then "What You’ll Do" list of duties: Drive New Business, Navigate Procurement, E-Rate Mastery, Strategic Networking, Solution Selling, Forecasting & Strategy. That's responsibilities. - Then "What You Bring" includes Experience, Telecom Knowledge, Procurement Expertise, Relationship Driven, Communication, Self-Motivated. That's qualifications/requirements/skills. Could split into Requirements (experience, telecom knowledge, procurement expertise) and Skills (relationship driven, communication, self-motivated). But we can combine. - Then "Why Join Us?" includes Competitive base salary plus uncapped commission potential. Comprehensive benefits package (Health, Dental, Vision, 401k). Specialized support from Sales Engineering and Public Sector bid teams. The opportunity to work with a leading-edge network that directly impacts the communities you serve. That's benefits and maybe pay. - Then "Physical Tasks- Standing Continuously: ..." etc. That's physical demands; maybe schedule? Not schedule. Could be part of responsibilities? Not exactly. Might be considered "Schedule"? No. It's physical tasks. Not in allowed headings list. Should we include? The instruction says use headings from list; we can omit sections not matching those headings. But we must preserve ALL substantive information. However we cannot invent headings not allowed. We could fold physical tasks into a

  under maybe Responsibilities or a generic section? But we must not create headings not in list. Could we include a

  Physical Demands

  ? Not allowed per instruction (they gave examples but not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they expect only those headings. Safer to stick to those. We could embed physical tasks in a

  under Responsibilities or maybe under a generic "About the role". But that may misrepresent. However instruction: "Prefer a few substantive sections over many thin ones." So we can combine. - Then "Audio Visual Needs - Hearing: Continuously: 67-100%| Near Vision: Frequently: 34-66% | Far Vision: Occasionally: 0-33% |Peripheral Vision: Occasionally: 0-33% | Color Discrimination: Occasionally: 0-33%". Also physical. - Then "Equipment Used in Job Performance/Working Environment: Computer, Printer, Telephone, Cellular Phone Type of Driver’s License Required: Driver’s License #IND456". That's equipment and license. - Then "Our Benefits Medical, Dental, Vision Insurance Plans 401K Plan Health & Flexible Savings Account Life and AD&D, Spousal Life, Child Life Insurance Plans Educational Assistance Plan". That's benefits details. - Then EEO boilerplate etc to remove. - Then "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's pay info but vague; we should not create Pay section if it's just "depends on location" without specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (our benefits). So we can include Benefits section with details. Pay: they say actual base pay will depend... no specific numbers. That's vague; maybe we should not create Pay section because it's not specific. However they said "Competitive base salary plus uncapped commission potential." That's under Why Join Us? That is pay info. So we can include Pay section with that sentence. - Schedule: not mentioned. So no Schedule section. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. Possibly also Qualifications separate from Requirements. But we can combine. We need to use

  • for any list of duties/requirements/benefits. So for responsibilities list, we make
    • . For requirements list (experience, telecom knowledge, procurement expertise) also list. For skills list (relationship driven, communication, self-motivated) also list. For benefits list (Medical, Dental, Vision Insurance Plans, 401K Plan, Health & Flexible Savings Account, Life and AD&D, Spousal Life, Child Life Insurance Plans, Educational Assistance Plan) also list. We need to preserve all substantive info: include company description paragraph, the opportunity paragraph, etc. We must remove boilerplate: EEO, legal notices, etc. Also remove duplicated lines (like repeated "Our Benefits" maybe). Also remove application instructions (none present). Also remove the physical tasks and audio visual needs? They are substantive but not fitting headings; maybe we can include them under Responsibilities as additional duties? But they are not duties; they are physical demands. Could we include them under a generic

      after Benefits? The instruction says preserve ALL substantive information. So we need to include them somewhere. We could add a

      Physical Demands

      but not in allowed list. However maybe we can treat them as part of "About the role" or "Responsibilities". But that would be inaccurate. However 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. It might be okay to add other headings if needed, but they said "include a section ONLY when the posting has real, specific content for it". They didn't forbid other headings. But they gave examples of typical sections. Safer to stick to those headings to avoid violating. However we risk losing substantive info (physical tasks). Could we embed them in a

      under Benefits? Not appropriate. Maybe we can treat physical tasks as part of "Schedule"? No. Alternatively, we could create a

      Working Conditions

      but not in list. Might be considered deviating. Given the instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect only those headings. The physical tasks might be considered part of "Responsibilities" (like physical tasks you perform). But it's a stretch. We could decide to omit physical tasks and audio visual needs, but that would lose substantive info, violating "Preserve ALL substantive information". However maybe those are considered boilerplate? They are specific to job but not typical. Might be considered part of job description but not required to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical tasks are not those. So we should keep them. Thus we need a heading for them. Could we use "About the role" to include them? The about the role section could include a paragraph describing the role, including physical demands. That might be acceptable. Let's structure:

      About the role

      Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S. Additional information about Kinetic is available at www.GoKinetic.com

      Kinetic seeks a high-caliber Government Account Executive to drive infrastructure growth and digital transformation across the public sector. In this role, you will be responsible for identifying and closing high-value fiber-optic, voice, and data networking opportunities within school districts, municipalities, and state agencies.

      The Opportunity: As a Government Account Executive, you will act as a mission-critical partner to public sector leaders. You will leverage your expertise in government procurement and E-Rate funding to deliver high-capacity connectivity solutions that power essential community services and modern classrooms.

      Then responsibilities list. Then requirements list (experience, telecom knowledge, procurement expertise). Then skills list (relationship driven, communication, self-motivated). Then benefits list. Then pay info. We could also include a short paragraph for physical tasks and audio visual needs and equipment under About the role or maybe a separate

      Working Conditions

      but not in list. I'd rather add a

      Working Conditions

      to preserve info, hoping it's acceptable. The instruction didn't forbid other headings, just gave examples. It said "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That could be interpreted as you should use h3 for headings, and those are examples of possible headings. So we can add other headings as needed. I'll add a

      Working Conditions

      for physical tasks, audio visual needs, equipment, driver's license. Now ensure we don't include boilerplate: remove EEO, legal notices, etc. Also remove duplicated lines: The "Our Benefits" appears both in Why Join Us? and later "Our Benefits". We'll combine. Now craft HTML. We need to output only HTML fragment, no /, no markdown. Let's draft:

      About the role

      Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in the U.S. Additional information about Kinetic is available at www.GoKinetic.com.

      Kinetic seeks a high-caliber Government Account Executive to drive infrastructure growth and digital transformation across the public sector. In this role, you will be responsible for identifying and closing high-value fiber-optic, voice, and data networking opportunities within school districts, municipalities, and state agencies.