Entry Level Building Performance Specialist - San Francsico, CA
for headings. Use - for lists. Use
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Keep substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The first paragraph: "The Opportunity PAE is looking for an aspiring engineer passionate about the intersection of sustainable design and mechanical systems to join our San Francisco team as an Entry Level Building Performance Specialist. In this role, you won’t just be drafting; you’ll be a key contributor to greenhouse gas analysis, renewable energy systems, and high-performance HVAC design. As a vital member of our project teams, you will bridge the gap between complex engineering simulations and real-world construction. From performing mechanical calculations in TRACE and IES to designing system layouts in Revit, you will gain hands-on experience across the entire project lifecycle, from initial district planning to construction administration."
That's prose.
- Who We Are: Could be "About the company" but not required heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include "About the role" and maybe "About the company" not listed; but we could include "About the role" only. However we have "Who We Are" content that is substantive; maybe we can put under "About the role"? But better to have a separate section like "About the company" but not in allowed list; but we could still include as a heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we can still include other headings if needed? Safer to stick to those. However we have substantive info about company that could be placed under "About the role"? Might be odd. Could put under "About the role" a paragraph about the company? Or we could create a section "About PAE" but not in list; risk of being considered not following instruction. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd include sections that match content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not mentioned (no schedule specifics). So we omit Schedule.
We need to extract:
Responsibilities: from "What You'll Do" bullet list.
Requirements: maybe "What You Bring" includes education, EIT, internship, etc. Could be Requirements.
Qualifications: maybe overlapping; but we can separate: Requirements = education, EIT, internship; Qualifications = skills like Revit/AutoCAD, TRACE, IES, analytical skills, etc. Skills = maybe software/tools? But we can combine.
Better: Use Requirements for education and experience; Qualifications for technical skills; Skills for soft skills? But we can just have Requirements and Qualifications.
Let's parse:
What You Bring:
- Bachelor’s Degree in Engineering for discipline work
- Engineer in Training (E.I.T.) or ability to obtain
- Internship experience preferred
- Revit/AutoCAD, TRACE, IES
- Strong analytical skills, strategic thinking
- Passionate about results
- Organization
- Clear communication
- Attention to detail
- Time management
- Microsoft Office Suite
We could split: Requirements: Bachelor’s Degree, EIT or ability to obtain, Internship experience preferred. Qualifications: Revit/AutoCAD, TRACE, IES, Strong analytical skills, strategic thinking, Passionate about results, Organization, Clear communication, Attention to detail, Time management, Microsoft Office Suite.
Skills: maybe we could list technical skills separately, but we can put them under Qualifications.
Benefits: from "What We Offer": list includes hiring base salary range (but that's Pay), overtime, benefits package: employer paid health insurance (medical, dental, vision), annual 401k profit sharing, professional development reimbursements, employer paid commuter/parking stipend, cell phone stipend, life insurance and disability benefits, hybrid work schedule, 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 $81,700-$98,700 annual, overtime eligibility.
Schedule: hybrid work schedule mentioned; could be Schedule section. But we have hybrid work schedule under benefits; but we could also put schedule as separate. Since they said include Schedule only if posting actually states them. It does state hybrid work schedule. So we can create Schedule section with that detail.
We must not include boilerplate like EEO, JUST label, etc. Remove fine print about recruiters, EEO, etc. Also remove "To learn more about our comprehensive benefits package, visit ..." maybe keep? It's a link; but it's part of benefits description. Might keep as part of benefits but it's a link; we can keep as plain text? Probably okay but it's not boilerplate; it's a link to benefits. Could keep.
Also remove "This information is provided per the Equal Pay Act" etc. That's boilerplate legal; remove.
Also remove "Our commitment to pay equity" etc. Remove.
Also remove "What We’re Made Of" etc? That's company history; could be considered substantive but not under allowed headings. Could we put under "About the role"? Might be too much. But maybe we can include a section "About the company" but not in list; risk. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company description under "About the role" or maybe under "About the role" we already have role description; we could add a paragraph about company after that. That seems okay.
Thus final HTML:
About the role
... (role description)
Responsibilities
- Develop an understanding of mechanical system design, modeling and documentation
- Develop proficiency using Revit and AutoCAD as design/drafting tools
- Provide task-based support building performance analysis, greenhouse gas analysis, renewable energy systems, district planning, engineering distribution, HVAC and plumbing
- Develop an understanding of drawings, specifications, building codes, and mechanical industry standards
- Complete assigned work with instruction from project team members
- Assist with construction administration
- Perform mechanical calculations and performance simulations
- Design layout of mechanical systems
- Perform other duties as assigned
Requirements
- Bachelor’s Degree in Engineering for discipline work
- Engineer in Training (E.I.T.) or ability to obtain
- Internship experience preferred
Qualifications
- Revit/AutoCAD, TRACE, IES
- Strong analytical skills, strategic thinking
- Passionate about results
- Organization
- Clear communication
- Attention to detail
- Time management
- Microsoft Office Suite
Benefits
- 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
- 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
- Hybrid work schedule
Pay
Hiring Base Salary Range: $81,700‑$98,700 annual. This position is eligible for time and a half overtime pay.
Schedule
Hybrid work schedule.
We need to ensure no duplicate content: hybrid work schedule appears both in Benefits and Schedule; we might remove from Benefits to avoid duplication. But the instruction says preserve ALL substantive information; we can keep it in both? Might be duplicate but still preserving. Better to keep only in Schedule and remove from Benefits to avoid redundancy. However benefits list includes hybrid work schedule as a benefit; we could keep it there and not have separate Schedule. But we already have Schedule section; we could keep hybrid work schedule only under Schedule and not duplicate. But then we lose that benefit detail under Benefits; but we still have it under Schedule, which is still preserving. The instruction: "Preserve ALL substantive information". If we move it to Schedule, it's still preserved. So we can remove from Benefits.
Thus Benefits list excludes hybrid work schedule.
Check other duplicates: none.
Now ensure we didn't include boilerplate: removed fine print, EEO, JUST label, etc.
Check for any remaining boilerplate like "To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits." That's a link; it's not boilerplate but it's a reference; we could keep it as part of Benefits maybe as a sentence. But it's not a list item; we could add a after the list. However the instruction says use
for prose. We could add a
with that sentence. But it's not essential; we could omit as it's just a link; but it's substantive? It's a reference to learn more; maybe we can keep as a
. However it's not a list; we can add a
after the Benefits
. Let's include: To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits.
Similarly, there is a line "This information is provided per the Equal Pay Act" which we removed.
Also there is "Our commitment to pay equity ..." removed.
Also "What We’re Made Of" etc removed.
Now check that we haven't missed any substantive info: The "Who We Are" paragraph about PAE being an engineering and design firm, leveraging latest technologies, solving problems, etc. That's substantive. We haven't included it anywhere. We could incorporate into About the role section as a paragraph after role description. Let's add a after the role description: "PAE is an engineering and design firm that turns complex challenges into reality. By leveraging the latest technologies, we solve problems in unique ways, and our designs enable buildings and communities to be more resilient and efficient. PAE is trusted by our clients in every aspect of a project's lifespan, from idea to occupancy. We set ambitious goals backed by analysis to significantly conserve water and energy while balancing costs and long-term operational needs. As a B Corp, we measure success by the benefits our projects provide to our clients, our communities, and our planet. We embrace innovation, transparency, sustainability, and lifelong curiosity."
That's substantive; we should include.
Thus About the role will have two paragraphs: first about role, second about company.
Now check for any other substantive: "Founded in
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Keep substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "The Opportunity PAE is looking for an aspiring engineer passionate about the intersection of sustainable design and mechanical systems to join our San Francisco team as an Entry Level Building Performance Specialist. In this role, you won’t just be drafting; you’ll be a key contributor to greenhouse gas analysis, renewable energy systems, and high-performance HVAC design. As a vital member of our project teams, you will bridge the gap between complex engineering simulations and real-world construction. From performing mechanical calculations in TRACE and IES to designing system layouts in Revit, you will gain hands-on experience across the entire project lifecycle, from initial district planning to construction administration." That's prose. - Who We Are: Could be "About the company" but not required heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include "About the role" and maybe "About the company" not listed; but we could include "About the role" only. However we have "Who We Are" content that is substantive; maybe we can put under "About the role"? But better to have a separate section like "About the company" but not in allowed list; but we could still include as a heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we can still include other headings if needed? Safer to stick to those. However we have substantive info about company that could be placed under "About the role"? Might be odd. Could put under "About the role" a paragraph about the company? Or we could create a section "About PAE" but not in list; risk of being considered not following instruction. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd include sections that match content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not mentioned (no schedule specifics). So we omit Schedule.
We need to extract:
Responsibilities: from "What You'll Do" bullet list.
Requirements: maybe "What You Bring" includes education, EIT, internship, etc. Could be Requirements.
Qualifications: maybe overlapping; but we can separate: Requirements = education, EIT, internship; Qualifications = skills like Revit/AutoCAD, TRACE, IES, analytical skills, etc. Skills = maybe software/tools? But we can combine.
Better: Use Requirements for education and experience; Qualifications for technical skills; Skills for soft skills? But we can just have Requirements and Qualifications.
Let's parse:
What You Bring:
- Bachelor’s Degree in Engineering for discipline work
- Engineer in Training (E.I.T.) or ability to obtain
- Internship experience preferred
- Revit/AutoCAD, TRACE, IES
- Strong analytical skills, strategic thinking
- Passionate about results
- Organization
- Clear communication
- Attention to detail
- Time management
- Microsoft Office Suite
We could split: Requirements: Bachelor’s Degree, EIT or ability to obtain, Internship experience preferred. Qualifications: Revit/AutoCAD, TRACE, IES, Strong analytical skills, strategic thinking, Passionate about results, Organization, Clear communication, Attention to detail, Time management, Microsoft Office Suite.
Skills: maybe we could list technical skills separately, but we can put them under Qualifications.
Benefits: from "What We Offer": list includes hiring base salary range (but that's Pay), overtime, benefits package: employer paid health insurance (medical, dental, vision), annual 401k profit sharing, professional development reimbursements, employer paid commuter/parking stipend, cell phone stipend, life insurance and disability benefits, hybrid work schedule, 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 $81,700-$98,700 annual, overtime eligibility.
Schedule: hybrid work schedule mentioned; could be Schedule section. But we have hybrid work schedule under benefits; but we could also put schedule as separate. Since they said include Schedule only if posting actually states them. It does state hybrid work schedule. So we can create Schedule section with that detail.
We must not include boilerplate like EEO, JUST label, etc. Remove fine print about recruiters, EEO, etc. Also remove "To learn more about our comprehensive benefits package, visit ..." maybe keep? It's a link; but it's part of benefits description. Might keep as part of benefits but it's a link; we can keep as plain text? Probably okay but it's not boilerplate; it's a link to benefits. Could keep.
Also remove "This information is provided per the Equal Pay Act" etc. That's boilerplate legal; remove.
Also remove "Our commitment to pay equity" etc. Remove.
Also remove "What We’re Made Of" etc? That's company history; could be considered substantive but not under allowed headings. Could we put under "About the role"? Might be too much. But maybe we can include a section "About the company" but not in list; risk. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company description under "About the role" or maybe under "About the role" we already have role description; we could add a paragraph about company after that. That seems okay.
Thus final HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd include sections that match content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not mentioned (no schedule specifics). So we omit Schedule.
We need to extract:
Responsibilities: from "What You'll Do" bullet list.
Requirements: maybe "What You Bring" includes education, EIT, internship, etc. Could be Requirements.
Qualifications: maybe overlapping; but we can separate: Requirements = education, EIT, internship; Qualifications = skills like Revit/AutoCAD, TRACE, IES, analytical skills, etc. Skills = maybe software/tools? But we can combine.
Better: Use Requirements for education and experience; Qualifications for technical skills; Skills for soft skills? But we can just have Requirements and Qualifications.
Let's parse:
What You Bring:
- Bachelor’s Degree in Engineering for discipline work
- Engineer in Training (E.I.T.) or ability to obtain
- Internship experience preferred
- Revit/AutoCAD, TRACE, IES
- Strong analytical skills, strategic thinking
- Passionate about results
- Organization
- Clear communication
- Attention to detail
- Time management
- Microsoft Office Suite
We could split: Requirements: Bachelor’s Degree, EIT or ability to obtain, Internship experience preferred. Qualifications: Revit/AutoCAD, TRACE, IES, Strong analytical skills, strategic thinking, Passionate about results, Organization, Clear communication, Attention to detail, Time management, Microsoft Office Suite.
Skills: maybe we could list technical skills separately, but we can put them under Qualifications.
Benefits: from "What We Offer": list includes hiring base salary range (but that's Pay), overtime, benefits package: employer paid health insurance (medical, dental, vision), annual 401k profit sharing, professional development reimbursements, employer paid commuter/parking stipend, cell phone stipend, life insurance and disability benefits, hybrid work schedule, 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 $81,700-$98,700 annual, overtime eligibility.
Schedule: hybrid work schedule mentioned; could be Schedule section. But we have hybrid work schedule under benefits; but we could also put schedule as separate. Since they said include Schedule only if posting actually states them. It does state hybrid work schedule. So we can create Schedule section with that detail.
We must not include boilerplate like EEO, JUST label, etc. Remove fine print about recruiters, EEO, etc. Also remove "To learn more about our comprehensive benefits package, visit ..." maybe keep? It's a link; but it's part of benefits description. Might keep as part of benefits but it's a link; we can keep as plain text? Probably okay but it's not boilerplate; it's a link to benefits. Could keep.
Also remove "This information is provided per the Equal Pay Act" etc. That's boilerplate legal; remove.
Also remove "Our commitment to pay equity" etc. Remove.
Also remove "What We’re Made Of" etc? That's company history; could be considered substantive but not under allowed headings. Could we put under "About the role"? Might be too much. But maybe we can include a section "About the company" but not in list; risk. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company description under "About the role" or maybe under "About the role" we already have role description; we could add a paragraph about company after that. That seems okay.
Thus final HTML:
About the role
... (role description)
Responsibilities
- Develop an understanding of mechanical system design, modeling and documentation
- Develop proficiency using Revit and AutoCAD as design/drafting tools
- Provide task-based support building performance analysis, greenhouse gas analysis, renewable energy systems, district planning, engineering distribution, HVAC and plumbing
- Develop an understanding of drawings, specifications, building codes, and mechanical industry standards
- Complete assigned work with instruction from project team members
- Assist with construction administration
- Perform mechanical calculations and performance simulations
- Design layout of mechanical systems
- Perform other duties as assigned
Requirements
- Bachelor’s Degree in Engineering for discipline work
- Engineer in Training (E.I.T.) or ability to obtain
- Internship experience preferred
Qualifications
- Revit/AutoCAD, TRACE, IES
- Strong analytical skills, strategic thinking
- Passionate about results
- Organization
- Clear communication
- Attention to detail
- Time management
- Microsoft Office Suite
Benefits
- 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
- 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
- Hybrid work schedule
Pay
Hiring Base Salary Range: $81,700‑$98,700 annual. This position is eligible for time and a half overtime pay.
Schedule
Hybrid work schedule.
We need to ensure no duplicate content: hybrid work schedule appears both in Benefits and Schedule; we might remove from Benefits to avoid duplication. But the instruction says preserve ALL substantive information; we can keep it in both? Might be duplicate but still preserving. Better to keep only in Schedule and remove from Benefits to avoid redundancy. However benefits list includes hybrid work schedule as a benefit; we could keep it there and not have separate Schedule. But we already have Schedule section; we could keep hybrid work schedule only under Schedule and not duplicate. But then we lose that benefit detail under Benefits; but we still have it under Schedule, which is still preserving. The instruction: "Preserve ALL substantive information". If we move it to Schedule, it's still preserved. So we can remove from Benefits. Thus Benefits list excludes hybrid work schedule. Check other duplicates: none. Now ensure we didn't include boilerplate: removed fine print, EEO, JUST label, etc. Check for any remaining boilerplate like "To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits." That's a link; it's not boilerplate but it's a reference; we could keep it as part of Benefits maybe as a sentence. But it's not a list item; we could add aafter the list. However the instruction says use
for prose. We could add a
with that sentence. But it's not essential; we could omit as it's just a link; but it's substantive? It's a reference to learn more; maybe we can keep as a
. However it's not a list; we can add a
after the Benefits
- . Let's include:
To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits.
Similarly, there is a line "This information is provided per the Equal Pay Act" which we removed. Also there is "Our commitment to pay equity ..." removed. Also "What We’re Made Of" etc removed. Now check that we haven't missed any substantive info: The "Who We Are" paragraph about PAE being an engineering and design firm, leveraging latest technologies, solving problems, etc. That's substantive. We haven't included it anywhere. We could incorporate into About the role section as a paragraph after role description. Let's add aafter the role description: "PAE is an engineering and design firm that turns complex challenges into reality. By leveraging the latest technologies, we solve problems in unique ways, and our designs enable buildings and communities to be more resilient and efficient. PAE is trusted by our clients in every aspect of a project's lifespan, from idea to occupancy. We set ambitious goals backed by analysis to significantly conserve water and energy while balancing costs and long-term operational needs. As a B Corp, we measure success by the benefits our projects provide to our clients, our communities, and our planet. We embrace innovation, transparency, sustainability, and lifelong curiosity." That's substantive; we should include. Thus About the role will have two paragraphs: first about role, second about company. Now check for any other substantive: "Founded in