Protection & Control Field Services Engineer / Technician
for 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 as headings; can fold minor metadata into short
or drop it. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Do not invent or summarize away detail. Must not include sections with filler like "commensurate with experience", "not specified", etc. So we need to extract actual content. Let's parse the posting. Job Summary: description about role, location, responsibilities, safety, etc. Education Requirements: list of education options. Preferred Experience: bullet list. Preferred Knowledge, Skills, And Abilities: bullet list. Requirements: list of requirements (driver's license, computer programs, callout rotation, overnight travel, safety sensitive, hybrid position requiring physical ability, must live in or willing to relocate within reasonable distance to Ponce and Conyers TMC and Northern TMA coverage area (list of cities), must pass background check, drug screen, NERC background check.) Job Responsibilities: bullet list. Behavioral Attributes: bullet list. Required: about Georgia Power fleet vehicle: must have at least one year verifiable driving experience, no revocation, no major traffic violations, consent to continuous monitoring of MVR. Then company description about Georgia Power and Southern Company (maybe considered boilerplate? It's about company, but might be considered substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description may be considered boilerplate? It's not EEO, but it's generic marketing. Might be considered boilerplate; but we need to preserve all substantive information. The company description may be considered not essential to job specifics. However, the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about the employer, but maybe it's considered boilerplate? The examples of boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning. Company description is not those. But it's also generic marketing; but it's still part of posting. I'd keep it as a short paragraph maybe under a section like "About the Company" but we only have allowed headings list; we could put it under "About the role"? Actually "About the role" is allowed heading. Could include summary of role and company info there. But we must not create sections like "About the Company" unless it's in allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have: - About the role: could include job summary (position based in Metro East Transmission Maintenance Center, responsibilities, safety, etc.) - Responsibilities: job responsibilities list. - Requirements: includes education requirements, experience, knowledge, skills, driver's license, etc. Might need to split into Requirements and Qualifications and Skills as separate sections if content exists. We have Education Requirements (list). Preferred Experience (list). Preferred Knowledge, Skills, And Abilities (list). Requirements (list of specific mandatory items). Behavioral Attributes (list). Required (driving record). Could map: - Qualifications: education requirements (maybe also preferred experience? but that's experience). Could treat Qualifications as education + preferred experience? But we need to avoid thin sections. Perhaps combine Education and Experience into Qualifications. - Skills: Preferred Knowledge, Skills, And Abilities + Behavioral Attributes? Might be separate. But we must not create sections with filler. If we create Qualifications, we need actual content. Let's decide sections: - About the role: job summary paragraph. - Responsibilities: job responsibilities list. - Requirements: mandatory requirements (driver's license, computer programs, callout rotation, overnight travel, safety sensitive, hybrid position physical ability, relocation, background checks). Also maybe include "Must possess ability to solve problems and make decisions while managing projects with multiple priorities" (that's more skill). But we can include. - Qualifications: education requirements (list) + preferred experience (list) maybe. - Skills: preferred knowledge, skills, abilities (list) + behavioral attributes (list) maybe. - Benefits: The posting mentions benefits link but no detail; says "A summary of the benefits offered for this position can be found here ..." and "Additional and specific details about total compensation and benefits will also be provided during the hiring process." No actual benefit details given. So we should NOT create Benefits section because no specific content. - Pay: The posting says "pay and level commensurate with the qualifications, education, and experience of the successful candidate." That's filler "commensurate with experience" - we should not create Pay section because it's not specific. - Schedule: The posting says "Job Schedule: Full time" near the end. That's specific: Full time. So we can create Schedule section with that. Also we have "Job Identification: 21683 Job Category: Engineering Job Schedule: Full time Company: Georgia Power". We can fold Job ID etc into a short
maybe under About the role or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with that metadata. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
About the role
... summary ...
Job Identification: 21683 | Job Category: Engineering | Company: Georgia Power
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- 4-year Bachelor’s Degree in Engineering, or
- 4-year BS Degree in Engineering Technology, or
- Professional Engineering License, or
- 2-year technical degree in electrical maintenance, or
- Equivalent applicable experience (Examples: Electrician, Technician, Wireman, HVAC, etc.)
Preferred Experience:
- P&C Field Services experience
- Electric power utility transmission construction, maintenance, or operations experience
- Experience related to P&C Applications, Design, Construction, Major Electrical Equipment, Project Management, etc.
- Experience standing by to respond to abnormal conditions 24 hours / 7 days
Skills
- Knowledge of 3-phase power systems, AC/DC Protection & Control Schemes, Fault Analysis
- Familiar with test equipment such as voltmeters, ammeters, ohmmeters, communications instruments, and computerized relay test sets.
- Ability to communicate across multiple work groups including customers, covered employees, and leadership
- Ability to solve problems and make decisions while managing projects with multiple priorities
- Familiar with computer programs including but not limited to Microsoft Office products (Word, Teams, Excel, PowerPoint, etc.)