Entry-Level Electrical Engineer
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We need to map content to these headings appropriately.
We have:
- About the role: The Opportunity paragraph: "The Opportunity PAE is seeking a motivated and inquisitive Entry-Level Electrical Engineer to join our team in a hybrid office environment in our San Francisco, CA office. This role is designed for a proactive individual looking to build a career in electrical system design for the built environment. Under the mentorship of experienced project leads, you will transition from academic theory to professional practice, learning to design and model power distribution, lighting, and technology systems. You will play a foundational role in supporting project teams while developing technical mastery in industry-standard software and electrical codes."
- Responsibilities: "What You'll Do" list: bullet points.
- Requirements/Qualifications/Skills: "What You Bring" includes Bachelor's degree, EIT, internship preferred, ability to develop understanding of Revit/AutoCAD, strong analytical skills, strategic thinking, passionate about results, organization, clear communication, attention to detail, time management, Microsoft Office Suite, Easy Power. Could separate into Requirements (education, certification) and Skills (software, soft skills). But we can combine into one section maybe "Qualifications" or "Skills". The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content.
We have Pay: "Hiring Base Salary Range: $81,700 - $98,700 annual". Also mention overtime eligibility. So we can have Pay section.
Benefits: "What We Offer" includes benefits list. So Benefits section.
Schedule: "Hybrid work schedule" mentioned. So Schedule section.
We also have "Who We Are" maybe could be About the company, but not required headings. Could incorporate into About the role? But we have "About the role" heading for role description. Could also add a section "About the Company" but not in allowed headings. Probably we should not add extra headings beyond allowed list. So we can put company description maybe under About the role? But that might be mixing. However instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings, but better to stick to those. We can include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: The opportunity paragraph (maybe also include hybrid office location). Could also include "Who We Are"? Might be better to put company description under About the role? But that heading is about the role, not company. However we could add a short paragraph about the company under About the role as context. It's okay.
Responsibilities: list from "What You'll Do".
Requirements: education and certification: Bachelor's degree in electrical engineering, Engineer in Training (E.I.T.) or ability to obtain, internship experience preferred.
Qualifications: maybe technical skills: ability to develop understanding of Revit/AutoCAD, Microsoft Office Suite, Easy Power.
Skills: soft skills: strong analytical skills, strategic thinking, passionate about results, organization, clear communication, attention to detail, time management.
Benefits: list from "What We Offer": employer paid health insurance, annual 401k profit sharing, professional development reimbursements, employer paid commuter/parking stipend, cell phone stipend, life insurance and disability benefits, hybrid work schedule (but schedule separate), Employee Assistance Program, 9 paid holidays including additional employee-selected day, paid time off for sick leave, family leave, community service, holidays and vacation.
Pay: base salary range, overtime eligibility.
Schedule: hybrid work schedule (maybe also mention hybrid office environment). Could also mention location San Francisco, CA.
We must not include boilerplate like Fine Print, EEO, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "To learn more about our comprehensive benefits package, visit ..." maybe that's okay as part of benefits? It's a link; but it's not boilerplate? It's a reference; could keep but it's not essential. Might be considered not boilerplate but it's a link; we could keep as part of benefits paragraph. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not those; it's okay.
Also remove "This information is provided per the Equal Pay Act" etc. That's legal boilerplate; remove.
Also remove "Our commitment to pay equity" etc. That's also legal/EEO; remove.
Also remove "What We’re Made Of" maybe not needed as heading; but could be considered company description; we could incorporate into About the role or maybe omit. Since we have limited headings, we could omit that section.
We need to preserve all substantive information; not invent or summarize away detail. So we must keep all details from sections we include.
Let's extract details:
About the role (Opportunity):
- PAE seeking motivated and inquisitive Entry-Level Electrical Engineer.
- Hybrid office environment in San Francisco, CA office.
- Role designed for proactive individual looking to build career in electrical system design for built environment.
- Under mentorship of experienced project leads, transition from academic theory to professional practice, learning to design and model power distribution, lighting, and technology systems.
- Play foundational role in supporting project teams while developing technical mastery in industry-standard software and electrical codes.
Who We Are (company description) maybe we can incorporate but not required; but we might lose substantive info if we omit. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description info somewhere. If we don't have a heading for it, we could include it as a paragraph under About the role or maybe under a separate heading like "About the Company" but not in allowed list. However we could add a heading "About the Company" but not in the list; risk of violating instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we could add other headings if needed, but better to stick to those to be safe. However we need to preserve company description; we could put it under About the role as a paragraph preceding role details. That would still preserve it.
Thus About the role section will contain both company description and role details.
Now Responsibilities: list from "What You'll Do". Let's capture each bullet:
- Develop an understanding of electrical system design, modeling and documentation
- Develop proficiency using Revit and AutoCAD as design/drafting tools
- Grow in the ability to read plans
- Provide task-based support for engineering distribution, lighting, power, and technology systems
- Develop an understanding of specifications, building codes and electrical industry standards
- Complete assigned work with instruction from project team members
- Model distribution Load Flow, Short Circuit and Arc Flash Energy using Easy Power
- Perform electrical load calculations
- Research codes and undertake code compliance analysis
- Perform other duties as assigned
We need to put each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we could add other headings if needed, but better to stick to those to be safe. However we need to preserve company description; we could put it under About the role as a paragraph preceding role details. That would still preserve it. Thus About the role section will contain both company description and role details. Now Responsibilities: list from "What You'll Do". Let's capture each bullet: - Develop an understanding of electrical system design, modeling and documentation - Develop proficiency using Revit and AutoCAD as design/drafting tools - Grow in the ability to read plans - Provide task-based support for engineering distribution, lighting, power, and technology systems - Develop an understanding of specifications, building codes and electrical industry standards - Complete assigned work with instruction from project team members - Model distribution Load Flow, Short Circuit and Arc Flash Energy using Easy Power - Perform electrical load calculations - Research codes and undertake code compliance analysis - Perform other duties as assigned We need to put each as
- .
Requirements: Bachelor’s degree in electrical engineering for discipline work; Engineer in Training (E.I.T.) or ability to obtain; Internship experience preferred.
Qualifications: Ability to develop an understanding of Revit/AutoCAD; Microsoft Office Suite; Easy Power.
Skills: Strong analytical skills, strategic thinking; Passionate about results; Organization; Clear communication; Attention to detail; Time management.
Benefits: list from "What We Offer":
- Employer paid health insurance (medical, dental, vision)
- Annual 401k profit sharing based on company profit for the year and account contribution
- Professional development reimbursements including state registration and professional association dues
- Employer paid commuter/parking stipend
- Cell phone stipend
- Life insurance and disability benefits
- Hybrid work schedule (but we have schedule separate; maybe we still include here? Could mention hybrid work schedule as part of benefits but we also have schedule section. To avoid duplication, we could keep hybrid work schedule only in Schedule section. But benefits list includes it; we could still include but note it's also schedule. However we must preserve all substantive information; we can include it in both places? That would be duplication. Better to keep it only in Schedule section and not duplicate in Benefits. But then we would be omitting that piece from Benefits. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we omit hybrid work schedule from Benefits, we lose that detail unless we put it elsewhere. We can put it in Schedule section, which is allowed. So we can keep hybrid work schedule only under Schedule, and not duplicate in Benefits. That preserves the info.
- Employee Assistance Program
- 9 paid holidays including an additional employee-selected day
- Paid time off for sick leave, family leave, community service, holidays and vacation
Also mention "To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits." Could keep as a sentence.
Pay: Hiring Base Salary Range: $81,700 - $98,700 annual; This position is eligible for time and a half overtime pay; base salary component of compensation package; factors considered; annual compensation reviews; range represents good faith estimate.
Schedule: Hybrid work schedule; also mention hybrid office environment in San Francisco, CA (maybe location). Could also mention location San Francisco, CA.
We must not include boilerplate like "This information is provided per the Equal Pay Act" etc. Also remove "Our commitment to pay equity" etc. Also remove "What We’re Made Of" maybe we incorporated.
Now produce HTML fragment with
- .
We must not include or . Just fragment.
Let's craft:
About the role
PAE is an engineering and design firm that turns complex challenges into reality, leveraging latest technologies to solve problems uniquely, enabling buildings and communities to be more resilient and efficient. Trusted by clients from idea to occupancy, PAE sets ambitious goals backed by analysis to significantly conserve water and energy while balancing costs and long-term operational needs. As a B Corp, success is measured by benefits to clients, communities, and the planet, embracing innovation, transparency, sustainability, and lifelong curiosity.
PAE is seeking a motivated and inquisitive Entry-Level Electrical Engineer to join our team in a hybrid office environment in our San Francisco, CA office. This role is designed for a proactive individual looking to build a career in electrical system design for the built environment. Under the mentorship of experienced project leads, you will transition from academic theory to professional practice, learning to design and model power distribution, lighting, and technology systems. You will play a foundational role in supporting project teams while developing technical mastery in industry-standard software and electrical codes.
Responsibilities
- Develop an understanding of electrical system design, modeling and documentation
- Develop proficiency using Revit and AutoCAD as design/drafting tools
- Grow in the ability to read plans
- Provide task-based support for engineering distribution, lighting, power, and technology systems
- Develop an understanding of specifications, building codes and electrical industry standards
headings and appropriate
or