Entry Level Plumbing Design Engineer - San Francisco

We need to output HTML fragment with sections: About the role? Actually the posting includes "The Opportunity", "Who We Are", "What You'll Do", "What You Bring", "What We Offer". Also maybe "What We’re Made Of". According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings. The posting includes responsibilities (What You'll Do), requirements/qualifications (What You Bring), benefits (What We Offer), pay (Hiring Base Salary Range). Also schedule (Hybrid work schedule). Also maybe "About the role" could be from The Opportunity description. "Who We Are" could be about company but not required heading; we could include as About the role? Actually About the role is separate. We could include a short paragraph about the role under

About the role

. Then responsibilities under

Responsibilities

. Qualifications under

Qualifications

(or Requirements). Skills maybe under

Skills

. Benefits under

Benefits

. Pay under

Pay

. Schedule under

Schedule

. Must only include sections when posting has real specific content. We have all. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove "Fine Print" about recruiters, EEO statement, etc. Also remove "To learn more about our comprehensive benefits package, visit ..."? That's part of benefits but we can keep description but maybe drop the link? The rule: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a reference; we could keep as part of benefits description but maybe it's okay to keep. However it's a URL; we can keep as plain text. It's not boilerplate. It's fine. We must not include duplicated lines. Also remove "Our commitment to pay equity" etc? That's part of pay equity description; it's substantive but maybe considered boilerplate? It's about pay equity; could be considered legal/EEO? It's not exactly EEO but it's about pay equity. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The pay equity statement might be considered legal/EEO. Safer to remove it. Also remove "This information is provided per the Equal Pay Act". Also remove "Our commitment to pay equity ...". Also remove "To learn more about pay equity and our commitments to equitable business practices, you may view our JUST label certification here: Living Future: Just Label Certification. To find out more visit our website." That's likely boilerplate. Remove. Also remove "Fine Print" section about recruiters, etc. Remove EEO statement at end. Now construct HTML. We need

About the role

with paragraph summarizing the opportunity: "PAE is seeking a motivated and inquisitive Entry-Level Plumbing Design Engineer to join our San Francisco team in a hybrid office environment. This role is designed for a proactive individual looking to build a career in plumbing 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 plumbing and engineering distribution systems. You will play a foundational role in supporting project teams while developing technical mastery in industry-standard software and plumbing codes." That's from The Opportunity paragraph. Then responsibilities: list items from "What You'll Do". We'll extract each bullet: - Develop an understanding of plumbing system design, modeling and documentation - Develop proficiency using Revit and AutoCAD as design/drafting tools - Provide task-based support for engineering distribution and Plumbing - Develop an understanding of drawings, specifications, building codes, and plumbing design industry standards - Complete assigned work with instruction from project team members - Assist with construction administration - Perform mechanical calculations and performance simulations - Design layout of plumbing systems - Perform other duties as assigned Make

• . Qualifications: from "What You Bring". Items: - Bachelor’s Degree in Engineering for discipline work - Engineer in Training (E.I.T.) or ability to obtain - Internship experience preferred - Revit/AutoCAD - Analytical skills, strategic thinking - Passionate about results - Organization - Clear communication - Attention to detail - Time management - Microsoft Office Suite We could group as qualifications. Skills maybe separate but we can put under Qualifications. But we have a heading for Skills; we could split: Qualifications (education, EIT, internship) and Skills (software, analytical, etc.). However we must not create thin sections; better to have Qualifications covering both education and skills. But we have a separate Skills heading optional. Since we have many skill items, we could create Skills section. But we need to avoid duplication. Let's decide: Use Qualifications for education and EIT/internship. Use Skills for Revit/AutoCAD, analytical skills, etc. That seems reasonable. Thus:

  Qualifications

  • Bachelor’s Degree in Engineering for discipline work
  • Engineer in Training (E.I.T.) or ability to obtain
  • Internship experience preferred

  Skills

  • Revit/AutoCAD
  • Analytical skills, strategic thinking
  • Passionate about results
  • Organization
  • Clear communication
  • Attention to detail
  • Time management
  • Microsoft Office Suite
  Benefits: from "What We Offer". List: - 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 (maybe schedule separate) - 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 - To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits. We could keep the link as part of benefits. Pay: from "What We Offer": Hiring Base Salary Range: $81,700-$98,700 annual. Also mention overtime eligibility. Also base salary component of compensation package. Also mention annual compensation reviews. We'll include that. Schedule: Hybrid work schedule mentioned. We should not duplicate hybrid schedule in both Benefits and Schedule; we can keep hybrid schedule under Benefits as a benefit, and Schedule section maybe just mention hybrid work schedule? But we should not repeat same content. Better to put hybrid schedule under Benefits and not have separate Schedule section, or we could have Schedule section with hybrid work schedule and maybe mention that it's hybrid. Since we already have hybrid schedule in benefits, we could still have Schedule section but risk duplication. The rule: do not repeat duplicated lines. So we should avoid repeating same sentence. We could keep hybrid schedule only in Benefits and not have Schedule section. But the instruction says include a section ONLY when posting has real, specific content for it. It does not require us to include Schedule if we already covered hybrid schedule elsewhere. However they gave example headings including Schedule. It's optional. We'll decide to include Schedule section with hybrid work schedule, but then we need to avoid duplicating the same sentence elsewhere. We could mention hybrid schedule in Benefits as "Hybrid work schedule" and also in Schedule as "Hybrid office environment (hybrid work schedule)". That's duplication of concept but not exact same line. Might be okay but better to avoid duplication. Let's keep hybrid schedule only in Benefits and omit Schedule section. However the user may expect Schedule section because they gave example. But the rule says only include when posting has real specific content for it. The posting does mention hybrid office environment and hybrid work schedule. So we could have Schedule section with that content, and not duplicate in Benefits. Then we can remove hybrid schedule from Benefits list. But benefits list includes many items; we could keep hybrid schedule as a benefit but then it's duplicated. I'd rather keep Benefits without hybrid schedule and put it under Schedule. Let's see: Benefits list originally includes "Hybrid work schedule". If we move it to Schedule, we need to adjust Benefits list accordingly (remove that line). That's fine. Thus Benefits list will exclude hybrid schedule. Schedule section:

  Schedule

  Hybrid office environment (hybrid work schedule)

  Now Pay section: include base salary range, overtime eligibility, compensation reviews. Let's craft Pay paragraph: "Hiring Base Salary Range: $81,700–$98,700 annual. This position is eligible for time and a half overtime pay. The base salary is one component of PAE’s competitive compensation package; exact salary is determined by skills, abilities, experience, education, credentials, internal equity, and geographic location. Employees are eligible for annual compensation reviews based on performance and business needs." Now Benefits list without hybrid schedule. Now About the role paragraph. Now Responsibilities list. Now Qualifications list. Now Skills list. Now Benefits list. Now Schedule paragraph. Now we must ensure no boilerplate: removed EEO, legal, fine print, JUST label, etc. Check for any leftover boilerplate like "We are a B Corp" etc. That's in Who We Are section; we didn't include Who We Are heading. Should we include About the company? Not required. Could omit. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we shouldn't include Who We Are as a heading unless we map to About the role? But About the role is for the role, not company. The "Who We Are" is company description; we could omit because not required heading. The rule: include a section ONLY when posting has real, specific content for it. We could include a section like "About the company" but not in allowed headings. So better to omit. Thus final HTML fragment:

  About the role

  PAE is seeking a motivated and inquisitive Entry-Level Plumbing Design Engineer to join our San Francisco team in a hybrid office environment. This role is designed for a proactive individual looking to build a career in plumbing 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 plumbing and engineering distribution systems. You will play a foundational role in supporting project teams while developing technical mastery in industry-standard software and plumbing codes.

  Responsibilities

  • Develop an understanding of plumbing system design, modeling and documentation
  • Develop proficiency using Revit and AutoCAD as design/drafting tools
  • Provide task-based support for engineering distribution and Plumbing
  • Develop an understanding of drawings, specifications, building codes, and plumbing design industry standards
  • Complete assigned work with instruction from project team members
  • Assist with construction administration
  • Perform mechanical calculations and performance simulations
  • Design layout of plumbing systems
  • Perform other duties as assigned

  Qualifications

  • Bachelor’s Degree in Engineering for discipline work
  • Engineer in Training (E.I.T.) or ability to obtain
  • Internship experience preferred

  Skills

  • Revit/AutoCAD
  • Analytical skills, strategic thinking
  • Passionate about results
  • Organization