CE Construction Support Representative

We need to produce HTML fragment with sections: About the role? The posting includes a paragraph at start: "Power up a career...". That's like overview. Could be "About the role" or maybe "Position Overview". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions (none). We need to preserve all substantive info. We need to decide sections: maybe "About the role" (intro paragraph), "Responsibilities" (Technical Responsibilities list), "Requirements" (Required Qualifications), "Preferred Qualifications" maybe as "Qualifications"? But we have Required Qualifications and Preferred Qualifications. Could combine into "Qualifications" with sub-sections? But we only allowed headings from list; we could have "Requirements" for required qualifications, and maybe "Preferred Qualifications" not in list; but we could treat as "Qualifications" covering both? However we need to preserve all info. Could have "Requirements" for required qualifications, and "Preferred Qualifications" as a separate heading? Not in allowed list but maybe we can still use if content exists? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could also use other headings if needed? Safer to stick to those. We could put required qualifications under "Requirements". Preferred qualifications could go under "Qualifications" (maybe separate). But we have both Required and Preferred; we could put Required under "Requirements" and Preferred under "Qualifications". That seems fine. We also have "Advancement Opportunity", "Work Environment & Position Expectations", "Benefits". Benefits section: they list benefits after "TECO offers a competitive Benefits package!!". That's substantive. So we need Benefits heading. Pay: they mention "Competitive Salary" but not specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. They state "Competitive Salary" but no specific figure; is that considered stating them? It says "Competitive Salary" as a phrase; it's not a specific number but it's stating that there is competitive salary. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not say they need to be specific numbers; just states them. So we can include Pay section with the statement "Competitive Salary". However they also list benefits after that. Could combine Pay and Benefits? But better separate. Schedule: they mention occasional overtime may be required, but not a schedule. Not specific schedule; maybe we shouldn't create Schedule section because not stated. They didn't give schedule details. So omit Schedule. We also have "Storm Duty Requirements" which is a condition of employment; could be part of Responsibilities or Work Environment. Might fit under "Work Environment & Position Expectations". We'll include that content there. We need to remove boilerplate: EEO statements, legal, etc. Also remove duplicated lines. Also remove "TECO offers a competitive Benefits package!!" maybe keep as part of Benefits. We need to preserve all substantive info: that includes the introductory paragraph, position overview, technical responsibilities (list), required qualifications (education, experience, knowledge/skills/abilities), preferred qualifications (education, experience, knowledge/skills/abilities), advancement opportunity, work environment & position expectations (including storm duty), benefits list. We need to format lists with

