Jobs · Engineering · North Carolina

Field Service Technician (NETA 3)

POWERX · Raleigh, NC · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About Us? 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: description of company, pillars, values, etc. That's substantive. Could be a section heading "About Us" but the allowed headings list includes "About the role". However they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not exclusive? Likely we should stick to those headings. But "About Us" is not in list; maybe we should use "About the role"? However the "About Us" is company overview, not role. Could we treat as "About the role"? Not exactly. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not limited. So we can use other headings if appropriate. But they also say "Prefer a few substantive sections over many thin ones." So we can have sections: About Us, Responsibilities, Requirements/Qualifications, Benefits, etc. We need to remove boilerplate: EEO statement at end, duplicated lines, etc. We need to preserve all substantive info: About Us paragraph, POWERX PERKS list (benefits), Job Summary, Supervisory Responsibilities, Duties/Responsibilities (list), Attributes/Abilities (list), Experience And Education (list), Physical Requirements (list). Also maybe "Competitive Pay" etc in PERKS. We need to not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state benefits: "Competitive PayIncentives for CertificationsReferral Bonus ProgramTuition ReimbursementMedical, dental, vision, LTD, STD, Basic Life/AD&D, and other ancillary products401k program with a company matchPerformance ProgramPaid Parental LeavePTO including Wellness Days and Paid HolidaysAnd much more!" That's benefits and pay. So we can have a Benefits section (maybe also Pay). But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Competitive Pay etc. So we can include a Benefits section (maybe combine Pay and Benefits). Could also have a Pay section if they mention competitive pay. But they said prefer few substantive sections over many thin ones. So we can combine Pay and Benefits into one "Benefits and Pay" section, but heading maybe "Benefits". Or we could have "Benefits" and include pay details there. Schedule: Not mentioned. So no Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to remove duplicated lines: The posting includes "required." after "NETA certification level 3 preferred. required." Might be a typo; we keep as is but maybe we can clean? We must preserve ALL substantive information; do not invent or summarize away detail. So we should keep the text as is, but we can fix obvious duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not remove words that are substantive. The duplication "required." after "preferred." maybe it's a mistake but it's still substantive? It's redundant but still part of posting. I'd keep it as is. We need to format lists with
    • . For prose, use

      . We need to decide sections: - About Us (maybe heading "About Us") - Job Summary (maybe heading "Job Summary" but not in examples; could be under Responsibilities? But we have separate sections for Responsibilities. The Job Summary is a prose paragraph summarizing role. Could be under "About the role". The examples include "About the role". So we could use heading "About the role" and put the Job Summary there. However there is also "About Us" company description. Could we have two sections: "About the company" and "About the role"? The instruction didn't forbid other headings. But to be safe, we could use "About the role" for the Job Summary, and maybe include a brief "About Us" as a paragraph before that? But they said do NOT repeat the job title as a heading. Not about company. Better to follow examples: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content: - About the role: Job Summary + maybe Supervisory Responsibilities? Actually supervisory responsibilities could be part of Responsibilities. But we have a separate "Supervisory Responsibilities" heading in the posting. Could treat as part of Responsibilities. - Responsibilities: Duties/Responsibilities list. - Requirements: Experience And Education list. - Qualifications: Attributes/Abilities list? Or maybe Qualifications includes certifications, education, experience. But we already have Experience And Education. Could combine. - Skills: maybe Microsoft Office, interpersonal skills, etc. Could be part of Attributes/Abilities. - Benefits: POWERX PERKS list. - Pay: maybe mention Competitive Pay within PERKS; we could include Pay section with that line. But we need to avoid many thin sections. Perhaps combine: Section 1: About the role (Job Summary) Section 2: Responsibilities (includes Supervisory Responsibilities and Duties/Responsibilities) Section 3: Qualifications (includes Experience And Education, Attributes/Abilities, maybe Skills) Section 4: Benefits (POWERX PERKS) We need to ensure we don't miss any substantive info: About Us company description is not covered. Should we include it? It's substantive. Could be placed under a heading "About the company" or maybe as a preamble before sections. The instruction says we can use headings like About the role etc. It didn't forbid other headings. I'd include an "About Us" section with the company description. Thus sections:

      About Us

      ... company description ...

      About the role

      Job Summary paragraph.

      Responsibilities

      • ... supervisory responsibilities ...
      • ... duties/responsibilities list ...
      But we need to separate supervisory responsibilities and duties? Could combine into one list. Better: Responsibilities section includes both supervisory responsibilities and duties/responsibilities. Thus list items: - Mentor Project Co-Lead Technician and NETA field technicians assigned to projects. Responsible for project success from start to finish, including the final report. - Perform moderate to advanced electrical measurements; collect and record data accurately. - Lead and manage projects, ensuring successful execution from start to finish; supervise and mentor project co-lead technicians and field technicians. - Write detailed reports on test results and findings; ensure reports are accurate and submitted in a timely manner. - Assist in setting up and removing test equipment for various testing activities; ensure proper handling and storage of equipment; maintain cleanliness of test equipment and work areas; ensure tools and equipment are kept in good condition. - Additional responsibilities and tasks as required to support the organization's goals and adapt to evolving business needs. We need to keep the exact phrasing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the wording as close as possible. However we can break into list items but must not lose info. We can keep each bullet as a sentence or phrase. We need to ensure we don't omit any piece: The supervisory responsibilities paragraph: "Mentor Project Co-Lead Technician and NETA field technicians assigned to projects. Responsible for project success from start to finish, including the final report." That's two sentences. Could be one list item. Duties/Responsibilities: They have headings: Moderate/Advanced Measurements, Project Management, Report Writing, Test Equipment, Additional responsibilities... We need to capture each bullet. Thus list items: - Perform moderate to advanced electrical measurements; collect and record data accurately. - Lead and manage projects, ensuring successful execution from start to finish; supervise and mentor project co-lead technicians and field technicians. - Write detailed reports on test results and findings; ensure reports are accurate and submitted in a timely manner. - Assist in setting up and removing test equipment for various testing activities; ensure proper handling and storage of equipment; maintain cleanliness of test equipment and work areas; ensure tools and equipment are kept in good condition. - Additional responsibilities and tasks as required to support the organization's goals and adapt to evolving business needs. We also need to include the supervisory responsibilities as separate bullet maybe. Now Qualifications/Requirements: We have Experience And Education list: - High school diploma/GED required, Associate’s degree from an accredited 2-year technical college or trade school preferred. - NETA certification level 3 preferred. required. (weird) - 5+ years of experience. - OSHA 10/30-hour, MSHA, NFPA 70-E, CPR/First Aid/BBP/AED, Power DB training a plus. We need to keep exactly as written? Might need to preserve punctuation. Attributes/Abilities list: - Must have a satisfactory background/MVR check. - Must pass a pre-employment, post-accident, reasonable suspicion, and/or random drug test. - Must have reliable transportation and possess a valid driver’s license. - Basic understanding of electrical theory. - Proficiency in Microsoft Office. - Interpersonal and social skills; strong customer service skills. - Excellent verbal and written communication. - Ability to prioritize tasks and attention to detail. Physical Requirements list: - Ability to travel up to 50% of the time. - Ability and willingness to work occasional overtime as needed. - Ability to lift up to 50 pounds. - Must wear appropriate and mandated PPE including arc-flash suit, safety glasses, hard hat, respirator, hearing protection, steel-toed boots, etc. - Ability to walk, stand, climb, pull, push, sit, and work in a cramped or confined space. - Potential low exposure to various conditions, including dirt, heat, fumes, smoke, water, noise, vibration, grease, oil, and dust. We could combine Experience And Education, Attributes/Abilities, Physical Requirements into a single "Requirements" section, but that may be too thick. However we can split into Requirements (Experience/Education + Attributes/Abilities) and maybe Physical Requirements as separate? But they said prefer few substantive sections over many thin ones. So maybe combine all into one "Requirements" section with sublists? But we need to use
      • for any list. Could have multiple lists under same section. Thus:

        Requirements

        Experience and Education:

          ...

        Attributes and Abilities:

          ...

        Physical Requirements:

          ...
        That's okay. Benefits section: P

Similar jobs

Service Technician

Middleburg CommunitiesGreenville, SC· 1 mo ago
Information Technologyapply on secure6.saashr.com

Service Technician

Sinclair TractorWashington, IA· 2 mo ago
Information Technologyapply on atsod.com

Service Technician

AramarkLouisville, KY· 2 mo ago
Information Technologyapply on careers.aramark.com

Service Technician

United Site ServicesMelbourne, FL· 3 mo ago
Information Technology$17.63/hrapply on careers.unitedsiteservices.com

Service Technician

CBX Solutions, LLCAustin, TX· 3 mo ago
Information Technologyapply on jobs.dayforcehcm.com

Service Technician

SRS Distribution Inc.Santa Ana, CA· 2 mo ago
Information Technology$20.63–$26.25/hr