Transmission Line Engineer 3 - Grid
Sargent & Lundy · Warrenville, IL · 1 mo ago
Engineering$74k–$114k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title heading. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info.
Let's parse the posting.
Content:
- Hybrid work schedule: "This position allows for a hybrid work schedule with a mix of work spent in office and working remote from home."
- Role description: "This Position Will Offer You The Ability To Directly Apply Your Knowledge Of Transmission Line Engineering Including, Conductors, Hardware, Insulation, Structures, Foundations And Electrical Principles To Design transmission lines in the 69kV to 765kV range. Perform structural analysis and design of pole, lattice, framed, and guyed structures. Perform foundation designs. Perform conductor selection studies, shielding, grounding and induction studies. Develop cost estimates and schedules and prepare specifications for the procurement of transmission line materials and construction. Specify transmission line components. Model transmission lines in PLS-CADD, determine right of way requirements, calculate conductor sags, and develop transmission line plan and profile drawings. Review vendor submittals."
- Qualifications: "We do not sponsor employees for work authorization in the U.S. for this position." (That's a note, maybe part of Qualifications? It's under "Qualifications" heading in original.)
- Essential Skills And Experience: list: degree from ABET-accredited engineering program; related engineering, internship or co-op work experience; proficiency with PLS-CADD and PLS-POLE; three or more years related experience in transmission line engineering; knowledge of practical application of engineering principles including basic transmission line engineering; knowledge of design techniques, tools, and principles involved in production of technical plans, drawings, and models; proficiency with MS Office applications; excellent written and verbal communication skills.
- Valued But Not Required Skills And Experience: list: successful completion of FE exam, Engineer in Training; proficiency with any of the following programs: PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation; experience in writing and providing support documentation for engineering calculations; familiarity with design codes and standards such as NESC, IEC, CSA, IEEE, ANSI, IBC, ASCE 7, AISC, and ACI 318.
- Technology & Innovation: paragraph about using tech, AI, automation valued but not required.
- About Sargent & Lundy: health and well-being, healthcare plans, paid time off, work-life balance, award-winning benefits, Top Workplaces Culture Excellence Award for compensation and benefits 2022-2024.
- Then list of benefits: Health & Wellness, Financial Benefits, Work-Life Balance, then bullet list: Health Plans: Medical, Dental, Vision; Life & Accident Insurance; Disability Coverage; Employee Assistance Program (EAP); Back-Up Daycare; FSA & HSA; 401(k) Pre-Tax Commuter Account; Merit Scholarship Program; Employee Discount Program; Corporate Charitable Giving Program; Tuition Assistance; First Professional Licensure Bonus; Employee Referral Bonus; Paid Annual Personal/Sick Time (PST); Paid Vacation; Paid Holidays; Paid Parental Leave; Paid Bereavement Leave; Flexible Work Arrangements.
- Compensation Range: $74,353 - $113,595
- Transparency Statement: about compensation ranges.
- Equal Opportunity boilerplate: remove.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: maybe the hybrid work schedule and description of role? Could be a short paragraph summarizing role.
Responsibilities: list of duties: design transmission lines, structural analysis, foundation designs, conductor selection studies, shielding, grounding, induction studies, develop cost estimates and schedules, prepare specs, specify components, model in PLS-CADD, determine ROW, calculate sags, develop plan/profile drawings, review vendor submittals.
Requirements: maybe the essential skills/experience that are required: degree from ABET-accredited engineering program; related engineering internship/co-op; proficiency with PLS-CADD and PLS-POLE; three+ years related experience; knowledge of practical application; knowledge of design techniques; proficiency with MS Office; excellent written/verbal communication.
Qualifications: maybe the "We do not sponsor employees for work authorization in the U.S."? Also maybe the "Essential Skills And Experience" could be qualifications. But we need to avoid duplication. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills)." So we can have those sections.
We need to include only sections with real specific content. So we need to decide content for each.
Potential mapping:
- About the role: hybrid work schedule + brief overview of role (ability to apply knowledge, design transmission lines 69kV-765kV). Could be a paragraph.
- Responsibilities: bullet list of duties as above.
- Requirements: maybe the essential required skills/experience (degree, experience, proficiency, etc.)
- Qualifications: maybe the "Valued But Not Required Skills And Experience" plus "Technology & Innovation" (valued but not required). Or we could treat Qualifications as the required qualifications (like degree, experience) and Skills as the valued but not required plus tech. But we already have Requirements for required. So Qualifications could be the valued but not required (FE exam, other programs, design codes). Or we could swap.
- Skills: maybe the technical skills like proficiency with PLS-CADD, PLS-POLE, MS Office, communication, etc. But those are already in Requirements. Hmm.
We need to avoid duplication. Let's think: The posting has "Essential Skills And Experience" (required) and "Valued But Not Required Skills And Experience" (preferred). Also "Technology & Innovation" (valued but not required). So we could map:
- Requirements: Essential Skills And Experience (required).
- Qualifications: Valued But Not Required Skills And Experience (preferred) + Technology & Innovation (valued but not required) maybe combined.
- Skills: maybe we could list specific technical skills like proficiency with PLS-CADD, PLS-POLE, MS Office, etc. But those are already in Requirements. Could instead put "Skills" as the list of software/programs: PLS-CADD, PLS-POLE, PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation, etc. But that duplicates.
Better: Use "Skills" for the list of technical/program proficiencies (both required and valued). "Requirements" for education/experience. "Qualifications" for certifications like FE exam, design codes familiarity. But we need to ensure we don't repeat.
Let's extract data:
Required (Essential Skills And Experience):
- Degree from ABET-accredited engineering program.
- Related engineering, internship or co-op work experience.
- Proficiency with PLS-CADD and PLS-POLE.
- Three or more years related experience in transmission line engineering.
- Knowledge of practical application of engineering principles including basic transmission line engineering.
- Knowledge of design techniques, tools, and principles involved in production of technical plans, drawings, and models.
- Proficiency with MS Office applications.
- Excellent written and verbal communication skills.
Valued But Not Required:
- Successful completion of FE exam, Engineer in Training.
- Proficiency with any of: PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation.
- Experience in writing and providing support documentation for engineering calculations.
- Familiarity with design codes and standards such as NESC, IEC, CSA, IEEE, ANSI, IBC, ASCE 7, AISC, ACI 318.
Technology & Innovation:
- Interest in learning and using emerging technologies (AI, automation, programming) valued where relevant but not required unless specified.
About Sargent & Lundy benefits: list.
Compensation Range: $74,353 - $113,595.
Schedule: hybrid work schedule (mix office/remote). Could be under Schedule section.
Now, we need to output HTML fragment with headings
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills)." So we can have those sections.
We need to include only sections with real specific content. So we need to decide content for each.
Potential mapping:
- About the role: hybrid work schedule + brief overview of role (ability to apply knowledge, design transmission lines 69kV-765kV). Could be a paragraph.
- Responsibilities: bullet list of duties as above.
- Requirements: maybe the essential required skills/experience (degree, experience, proficiency, etc.)
- Qualifications: maybe the "Valued But Not Required Skills And Experience" plus "Technology & Innovation" (valued but not required). Or we could treat Qualifications as the required qualifications (like degree, experience) and Skills as the valued but not required plus tech. But we already have Requirements for required. So Qualifications could be the valued but not required (FE exam, other programs, design codes). Or we could swap.
- Skills: maybe the technical skills like proficiency with PLS-CADD, PLS-POLE, MS Office, communication, etc. But those are already in Requirements. Hmm.
We need to avoid duplication. Let's think: The posting has "Essential Skills And Experience" (required) and "Valued But Not Required Skills And Experience" (preferred). Also "Technology & Innovation" (valued but not required). So we could map:
- Requirements: Essential Skills And Experience (required).
- Qualifications: Valued But Not Required Skills And Experience (preferred) + Technology & Innovation (valued but not required) maybe combined.
- Skills: maybe we could list specific technical skills like proficiency with PLS-CADD, PLS-POLE, MS Office, etc. But those are already in Requirements. Could instead put "Skills" as the list of software/programs: PLS-CADD, PLS-POLE, PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation, etc. But that duplicates.
Better: Use "Skills" for the list of technical/program proficiencies (both required and valued). "Requirements" for education/experience. "Qualifications" for certifications like FE exam, design codes familiarity. But we need to ensure we don't repeat.
Let's extract data:
Required (Essential Skills And Experience):
- Degree from ABET-accredited engineering program.
- Related engineering, internship or co-op work experience.
- Proficiency with PLS-CADD and PLS-POLE.
- Three or more years related experience in transmission line engineering.
- Knowledge of practical application of engineering principles including basic transmission line engineering.
- Knowledge of design techniques, tools, and principles involved in production of technical plans, drawings, and models.
- Proficiency with MS Office applications.
- Excellent written and verbal communication skills.
Valued But Not Required:
- Successful completion of FE exam, Engineer in Training.
- Proficiency with any of: PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation.
- Experience in writing and providing support documentation for engineering calculations.
- Familiarity with design codes and standards such as NESC, IEC, CSA, IEEE, ANSI, IBC, ASCE 7, AISC, ACI 318.
Technology & Innovation:
- Interest in learning and using emerging technologies (AI, automation, programming) valued where relevant but not required unless specified.
About Sargent & Lundy benefits: list.
Compensation Range: $74,353 - $113,595.
Schedule: hybrid work schedule (mix office/remote). Could be under Schedule section.
Now, we need to output HTML fragment with headings for each section we include.
We must not include empty sections.
Thus we will include:
About the role
with paragraph about hybrid schedule and role description.
Responsibilities
with - list of duties.
Requirements
with - list of required essential skills/experience.
Qualifications
with - list of valued but not required skills/experience (FE exam, other programs, writing support docs, design codes familiarity) plus maybe technology & innovation (interest in emerging tech). Could combine.
Skills
maybe we could list technical software proficiencies (both required and valued) as a list. But we already have required proficiency with PLS-CADD and PLS-POLE in Requirements, and valued proficiency with other programs in Qualifications. To avoid duplication, maybe we put Skills as a list of all software/programs: PLS-CADD, PLS-POLE, PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation. Also maybe MS Office? Could be considered skill. But we already have MS Office in Requirements. Might be okay to duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication might be okay if it's present in both places? But we should avoid unnecessary duplication. However, we could keep MS Office under Requirements and not repeat in Skills. For Skills, we could list the other programs.
Alternatively, we could omit Skills section entirely if we feel it's covered elsewhere. But the instruction says prefer a few substantive sections over many thin ones. We could omit Skills if it's redundant. However, we have a section for Skills in the list of possible headings; we are not required to include it. So we can omit if no specific content beyond what's already covered. But we have specific content: proficiency with PLS-CADD and PLS-POLE (required) and proficiency with other programs (valued). That is substantive. Could be placed under Skills. Then Requirements could focus on education/experience and communication skills. Qualifications could focus on certifications and design codes. Let's try that.
Thus:
- About the role: hybrid schedule + brief role description.
- Responsibilities: duties list.
- Requirements: education (ABET degree), related experience (internship/co-op), years of experience (3+), proficiency with MS Office, excellent written/verbal communication.
- Qualifications: maybe the FE exam, Engineer in Training, familiarity with design codes, experience writing support documentation.
- Skills: proficiency with PLS-CADD, PLS-POLE, PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation.
- Benefits: list of benefits.
- Pay: compensation range.
- Schedule: hybrid work schedule (maybe we already mentioned in About the role; but we could move schedule to Schedule section and keep About the role more generic). However, the hybrid schedule is substantive; we need to include it somewhere. If we put it in Schedule section, we can still mention hybrid in About the role briefly but not duplicate. Let's decide: About the role could be a short paragraph describing the role (apply knowledge, design lines 69kV-765kV). Schedule section will have hybrid schedule. That avoids duplication.
Thus:
About the role: paragraph: "This position offers the ability to directly apply your knowledge of transmission line engineering including conductors, hardware, insulation, structures, foundations, and electrical principles to design transmission lines in the
About the role
with paragraph about hybrid schedule and role description.Responsibilities
with- list of duties.
Requirements
with- list of required essential skills/experience.
Qualifications
with- list of valued but not required skills/experience (FE exam, other programs, writing support docs, design codes familiarity) plus maybe technology & innovation (interest in emerging tech). Could combine.
Skills
maybe we could list technical software proficiencies (both required and valued) as a list. But we already have required proficiency with PLS-CADD and PLS-POLE in Requirements, and valued proficiency with other programs in Qualifications. To avoid duplication, maybe we put Skills as a list of all software/programs: PLS-CADD, PLS-POLE, PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation. Also maybe MS Office? Could be considered skill. But we already have MS Office in Requirements. Might be okay to duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication might be okay if it's present in both places? But we should avoid unnecessary duplication. However, we could keep MS Office under Requirements and not repeat in Skills. For Skills, we could list the other programs. Alternatively, we could omit Skills section entirely if we feel it's covered elsewhere. But the instruction says prefer a few substantive sections over many thin ones. We could omit Skills if it's redundant. However, we have a section for Skills in the list of possible headings; we are not required to include it. So we can omit if no specific content beyond what's already covered. But we have specific content: proficiency with PLS-CADD and PLS-POLE (required) and proficiency with other programs (valued). That is substantive. Could be placed under Skills. Then Requirements could focus on education/experience and communication skills. Qualifications could focus on certifications and design codes. Let's try that. Thus: - About the role: hybrid schedule + brief role description. - Responsibilities: duties list. - Requirements: education (ABET degree), related experience (internship/co-op), years of experience (3+), proficiency with MS Office, excellent written/verbal communication. - Qualifications: maybe the FE exam, Engineer in Training, familiarity with design codes, experience writing support documentation. - Skills: proficiency with PLS-CADD, PLS-POLE, PLS-TOWER, SAG10, LPILE, MFAD, ArcGIS, CDEGS, AutoCAD, Microstation. - Benefits: list of benefits. - Pay: compensation range. - Schedule: hybrid work schedule (maybe we already mentioned in About the role; but we could move schedule to Schedule section and keep About the role more generic). However, the hybrid schedule is substantive; we need to include it somewhere. If we put it in Schedule section, we can still mention hybrid in About the role briefly but not duplicate. Let's decide: About the role could be a short paragraph describing the role (apply knowledge, design lines 69kV-765kV). Schedule section will have hybrid schedule. That avoids duplication. Thus: About the role: paragraph: "This position offers the ability to directly apply your knowledge of transmission line engineering including conductors, hardware, insulation, structures, foundations, and electrical principles to design transmission lines in the
- list of valued but not required skills/experience (FE exam, other programs, writing support docs, design codes familiarity) plus maybe technology & innovation (interest in emerging tech). Could combine.
- list of required essential skills/experience.