Field Service Technician, NETA
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content for it
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
Let me structure this:
1. "Why IPS?" - This is company culture/values. Could be "About the role" or "About the company". Since it's about why work there, maybe "About the role" or "About the company". I'll use "About the role" as it's about the role's context.
2. "Benefits" - Clear benefits section with list.
3. "Responsibilities & Expectations" - Responsibilities section.
4. "Qualifications And Competencies" - Requirements/Qualifications.
5. "Physical Requirements" - Could be part of Requirements or separate. Since it's specific, I'll include as part of Requirements or separate "Requirements" section. The rules mention "Requirements" as a heading option. I'll combine Qualifications and Physical Requirements under "Requirements" or separate? The rules say "Requirements, Qualifications" as possible headings. I think "Requirements" can encompass both. But "Qualifications And Competencies" is a heading in the posting. I'll use "Qualifications" for that section and include physical requirements there or separate. Let me see: The posting has "Qualifications And Competencies" and then "Physical Requirements" as separate sections. I'll keep them separate: "Qualifications" and "Physical Requirements" (but "Physical Requirements" is not in the suggested headings list. The suggested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Physical Requirements" could fall under "Requirements". I'll make a "Requirements" section that includes both qualifications and physical requirements? Or separate "Qualifications" and "Requirements"? The posting has "Qualifications And Competencies" and "Physical Requirements". I'll use "Qualifications" for the first and "Requirements" for physical? But "Requirements" is a suggested heading. I think I'll create two sections: "Qualifications" and "Physical Requirements" but "Physical Requirements" is not in the list. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But they prefer few substantive sections. I'll combine physical requirements into Qualifications section as a subsection? But HTML doesn't have subsections with h3. I could make a single "Qualifications" section with two lists: one for qualifications/competencies, one for physical requirements. Or separate h3 for "Physical Requirements". I'll do separate h3 for "Physical Requirements" as it's substantive.
6. "You'll thrive at IPS if you..." - This is like desired skills/attributes. Could be "Skills" or "Qualifications". I'll make a "Skills" section.
7. "Who We Are" - Company description. Could be "About the role" or "About the company". Since we already have "Why IPS?" as about the role, maybe "Who We Are" is company description. I'll include as "About the company" but not in suggested headings. The suggested headings include "About the role". I'll use "About the role" for "Why IPS?" and maybe "About the company" for "Who We Are"? But the rules say use h3 for section headings (e.g. About the role...). It doesn't forbid other headings. But they prefer few sections. I could combine "Why IPS?" and "Who We Are" into one "About the role" section? They are distinct: one is why work here, the other is company description. I'll keep both but use appropriate headings: "About the role" for "Why IPS?" and "About the company" for "Who We Are"? However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "About the company". But it's an example list. I think it's okay to use "About the company". But to be safe, I'll use "About the role" for "Why IPS?" and maybe incorporate "Who We Are" into that same section? Or make a separate "About the company" heading. I'll do separate "About the company" as it's substantive.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine "Why IPS?" and "Who We Are" into one "About the role" section with two paragraphs? They are both prose. I'll combine them under "About the role" with two paragraphs.
Let's decide on sections:
- About the role (combining Why IPS? and Who We Are)
- Benefits
- Responsibilities
- Qualifications (including Qualifications And Competencies and Physical Requirements)
- Skills (You'll thrive at IPS if you...)
But Physical Requirements is a list, Qualifications And Competencies is a list. I'll keep them separate under Qualifications heading with two sub-lists? But HTML doesn't have sub-headings. I could use for Qualifications and then for Physical Requirements? But rules say use for section headings. Not sure about h4. Safer to make separate h3 sections: "Qualifications" and "Physical Requirements". But "Physical Requirements" is not in the example list. However, the rules say "e.g." so it's allowed. I'll do:
- About the role
- Benefits
- Responsibilities
- Qualifications
- Physical Requirements
- Skills
But that's many sections. Could combine Qualifications and Physical Requirements into one "Requirements" section. The example headings include "Requirements" and "Qualifications". They might be synonymous. I'll use "Qualifications" for the qualifications/competencies and "Requirements" for physical requirements? Or just "Requirements" for both. Let's see the posting: "Qualifications And Competencies" and "Physical Requirements". I'll create a "Qualifications" section for the first, and a "Physical Requirements" section for the second. That's fine.
Now, "You'll thrive at IPS if you..." is a list of attributes. That's "Skills" or "Qualities". I'll use "Skills".
Now, remove boilerplate: The last paragraph about EEO, background check, drug screen is boilerplate. Remove.
Also, "IPS is committed to equal employment opportunity..." etc. Remove.
Now, write HTML.
Let's start:
About the role
If you're searching for a place where you can grow, continue learning, and make a meaningful impact while still having time for the people and moments that matter most, welcome to Integrated Power Services! We believe your value extends far beyond your job title because the best work comes from people who feel supported, challenged, and fulfilled both professionally and personally. Here, you'll find opportunities to develop your career, work alongside exceptional teammates, and be part of a culture that recognizes that your life is worth just as much as your work—if not more. Because when people thrive, businesses thrive. If that sounds like the kind of place you've been looking for, we invite you to join us!
At IPS, we're committed to empowering you to make a meaningful impact. As the industry's leading and fastest-growing service provider, IPS offers single-source electromechanical and power management solutions to enhance the reliability of critical infrastructure across North America and the United Kingdom. We serve over 40,000 essential customer locations, from renewable energy pioneers to hospitals, manufacturers, and municipalities, helping them avoid costly downtime and ensure mission-critical operations. When you join IPS, you're joining a team that's revolutionizing equipment and process reliability across diverse sectors, from power generation to petrochemicals, and beyond. You'll learn from industry experts, grow alongside a talented workforce, and be part of a company that is built on the Shared Values of Safety, Integrity, Teamwork, Accountability, Customer Focus, and Entrepreneurial Spirit.
Benefits
- Paid Time Off (PTO)
- 401k Employer Match
- Bonus Incentives
- Extensive Training & Career Development Programs
- Tuition Reimbursement Program
- Medical, Dental and Vision plans
- Employee Assistance Program (EAP)
- And more!
Responsibilities
- Inspect, test, troubleshoot, perform start-up and collect data of low, medium and high voltage (to 500kV) electrical systems, and moderately complex relay calibration and power metering.
- Instrument transformer tests
- Power transformer testing - Doble, TTR, Insulation Resistance, etc.
- Test both electro-mechanical and solid state relays
- Cable testing - Tan Delta, Power Factor, VLF, DC Hipot
- Automatic transfer switch troubleshooting
- Low, Medium and High voltage switchgear and circuit breaker testing
- Rotate emergency on-call duty and if called respond to customer emergencies in a timely manner
- Strong verbal and written communication skills
- Must have a valid Driver’s License and acceptable driving record
- Ability to travel locally and overnight
- Ability to work flexible hours, overtime and weekends as required, willingness to be on call
- Work safely alone and as part of a team
- Closely adhere to all electrical safety procedures
- Effectively contributes to a strong team environment through assisting teammates in accomplishing mutual goals
Qualifications
- High school diploma or equivalent required
- Associate degree from an accredited 2-year technical college in Electrical Power, or similar experience/training from the military (Army Prime Power, Air Force Electrical Power Production, or NAVY Seabee) preferred
- Must have at least 5 or more years of relevant experience
- NETA Certification II or higher preferred or equivalent skills/experience to become NETA Certified
- Prefer OSHA 30 hour, MSHA, NFPA 70-E, CPR/First Aid/BBP
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Let me structure this: 1. "Why IPS?" - This is company culture/values. Could be "About the role" or "About the company". Since it's about why work there, maybe "About the role" or "About the company". I'll use "About the role" as it's about the role's context. 2. "Benefits" - Clear benefits section with list. 3. "Responsibilities & Expectations" - Responsibilities section. 4. "Qualifications And Competencies" - Requirements/Qualifications. 5. "Physical Requirements" - Could be part of Requirements or separate. Since it's specific, I'll include as part of Requirements or separate "Requirements" section. The rules mention "Requirements" as a heading option. I'll combine Qualifications and Physical Requirements under "Requirements" or separate? The rules say "Requirements, Qualifications" as possible headings. I think "Requirements" can encompass both. But "Qualifications And Competencies" is a heading in the posting. I'll use "Qualifications" for that section and include physical requirements there or separate. Let me see: The posting has "Qualifications And Competencies" and then "Physical Requirements" as separate sections. I'll keep them separate: "Qualifications" and "Physical Requirements" (but "Physical Requirements" is not in the suggested headings list. The suggested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Physical Requirements" could fall under "Requirements". I'll make a "Requirements" section that includes both qualifications and physical requirements? Or separate "Qualifications" and "Requirements"? The posting has "Qualifications And Competencies" and "Physical Requirements". I'll use "Qualifications" for the first and "Requirements" for physical? But "Requirements" is a suggested heading. I think I'll create two sections: "Qualifications" and "Physical Requirements" but "Physical Requirements" is not in the list. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so not exhaustive. But they prefer few substantive sections. I'll combine physical requirements into Qualifications section as a subsection? But HTML doesn't have subsections with h3. I could make a single "Qualifications" section with two lists: one for qualifications/competencies, one for physical requirements. Or separate h3 for "Physical Requirements". I'll do separate h3 for "Physical Requirements" as it's substantive.
6. "You'll thrive at IPS if you..." - This is like desired skills/attributes. Could be "Skills" or "Qualifications". I'll make a "Skills" section.
7. "Who We Are" - Company description. Could be "About the role" or "About the company". Since we already have "Why IPS?" as about the role, maybe "Who We Are" is company description. I'll include as "About the company" but not in suggested headings. The suggested headings include "About the role". I'll use "About the role" for "Why IPS?" and maybe "About the company" for "Who We Are"? But the rules say use h3 for section headings (e.g. About the role...). It doesn't forbid other headings. But they prefer few sections. I could combine "Why IPS?" and "Who We Are" into one "About the role" section? They are distinct: one is why work here, the other is company description. I'll keep both but use appropriate headings: "About the role" for "Why IPS?" and "About the company" for "Who We Are"? However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "About the company". But it's an example list. I think it's okay to use "About the company". But to be safe, I'll use "About the role" for "Why IPS?" and maybe incorporate "Who We Are" into that same section? Or make a separate "About the company" heading. I'll do separate "About the company" as it's substantive.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine "Why IPS?" and "Who We Are" into one "About the role" section with two paragraphs? They are both prose. I'll combine them under "About the role" with two paragraphs.
Let's decide on sections:
- About the role (combining Why IPS? and Who We Are)
- Benefits
- Responsibilities
- Qualifications (including Qualifications And Competencies and Physical Requirements)
- Skills (You'll thrive at IPS if you...)
But Physical Requirements is a list, Qualifications And Competencies is a list. I'll keep them separate under Qualifications heading with two sub-lists? But HTML doesn't have sub-headings. I could use for Qualifications and then for Physical Requirements? But rules say use for section headings. Not sure about h4. Safer to make separate h3 sections: "Qualifications" and "Physical Requirements". But "Physical Requirements" is not in the example list. However, the rules say "e.g." so it's allowed. I'll do:
- About the role
- Benefits
- Responsibilities
- Qualifications
- Physical Requirements
- Skills
But that's many sections. Could combine Qualifications and Physical Requirements into one "Requirements" section. The example headings include "Requirements" and "Qualifications". They might be synonymous. I'll use "Qualifications" for the qualifications/competencies and "Requirements" for physical requirements? Or just "Requirements" for both. Let's see the posting: "Qualifications And Competencies" and "Physical Requirements". I'll create a "Qualifications" section for the first, and a "Physical Requirements" section for the second. That's fine.
Now, "You'll thrive at IPS if you..." is a list of attributes. That's "Skills" or "Qualities". I'll use "Skills".
Now, remove boilerplate: The last paragraph about EEO, background check, drug screen is boilerplate. Remove.
Also, "IPS is committed to equal employment opportunity..." etc. Remove.
Now, write HTML.
Let's start:
About the role
for Qualifications and then for Physical Requirements? But rules say use for section headings. Not sure about h4. Safer to make separate h3 sections: "Qualifications" and "Physical Requirements". But "Physical Requirements" is not in the example list. However, the rules say "e.g." so it's allowed. I'll do:
- About the role
- Benefits
- Responsibilities
- Qualifications
- Physical Requirements
- Skills
But that's many sections. Could combine Qualifications and Physical Requirements into one "Requirements" section. The example headings include "Requirements" and "Qualifications". They might be synonymous. I'll use "Qualifications" for the qualifications/competencies and "Requirements" for physical requirements? Or just "Requirements" for both. Let's see the posting: "Qualifications And Competencies" and "Physical Requirements". I'll create a "Qualifications" section for the first, and a "Physical Requirements" section for the second. That's fine.
Now, "You'll thrive at IPS if you..." is a list of attributes. That's "Skills" or "Qualities". I'll use "Skills".
Now, remove boilerplate: The last paragraph about EEO, background check, drug screen is boilerplate. Remove.
Also, "IPS is committed to equal employment opportunity..." etc. Remove.
Now, write HTML.
Let's start:
About the role
for section headings. Not sure about h4. Safer to make separate h3 sections: "Qualifications" and "Physical Requirements". But "Physical Requirements" is not in the example list. However, the rules say "e.g." so it's allowed. I'll do:
- About the role
- Benefits
- Responsibilities
- Qualifications
- Physical Requirements
- Skills
But that's many sections. Could combine Qualifications and Physical Requirements into one "Requirements" section. The example headings include "Requirements" and "Qualifications". They might be synonymous. I'll use "Qualifications" for the qualifications/competencies and "Requirements" for physical requirements? Or just "Requirements" for both. Let's see the posting: "Qualifications And Competencies" and "Physical Requirements". I'll create a "Qualifications" section for the first, and a "Physical Requirements" section for the second. That's fine.
Now, "You'll thrive at IPS if you..." is a list of attributes. That's "Skills" or "Qualities". I'll use "Skills".
Now, remove boilerplate: The last paragraph about EEO, background check, drug screen is boilerplate. Remove.
Also, "IPS is committed to equal employment opportunity..." etc. Remove.
Now, write HTML.
Let's start:
About the role
If you're searching for a place where you can grow, continue learning, and make a meaningful impact while still having time for the people and moments that matter most, welcome to Integrated Power Services! We believe your value extends far beyond your job title because the best work comes from people who feel supported, challenged, and fulfilled both professionally and personally. Here, you'll find opportunities to develop your career, work alongside exceptional teammates, and be part of a culture that recognizes that your life is worth just as much as your work—if not more. Because when people thrive, businesses thrive. If that sounds like the kind of place you've been looking for, we invite you to join us!
At IPS, we're committed to empowering you to make a meaningful impact. As the industry's leading and fastest-growing service provider, IPS offers single-source electromechanical and power management solutions to enhance the reliability of critical infrastructure across North America and the United Kingdom. We serve over 40,000 essential customer locations, from renewable energy pioneers to hospitals, manufacturers, and municipalities, helping them avoid costly downtime and ensure mission-critical operations. When you join IPS, you're joining a team that's revolutionizing equipment and process reliability across diverse sectors, from power generation to petrochemicals, and beyond. You'll learn from industry experts, grow alongside a talented workforce, and be part of a company that is built on the Shared Values of Safety, Integrity, Teamwork, Accountability, Customer Focus, and Entrepreneurial Spirit.
Benefits
- Paid Time Off (PTO)
- 401k Employer Match
- Bonus Incentives
- Extensive Training & Career Development Programs
- Tuition Reimbursement Program
- Medical, Dental and Vision plans
- Employee Assistance Program (EAP)
- And more!
Responsibilities
- Inspect, test, troubleshoot, perform start-up and collect data of low, medium and high voltage (to 500kV) electrical systems, and moderately complex relay calibration and power metering.
- Instrument transformer tests
- Power transformer testing - Doble, TTR, Insulation Resistance, etc.
- Test both electro-mechanical and solid state relays
- Cable testing - Tan Delta, Power Factor, VLF, DC Hipot
- Automatic transfer switch troubleshooting
- Low, Medium and High voltage switchgear and circuit breaker testing
- Rotate emergency on-call duty and if called respond to customer emergencies in a timely manner
- Strong verbal and written communication skills
- Must have a valid Driver’s License and acceptable driving record
- Ability to travel locally and overnight
- Ability to work flexible hours, overtime and weekends as required, willingness to be on call
- Work safely alone and as part of a team
- Closely adhere to all electrical safety procedures
- Effectively contributes to a strong team environment through assisting teammates in accomplishing mutual goals
Qualifications
- High school diploma or equivalent required
- Associate degree from an accredited 2-year technical college in Electrical Power, or similar experience/training from the military (Army Prime Power, Air Force Electrical Power Production, or NAVY Seabee) preferred
- Must have at least 5 or more years of relevant experience
- NETA Certification II or higher preferred or equivalent skills/experience to become NETA Certified
- Prefer OSHA 30 hour, MSHA, NFPA 70-E, CPR/First Aid/BBP