• . For prose use

  . For headings use

  . We must not repeat job title as heading. The job title is "CE Construction Support Representative I". Not to be used as heading. We need to output only HTML fragment. Let's craft. First, maybe an

  About the role

  with the introductory paragraph(s) up to "Position Overview". Actually the introductory paragraph before "Position Overview" is: "Power up a career with us. Our people are our greatest investments. Be the light to help us keep our customers connected. If you are interested in a career and not just a position, Tampa Electric is the place to be! Tampa Electric offers competitive pay, a comprehensive benefits package and opportunities for growth and development in a friendly and professional work environment. We embrace diversity and the inclusion of all. We believe our differences, unique perspectives and talents are our strengths and integral to the success of our company. We’re honored to serve approximately 780,000 customers across West Central Florida and safely provide them with clean, affordable and reliable electricity. We’ve been doing it for more than 100 years, and there’s so much more ahead. Join our team of energy experts as we build on that legacy through innovation, continued solar investments, cost-effective and sustainable energy solutions all while keeping top-notch customer service at the center of all we do. Tampa Electric is a subsidiary of Emera Inc., a family of energy companies which also includes TECO Peoples Gas and New Mexico Gas Company. Emera provides energy to residential and commercial customers in the United States, Canada, and the Caribbean, with career opportunities available in all of these locations." That's substantive; we can put under About the role. Then we have "Position Overview" which could be part of About the role or separate heading? Could be under About the role as well. But we could also make a separate heading "Position Overview" but not in list; maybe we keep under About the role. Then "Technical Responsibilities" is a list; we can put under

  Responsibilities

  with a
  . Then "Required Qualifications" under

  Requirements

  with subheadings? We could just list items as
  but we need to preserve categories: Education, Experience, Required Knowledge/Skills/Abilities. Could keep as
  with each item maybe containing subpoints. But we need to preserve all info; we can embed paragraphs inside
  • . Simpler: produce
    • Education: High School Diploma or equivalent
    etc. But we must not add extra formatting not in original? Using is okay but not required; we can just write plain text. We'll do:

    Requirements

    • Education: High School Diploma or equivalent
    • Experience: Minimum 3 years' direct work experience in a Contact Center Customer Service environment or in an Engineering Construction environment.
    • Required Knowledge/Skills/Abilities: Working knowledge of Customer Relationship Management (CRM) system(s); Knowledge of Microsoft Office Suites; Ability to refer to documentation or manuals/guidelines to resolve issues; Ability to recommend and implement process improvement, update manuals and support new/amended business requirements; Strong organizational and time management skills; Excellent written and oral communication skills; Ability to perform moderately complex assignments independently to support the New Construction Department; Ability to effectively interact with external TEC contacts (consultants, engineers, architects, government officials, developers, etc.) to discuss technical project/customer requirements; Understand the importance of assimilating the needs of the customer and the Company and incorporate those needs into processes; Ability to meet deadlines, possess initiative, adapt to a fast-paced work environment, and handle many tasks at once under minimal supervision; Ability to reference documentation or manuals/guidelines to resolve issues and have a basic foundational knowledge of processes to provide general assistance; Demonstrated strong analytical, planning, and organizational skills and the ability to work independently.
    But that's a long list; maybe break into multiple
    • for each ability. Better to separate each ability as its own
    • . Let's do that. Similarly for Preferred Qualifications under

      Qualifications

      (or maybe

      Preferred Qualifications

      but not in list). We'll use

      Qualifications

      and include both required and preferred? But we already used Requirements for required. So Qualifications for preferred. We'll list:

      Qualifications

      • Education Preferred: Associates degree in a related field.
      • Direct Experience Preferred: Direct work experience in the electric utility industry in a customer service role
      • Preferred Knowledge/Skills/Abilities: Proficient understanding of how to relate rate types to customer work request and billing coordinate with all systems; Ability to read and analyze professional architectural and engineered drawings along with electric utility primary circuit maps, to include knowledge of CAD; Ability to analyze and interpret Electrical and Construction Drawings; Knowledge of TEC Customer Service policies and procedures and working knowledge of WorkPro; Knowledge of Maxviewer & Finesse, GIS (Geographic Information System), and PCAD, and Google Earth; Knowledge of Standard Electrical Service Requirement (SESR) handbook; Knowledge of FTP Site and Access/View Service Alerts; Working knowledge of blueprints and schematics and the ability to read electrical prints, riser diagrams, panel schedules, civil and site drawings; Ability to analyze technical data with knowledge of construction types (new/existing/renovations), amperage, voltage (single and three phase), and loads associated with retail, office, warehouse, residential, pumps, temporary service, etc.; comparing application and customer submitted drawings to ensure accuracy and inquire about discrepancies.
      But again we could split each. Then Advancement Opportunity: could be under

      Advancement Opportunity

      but not in list. Maybe we can incorporate into Requirements or Qualifications? But it's substantive; we could create a heading "Advancement Opportunity" even if not in example list; 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 says "use

      for section headings (e.g. ...)". It implies we should use those headings for sections; but we could still use other headings if needed. Safer to stick to given list. Where to put advancement? Could be under "Requirements" or "Qualifications"? Not ideal. Maybe we can put under "Responsibilities"? Not really. Could be under "About the role"? Not ideal. We could treat advancement as part of "Requirements" as a bullet? But it's not a requirement. Could be under "Qualifications". Might be okay. Alternatively we could create a section "Advancement Opportunity" using

      even if not in list; risk of violating instruction? The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but the examples are given. Usually they expect you to use those headings only. However they also say "Prefer a few substantive sections over many thin ones." So we could combine advancement into "Requirements" or "Qualifications". I'd put it under "Qualifications" as a bullet. Work Environment & Position Expectations: we could put under

      Responsibilities

      or maybe a separate heading "Work Environment". Not in list. Could incorporate into Responsibilities as a paragraph after list. Benefits:

      Benefits

      with
      . Pay:

      Pay

      with

      Competitive Salary

      . Schedule: we omit. Now we need to remove boilerplate: EEO statements, legal, ADA policy, etc. Also remove "STORM DUTY REQUIREMENTS....Please make sure to read below!!!" but we need to keep the substance: "Responding to storms will be considered a condition of employment..." etc. We'll incorporate that into Work Environment paragraph. Also remove duplicated lines. Now craft HTML. Let's write:

      About