Sr Electrical Engineer – Federal Experience
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Company Description: not needed? It's part of description but not a heading. We can include maybe as a
under "About the role"? Actually "About the role" heading is for role description. The posting includes "Job Description" and "Summary". We can treat that as responsibilities. We need to extract responsibilities list: bullet points under Summary: Leading or assisting with the electrical design..., Developing integrated controls..., Developing and editing product specifications..., Directly interfacing..., Developing designs..., Interpreting..., Creating and supervising..., Performing Power Systems Studies..., Conducting electrical surveys..., Performing quality control review..., Providing guidance..., Preparing and reviewing..., Performing construction administration tasks... These are duties. Use
- .
Qualifications: Minimum Requirements: Bachelor's Degree..., 8 years..., US Citizenship required, Valid US Driver's License, pass motor vehicle records review.
Preferred Qualifications: list many items.
We can combine into Requirements section? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which headings to use.
We have responsibilities (duties). We have qualifications (minimum and preferred). We have skills (maybe from preferred qualifications like communication, MS office, etc). We have Pay (range given). Benefits: described in "About AECOM" paragraph about benefits. Also "Additional Information" includes Day 1 onboarding etc but not benefits. Benefits paragraph: "AECOM is proud to offer comprehensive benefits...". So we can include Benefits section.
Schedule: Not mentioned explicitly; maybe hybrid work model mentioned later: "Work Location Model: Hybrid". That's schedule? Could be considered schedule? It's work location model. Not exactly schedule (like full-time, part-time). Probably we should not create Schedule section unless explicit schedule info. The posting does not give hours. So omit Schedule.
Pay: we have compensation range: $160,000 to $200,000 yearly. Also later "Compensation: USD 160000 - USD 200000 - yearly". So we can include Pay section.
About the role: maybe we can include a short paragraph summarizing role from Job Description/Summary. Could be under "About the role". The instruction: do NOT repeat the job title as a heading. So we can have
About the role
with a paragraph summarizing. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from responsibilities, qualifications, etc. We can't omit details. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Remove EEO statements etc. The posting includes "As an Equal Opportunity Employer..." etc. Remove that. Also remove "ReqID: J10160258 Business Line: ..." etc. That's metadata; we can drop or fold into short p. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. So we can drop them. We need to output only HTML fragment, no /, no markdown. Let's craft:
About the role
AECOM is seeking a creative and highly talented Senior Electrical Power Systems Engineer - Federal for immediate employment in our Dallas or Houston, TX office. The role involves leading or assisting with electrical design of power distribution infrastructure, medium and low voltage power, lightning protection, and grounding systems for DoD and Mission Critical Facility projects.
But we need to preserve all substantive info; maybe better to keep responsibilities list separate under Responsibilities heading, and About the role can be a brief summary. Responsibilities: list all bullet points. Qualifications: maybe split into Minimum Requirements and Preferred Qualifications under Requirements heading? Or we could have Requirements heading for minimum, and Qualifications heading for preferred? The instruction list includes both Requirements and Qualifications as possible headings. We can use Requirements for minimum, Qualifications for preferred (or vice versa). Let's decide: UseRequirements
for minimum requirements (Bachelor's, 8 years, US Citizenship, Driver's License, MVR review). UseQualifications
for preferred qualifications list. Skills: maybe extract from preferred qualifications: Effective written and verbal communication skills, Proficiency with MS office applications, Ability to prioritize multitask plan adapt and self-initiate tasks in a fast-paced environment with minimal supervision, etc. Could be under Skills. But we might combine some. However we need to avoid thin sections. Let's see if we have enough content for each. Responsibilities: many bullets -> good. Requirements (minimum): Bachelor's Degree, 8 years experience, US Citizenship, Valid US Driver's License, pass AECOM's motor vehicle records review. That's decent. Qualifications (preferred): many items: Professional Engineer's license, 15+ Years of Experience, Experience with spot networks and micro-grid systems, lighting design, and electrical commissioning, Experience in development of A/E services proposals, Experience working in a time-sensitive environment with direct client interface and high-level accountability, Effective written and verbal communication skills, Proficiency with MS office applications, Ability to prioritize multitask plan adapt and self-initiate tasks in a fast-paced environment with minimal supervision, Telecommunications design experience including telecommunications network, A/V, and electronic security design in DoD and mission critical projects, Knowledge of and experience with Department of Defense requirements including Unified Facilities Criteria (UFC) and the National Electric Code. That's a good list. Skills: maybe we could pull out communication, MS office, prioritization, etc. But those are already in preferred qualifications. Could create Skills section for those soft skills. However we might duplicate content. Better to keep them under Qualifications (preferred) and not create separate Skills to avoid thin section. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine preferred qualifications and skills into one Qualifications section. But we already have Requirements (minimum) and Qualifications (preferred). That's two sections. Could also have Skills separate but risk thin. We also have Benefits section: paragraph about benefits. Pay section: compensation range. We might also have About the role section: short summary. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any content missing: Work Location Model: Hybrid - could be included under About the role or maybe as a note. Could add a short p under About the role mentioning hybrid work model in Dallas or Houston. We need to preserve all substantive info: The job location (Dallas or Houston, TX office) and hybrid model. Include that. Also note "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's part of pay description; we can include in Pay section. Now ensure we don't include boilerplate: Remove EEO, etc. Also remove "Additional Information" about Day 1 onboarding? That's not boilerplate but it's a condition of employment. Could be included maybe under Requirements? It's a condition: "all newly hired employees are required to attend an in-person Day 1 onboarding at an AECOM office location as a condition of employment." That's substantive; we could include under Requirements or a separate section like "Additional Information". But we don't have a heading for that; we could fold into Requirements or maybe under About the role. Probably include under Requirements as a condition. Also "Due to the nature of this work, US Citizenship is required." Already in Requirements. Now craft HTML. We need to usefor section headings. Use
- for lists. Use
for prose. Let's draft:
About the role
AECOM is seeking a Senior Electrical Power Systems Engineer – Federal for immediate employment in the Dallas or Houston, TX office, working in a hybrid model. The role involves leading or assisting with the electrical design of power distribution infrastructure, medium and low voltage power, lightning protection, and grounding systems for DoD and Mission Critical Facility projects.
Responsibilities
- Leading or assisting with the electrical design of power distribution infrastructure, medium and low voltage power, lightning protection, and grounding systems for DoD, and Mission Critical Facility projects.
- Developing integrated controls sequences and schematics for power distribution equipment.
- Developing and editing product specifications for power distribution equipment and electrical components.
- Directly interfacing with client SMEs for coordination of power systems components, controls, and integration.
- Developing designs from site assessments and concept design through a project lifecycle to final design.
- Interpreting and implementing client requirements into code‑compliant designs.
- Creating and supervising the development of electrical plans and details with the use of Revit or AutoCAD.
- Performing Power Systems Studies through creation of electrical models in SKM (or similar software).
- Conducting electrical surveys (onsite) and site visits during construction.
- Performing quality control review of electrical engineering design.
- Providing guidance to entry level engineers.
- Preparing and reviewing design and construction cost estimates for electrical scopes of work.
- Performing construction administration tasks including shop drawing and RFI reviews.
Requirements
- Bachelor's Degree in Electrical Engineering, Electrical Engineering Technology or related field.
- 8 years of relevant electrical power system design experience (or demonstrated equivalency of experience and/or education).
- US Citizenship is required.
- Valid US Driver's License.
- Must pass AECOM's motor vehicle records review.
- All newly hired employees must attend an in‑person Day 1 onboarding at an AECOM office location as a condition of employment.
Qualifications
- Professional Engineer's license.
- 15+ years of experience.
- Experience with spot networks and micro‑grid systems, lighting design, and electrical commissioning.
- Experience in development of A/E services proposals.
- Experience working in a time‑sensitive environment with direct client interface and high‑level accountability.
- Effective written and verbal communication skills.
- Proficiency with MS Office applications.
- Ability to prioritize, multitask, plan, adapt, and self‑initiate tasks in a fast‑paced environment with minimal supervision.
- Telecommunications design experience including telecommunications network, A/V, and electronic security design in DoD and mission critical projects.
- Knowledge of and experience with Department of Defense requirements including Unified Facilities Criteria (UFC) and the National Electric Code.
Benefits
AECOM offers comprehensive benefits that may include medical, dental, vision, life, AD&D, disability benefits, paid time off, leaves of absence, voluntary benefits, perks, flexible work options, well‑being resources, employee assistance program, business travel insurance, service recognition awards, retirement savings plan, and employee stock purchase plan.
Pay
The offered rate of compensation will be based on individual education, qualifications, experience, and work location. The salary range for this position is $160,000 to $200,000 per year.
Check for any duplicated content: We have responsibilities list includes all bullet points from summary. Good. We omitted "Developing integrated controls sequences and schematics for power distribution equipment." included.
- for lists. Use