Field Service Technician III
for section headings.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate: EEO, etc. Also remove application instructions like "Apply today". Also remove navigation/cookie etc. Also remove duplicated lines.
We need to keep all substantive info: intro paragraph, responsibilities list, experience requirements, additional requirements, bonus points, benefits list.
We need to structure sections: About the role (intro paragraph). Responsibilities (list of duties). Requirements (maybe experience and qualifications). Could separate Qualifications and Skills but we can combine if thin. Let's see.
We have:
- Intro: "We’re looking for Field Service Technicians with strong testing and troubleshooting experience who are ready to take on challenging fieldwork across the country. In this hands-on role, you’ll test, maintain, and commission low to high-voltage systems at power plants, hydroelectric dams, and other industrial sites. You’ll work with relays, transformers, breakers, SCADA systems, and more—bringing reliable energy solutions to life. This is a great opportunity to develop technical skills and grow with a fast-paced, mission-driven team."
That's About the role.
Responsibilities: bullet list after "What You’ll Do". Items:
- Test, maintain, and collect data on low, medium, and high voltage systems (480V–600kV), including breakers, relays, switchgear, cables, and transformers
- Run standard field tests (TTR, insulation resistance, Power Factor, Tan Delta, VLF, DC Hi-Pot)
- Test relays (electromechanical and solid-state) with minimal supervision
- Troubleshoot control circuits, relay logic, and protection schemes
- Function check control panels, trip/alarm circuits, and SCADA signal integrity
- Support commissioning activities and ensure customer satisfaction
- Read and interpret schematics, drawings, manuals, and one-line diagrams
- Communicate with customers on-site and provide timely job updates
- Keep accurate reports, logs, and equipment calibration records
- Follow all RMS Energy and site safety procedures (Lockout/Tagout, PPE, JHA)
- Use hand tools and test equipment safely and correctly
- Inspect and maintain PPE and job tools
- Help mentor Tech I team members on procedures and safe practices
That's responsibilities.
Experience We’re Looking For: bullet list:
- 3–5 years of field experience testing, maintaining, and commissioning power systems up to 500kV; related experience considered.
- Experience with megohmmeters, TTRs, contact resistance testers, and insulation testers
- Familiarity with PowerDB or similar test documentation software
- Strong understanding of NFPA 70E, OSHA 1910.269, and field safety standards
- Able to read and interpret schematics and one-line diagrams
- NETA Level II certification preferred or active pursuit of certification
- Proficient in Microsoft Office Suite (Excel, Word, Outlook, Teams)
- Organized, safety-conscious, and able to manage time and priorities independently
Additional Requirements: bullet list:
- Willingness to travel up to 75% across the continental U.S.
- High school diploma or GED required
- Valid driver’s license
- Must successfully complete a background check and pre-employment/random drug tests
- Legally authorized to work in the United States
- Available for extended and irregular hours as needed
- Able to work outdoors in all weather, at heights (100+ ft), in confined spaces, and around high-voltage equipment and heavy machinery
- Physically capable of lifting 50+ lbs and enduring extended physical activity
- Requires good vision, hearing, and English proficiency for safe, effective communication in noisy environments
Bonus Points For: bullet list:
- NETA Level II or higher certification
- An associate’s or Bachelor’s degree in Electrical Technology, Power Systems, or Mechanical Engineering
- TWIC card
- Previous experience in testing or commissioning substation equipment
- Strong documentation and reporting skills using PowerDB or similar systems
Benefits (Why Join RMS Energy): bullet list:
- Competitive Compensation – Overtime potential and merit-based raises
- Full Benefits – Medical, dental, and vision coverage fully paid for employees, starting the month after hire
- Steady Employment & Career Growth – Be part of a fast-growing company with promotion potential
- 401(k) with Company Match – Traditional & Roth options + free investment guidance
- Top-Tier Equipment – Provided to support you in the field
- Compensated Travel Time plus Per Diem – Earn while seeing new places
- Education Support – Paid training, certifications, and industry memberships
- Generous PTO – Paid vacation, holidays, and sick leave
- Employee Assistance Program – Legal, financial, and mental wellness support
We need to avoid repeating job title as heading. No Pay section. Schedule? We have travel and hours info under Additional Requirements. Could we create a Schedule section with travel and hours? But that would duplicate content. Better to keep travel and hours under Additional Requirements or maybe under Requirements. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But we need to decide where to put each piece.
We have experience requirements (years, equipment familiarity, standards, NETA, Office). That's like Requirements. Qualifications could be education, certifications, degrees. Skills could be technical skills (testing equipment, software, reading schematics, etc). But many overlap.
We could combine Requirements and Qualifications into one section "Requirements". But we need to avoid thin sections. Perhaps we can have:
- About the role (intro)
- Responsibilities (list)
- Requirements & Qualifications (combined) (list of experience, education, certifications, etc)
- Skills (list of technical skills like testing equipment, software, safety standards, Office proficiency)
- Benefits (list)
- Schedule (travel and hours) maybe.
But we need to ensure we don't create thin sections. Let's see content:
Experience We’re Looking For: includes years, equipment, software, standards, NETA, Office, organized.
Additional Requirements: includes travel, diploma, license, background, authorization, hours, physical, vision.
Bonus Points: includes NETA level II+, degree, TWIC, substation experience, documentation skills.
We could treat Requirements as the mandatory items (Experience We’re Looking For + Additional Requirements). Qualifications as Bonus Points? Or Skills as technical skills.
But we need to avoid duplication. Let's think: The posting already has headings: "The Experience We’re Looking For", "Additional Requirements", "Bonus Points For". We could map those to sections: Requirements (Experience We’re Looking For), Qualifications (Additional Requirements), Skills (Bonus Points). But Bonus Points are not skills exactly; they are preferred qualifications.
Better: Use sections: About the role, Responsibilities, Requirements (combining Experience We’re Looking For + Additional Requirements), Benefits. That's maybe enough. But we lose Bonus Points and Skills details. However we could incorporate Bonus Points into Requirements as "Preferred qualifications". The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep Bonus Points info somewhere. Could add a section "Preferred Qualifications". That's allowed as a heading? The allowed headings list includes Qualifications, Skills, Benefits, Pay, Schedule. Not "Preferred Qualifications". But we could put them under Qualifications (makes sense). Or under Skills.
We have to use only the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these.
Thus:
- About the role: intro paragraph.
- Responsibilities: the "What You’ll Do" list.
- Requirements: mandatory items: Experience We’re Looking For (3-5 years, equipment familiarity, software, standards, NETA II preferred, Office proficiency, organized) + Additional Requirements (travel, diploma, license, background, auth, hours, physical, vision). That's a lot but okay.
- Qualifications: maybe education/certifications: Bonus Points (NETA Level II or higher, associate/bachelor degree, TWIC card, previous substation experience, strong documentation/reporting skills using PowerDB). Also maybe NETA Level II preferred already in Requirements but we can keep as qualification.
- Skills: maybe technical skills: testing equipment, reading schematics, troubleshooting, etc. But many of those are in Responsibilities. However we could list skills like "Testing low to high voltage systems", "Running standard field tests", "Testing relays", "Troubleshooting control circuits", "Function checking panels", "Reading schematics", "Communicating with customers", "Maintaining reports", "Following safety procedures", "Using hand tools", "Inspecting PPE", "Mentoring". That seems overlapping with responsibilities but could be considered skills. However we need to avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but we should avoid unnecessary duplication. However we can keep responsibilities as duties, and skills as abilities. Might be okay.
But we could also omit Skills section if it's thin. However we have many skills listed in responsibilities; we could move them to Skills and keep responsibilities more high-level? But responsibilities already detailed. Better to keep responsibilities as duties, and maybe Skills section could be empty -> not allowed. So we should not create Skills if no specific content beyond what's already in responsibilities. However we could extract some skill statements not captured as duties: e.g., "Proficient in Microsoft Office Suite", "Strong understanding of NFPA 70E, OSHA 1910.269", "Able to read and interpret schematics", "Organized, safety-conscious, able to manage time". Those are skills/qualities. Those could go under Skills.
Thus:
- Requirements: mandatory experience and qualifications (years, equipment, software, standards, NETA II preferred, Office proficiency, organized, safety-conscious, time management, diploma, license, background, auth, travel, hours, physical, vision). That's a mix.
- Qualifications: education and certifications: NETA Level II or higher, associate/bachelor degree in relevant fields, TWIC card, previous substation experience, strong documentation/reporting skills using PowerDB.
- Skills: technical abilities: testing low/medium/high voltage systems, running standard field tests, testing relays, troubleshooting control circuits, function checking panels, reading schematics, communicating with customers, maintaining reports, following safety procedures, using hand tools, inspecting PPE, mentoring.
But we see overlap: reading schematics appears both in Skills and Requirements (under "Able to read and interpret schematics"). That's okay maybe.
We need to ensure
for prose. We need to remove boilerplate: EEO, etc. Also remove application instructions like "Apply today". Also remove navigation/cookie etc. Also remove duplicated lines. We need to keep all substantive info: intro paragraph, responsibilities list, experience requirements, additional requirements, bonus points, benefits list. We need to structure sections: About the role (intro paragraph). Responsibilities (list of duties). Requirements (maybe experience and qualifications). Could separate Qualifications and Skills but we can combine if thin. Let's see. We have: - Intro: "We’re looking for Field Service Technicians with strong testing and troubleshooting experience who are ready to take on challenging fieldwork across the country. In this hands-on role, you’ll test, maintain, and commission low to high-voltage systems at power plants, hydroelectric dams, and other industrial sites. You’ll work with relays, transformers, breakers, SCADA systems, and more—bringing reliable energy solutions to life. This is a great opportunity to develop technical skills and grow with a fast-paced, mission-driven team." That's About the role. Responsibilities: bullet list after "What You’ll Do". Items: - Test, maintain, and collect data on low, medium, and high voltage systems (480V–600kV), including breakers, relays, switchgear, cables, and transformers - Run standard field tests (TTR, insulation resistance, Power Factor, Tan Delta, VLF, DC Hi-Pot) - Test relays (electromechanical and solid-state) with minimal supervision - Troubleshoot control circuits, relay logic, and protection schemes - Function check control panels, trip/alarm circuits, and SCADA signal integrity - Support commissioning activities and ensure customer satisfaction - Read and interpret schematics, drawings, manuals, and one-line diagrams - Communicate with customers on-site and provide timely job updates - Keep accurate reports, logs, and equipment calibration records - Follow all RMS Energy and site safety procedures (Lockout/Tagout, PPE, JHA) - Use hand tools and test equipment safely and correctly - Inspect and maintain PPE and job tools - Help mentor Tech I team members on procedures and safe practices That's responsibilities. Experience We’re Looking For: bullet list: - 3–5 years of field experience testing, maintaining, and commissioning power systems up to 500kV; related experience considered. - Experience with megohmmeters, TTRs, contact resistance testers, and insulation testers - Familiarity with PowerDB or similar test documentation software - Strong understanding of NFPA 70E, OSHA 1910.269, and field safety standards - Able to read and interpret schematics and one-line diagrams - NETA Level II certification preferred or active pursuit of certification - Proficient in Microsoft Office Suite (Excel, Word, Outlook, Teams) - Organized, safety-conscious, and able to manage time and priorities independently Additional Requirements: bullet list: - Willingness to travel up to 75% across the continental U.S. - High school diploma or GED required - Valid driver’s license - Must successfully complete a background check and pre-employment/random drug tests - Legally authorized to work in the United States - Available for extended and irregular hours as needed - Able to work outdoors in all weather, at heights (100+ ft), in confined spaces, and around high-voltage equipment and heavy machinery - Physically capable of lifting 50+ lbs and enduring extended physical activity - Requires good vision, hearing, and English proficiency for safe, effective communication in noisy environments Bonus Points For: bullet list: - NETA Level II or higher certification - An associate’s or Bachelor’s degree in Electrical Technology, Power Systems, or Mechanical Engineering - TWIC card - Previous experience in testing or commissioning substation equipment - Strong documentation and reporting skills using PowerDB or similar systems Benefits (Why Join RMS Energy): bullet list: - Competitive Compensation – Overtime potential and merit-based raises - Full Benefits – Medical, dental, and vision coverage fully paid for employees, starting the month after hire - Steady Employment & Career Growth – Be part of a fast-growing company with promotion potential - 401(k) with Company Match – Traditional & Roth options + free investment guidance - Top-Tier Equipment – Provided to support you in the field - Compensated Travel Time plus Per Diem – Earn while seeing new places - Education Support – Paid training, certifications, and industry memberships - Generous PTO – Paid vacation, holidays, and sick leave - Employee Assistance Program – Legal, financial, and mental wellness support We need to avoid repeating job title as heading. No Pay section. Schedule? We have travel and hours info under Additional Requirements. Could we create a Schedule section with travel and hours? But that would duplicate content. Better to keep travel and hours under Additional Requirements or maybe under Requirements. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But we need to decide where to put each piece. We have experience requirements (years, equipment familiarity, standards, NETA, Office). That's like Requirements. Qualifications could be education, certifications, degrees. Skills could be technical skills (testing equipment, software, reading schematics, etc). But many overlap. We could combine Requirements and Qualifications into one section "Requirements". But we need to avoid thin sections. Perhaps we can have: - About the role (intro) - Responsibilities (list) - Requirements & Qualifications (combined) (list of experience, education, certifications, etc) - Skills (list of technical skills like testing equipment, software, safety standards, Office proficiency) - Benefits (list) - Schedule (travel and hours) maybe. But we need to ensure we don't create thin sections. Let's see content: Experience We’re Looking For: includes years, equipment, software, standards, NETA, Office, organized. Additional Requirements: includes travel, diploma, license, background, authorization, hours, physical, vision. Bonus Points: includes NETA level II+, degree, TWIC, substation experience, documentation skills. We could treat Requirements as the mandatory items (Experience We’re Looking For + Additional Requirements). Qualifications as Bonus Points? Or Skills as technical skills. But we need to avoid duplication. Let's think: The posting already has headings: "The Experience We’re Looking For", "Additional Requirements", "Bonus Points For". We could map those to sections: Requirements (Experience We’re Looking For), Qualifications (Additional Requirements), Skills (Bonus Points). But Bonus Points are not skills exactly; they are preferred qualifications. Better: Use sections: About the role, Responsibilities, Requirements (combining Experience We’re Looking For + Additional Requirements), Benefits. That's maybe enough. But we lose Bonus Points and Skills details. However we could incorporate Bonus Points into Requirements as "Preferred qualifications". The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep Bonus Points info somewhere. Could add a section "Preferred Qualifications". That's allowed as a heading? The allowed headings list includes Qualifications, Skills, Benefits, Pay, Schedule. Not "Preferred Qualifications". But we could put them under Qualifications (makes sense). Or under Skills. We have to use only the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. Thus: - About the role: intro paragraph. - Responsibilities: the "What You’ll Do" list. - Requirements: mandatory items: Experience We’re Looking For (3-5 years, equipment familiarity, software, standards, NETA II preferred, Office proficiency, organized) + Additional Requirements (travel, diploma, license, background, auth, hours, physical, vision). That's a lot but okay. - Qualifications: maybe education/certifications: Bonus Points (NETA Level II or higher, associate/bachelor degree, TWIC card, previous substation experience, strong documentation/reporting skills using PowerDB). Also maybe NETA Level II preferred already in Requirements but we can keep as qualification. - Skills: maybe technical skills: testing equipment, reading schematics, troubleshooting, etc. But many of those are in Responsibilities. However we could list skills like "Testing low to high voltage systems", "Running standard field tests", "Testing relays", "Troubleshooting control circuits", "Function checking panels", "Reading schematics", "Communicating with customers", "Maintaining reports", "Following safety procedures", "Using hand tools", "Inspecting PPE", "Mentoring". That seems overlapping with responsibilities but could be considered skills. However we need to avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but we should avoid unnecessary duplication. However we can keep responsibilities as duties, and skills as abilities. Might be okay. But we could also omit Skills section if it's thin. However we have many skills listed in responsibilities; we could move them to Skills and keep responsibilities more high-level? But responsibilities already detailed. Better to keep responsibilities as duties, and maybe Skills section could be empty -> not allowed. So we should not create Skills if no specific content beyond what's already in responsibilities. However we could extract some skill statements not captured as duties: e.g., "Proficient in Microsoft Office Suite", "Strong understanding of NFPA 70E, OSHA 1910.269", "Able to read and interpret schematics", "Organized, safety-conscious, able to manage time". Those are skills/qualities. Those could go under Skills. Thus: - Requirements: mandatory experience and qualifications (years, equipment, software, standards, NETA II preferred, Office proficiency, organized, safety-conscious, time management, diploma, license, background, auth, travel, hours, physical, vision). That's a mix. - Qualifications: education and certifications: NETA Level II or higher, associate/bachelor degree in relevant fields, TWIC card, previous substation experience, strong documentation/reporting skills using PowerDB. - Skills: technical abilities: testing low/medium/high voltage systems, running standard field tests, testing relays, troubleshooting control circuits, function checking panels, reading schematics, communicating with customers, maintaining reports, following safety procedures, using hand tools, inspecting PPE, mentoring. But we see overlap: reading schematics appears both in Skills and Requirements (under "Able to read and interpret schematics"). That's okay maybe. We need to ensure