Project Engineer III
TRC Companies, Inc. · Kansas City, MO · 1 mo ago
On-siteEngineering$92k/yrFull-time
We need to output HTML fragment with sections: About Us? Actually "About Us" is a section heading? The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading. They also say include a section ONLY when posting has real, specific content for it. So we need to parse the posting.
We have sections: About Us (company overview). Could be considered "About the role"? Actually "About Us" is about company, not role. The instruction list includes "About the role". But we can still use heading "About Us"? The examples are not exhaustive; they say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading. They also say include a section ONLY when posting has real, specific content for it. So we need to parse the posting.
We have sections: About Us (company overview). Could be considered "About the role"? Actually "About Us" is about company, not role. The instruction list includes "About the role". But we can still use heading "About Us"? The examples are not exhaustive; they say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use other headings if appropriate, but likely they expect those standard headings. However "About Us" could be considered "About the role"? Not exactly. Might be better to use "About the role" heading and put the company overview there? But the instruction says do NOT repeat the job title as a heading. It doesn't forbid using "About Us". But they gave examples; we can still use other headings if they make sense. However they said "Prefer a few substantive sections over many thin ones." So we could combine company overview into a section like "About the role" or maybe "Overview". The posting includes "Overview" heading after About Us. Actually the text: "About Us TRC, Member of WSP, is a global consulting..." then later "Overview TRC is seeking a qualified individual..." So there are two sections: About Us and Overview. We could combine them into a single section like "About the role" or maybe keep both as separate headings? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Both have content. So we could output two sections: one for "About Us" and one for "Overview". But the examples list didn't include About Us; but they didn't forbid. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those headings. But we could still use "About Us" as a heading; it's still an h3. The instruction didn't say we cannot use other headings. It just gave examples. So I think it's fine to use "About Us" and "Overview". However "Overview" is similar to "About the role". Might be redundant. Could combine.
Better to follow the spirit: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (company overview + overview of role). Responsibilities (list). Requirements (maybe qualifications). Qualifications (education/experience). Skills (maybe technical skills). Benefits (listed). Pay (salary range). Schedule (not mentioned). So we should omit Schedule.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, disclaimers, application instructions, cookie/navigation/legal, duplicated lines.
We need to output only HTML fragment.
Let's extract content.
About Us: "TRC, Member of WSP, is a global consulting environmental and engineering firm and one of the top design firms in the energy sector. Together, TRC and WSP’s 83,000 experts create positive, long-lasting impacts for our communities and our clients in the power and energy, transportation and infrastructure, environmental, and property and buildings sectors. As part of our team, you’ll discover a world of opportunities to connect with innovative thinkers, forge your path, and have fun tackling the world’s most challenging projects. At TRC, Member of WSP, you can have a rewarding career on every level. TRC has long set the bar for clients who require more than just engineering, combining science with the latest technology to devise innovative solutions that stand the test of time. From pipelines to power plants, roadways to reservoirs, schoolyards to security solutions, clients look to TRC for breakthrough thinking backed by the innovative follow-through of an industry leader. We recognize that the expertise of our staff is our strongest asset, so we generously reward employees for successful performance and invest in their careers through training and the development of new skills and certifications."
Overview: "TRC is seeking a qualified individual to manage technical reviews for commercial energy efficiency projects in Kansas City. Projects and responsibilities include direct supervision of several project engineers, peer review of energy efficiency calculations, technical and financial analysis for new and existing energy efficiency measures and developing energy efficiency measure calculations. Must be a proven collaborator, able to work across internal teams and external partners to drive alignment and achieve project goals. The individual will also be responsible for monitoring project engineers’ workloads, assigning work, ensuring quality of deliverables, and providing technical guidance to support consistent and high-quality project execution. Candidates must possess strong technical capabilities including knowledge of building systems, energy efficiency, and energy-related codes and standards. The desired candidate will work collaboratively with program staff and clients to promote energy efficiency and green building projects. The candidate will be presented with a diverse range of projects found in commercial energy systems. This position requires flexibility; diversity of technical expertise; strong written, verbal, and interpersonal communication skills; and excellent customer care skills. The candidate will rely on experience and judgment to plan and accomplish goals."
Responsibilities list: It appears as a paragraph with many items separated by periods. Need to convert to - . Let's parse:
"Develop data analysis to determine savings from retro commissioning and custom energy efficiency projects.
Review custom project technical analyses (both spreadsheets and/or building simulation models) to analyze energy use in buildings in compliance with program participation guidelines and energy code requirements.
Assist in the development of technical standards, protocols and requirements for innovative energy efficiency and green building programs.
Communicate with contractors and program administrators regarding program requirements.
Stay informed about energy issues and industry trends through regular technical reading and. participation in local and national professional organizations.
As needed, conduct site visits to identify and quantify opportunities for custom measures and retro commissioning, verify installation and operation of baseline and replacement energy-using equipment.
Energy efficiency projects involving natural gas savings.
Energy efficiency program market in the Pacific Northwest.
Retro commissioning and energy efficiency assessments on commercial buildings.
Data analytics experience using R or Python programming.
Proficiency with Trane TRACE 3D Plus and/or eQuest simulation modeling software.
Well-developed presentation/public speaking skills
Use of Customer Relationship Management (CRM) technologies
PE, CEM or LEED AP accreditation."
Note there is a stray period after "reading and." but we keep as is.
Qualifications: list:
"Bachelors or Master’s degree in Mechanical Engineering or equivalent field.
5+ years of experience within the energy efficiency, green building, building science, or related fields.
Experience with commercial energy audits, analytical requirements for commercial HVAC, central heating, and cooling plants.
Familiarity with energy modeling software (e.g. eQuest, Energy Plus, Trane TRACE) and reviewing energy model output reports.
Well-developed analytical, critical thinking, and problem-solving skills.
Excellent verbal and written communication skills, time management and organizational skills
Experience with managing project engineers’ workloads, assign tasks, ensure quality of deliverables, and provide technical guidance.
Proficiency in MS Office (Word, Excel, PowerPoint, Outlook) and Team player with ability to work in a fast-paced environment."
Skills: maybe overlapping with qualifications. But we could treat qualifications as education/experience, and skills as technical skills. However the instruction says prefer few substantive sections over many thin ones. Could combine Qualifications and Skills into one section "Qualifications". But we have both sections listed in the posting: "Qualifications" heading appears before the list of qualifications. There's also a "Skills" implied in responsibilities list (like presentation skills, CRM, etc). But we could create a "Skills" section for those skill items that are not strictly qualifications (like presentation/public speaking, CRM, PE/CEM/LEED). However the qualifications list already includes some skills like analytical, communication, etc. Might be okay to have just Qualifications section covering both education/experience and skills. But the instruction says include a section ONLY when posting has real, specific content for it. The posting has a "Qualifications" heading with content. It also has responsibilities list. It also has benefits, compensation. It does not have explicit "Skills" heading, but there are skill-like items in responsibilities and qualifications. Could still create a Skills section but would be thin? Might be better to not create a Skills section unless there is a distinct heading. The posting does not have a "Skills" heading. So we should not create one.
Thus sections: About Us (or About the role?), Overview, Responsibilities, Qualifications, Benefits, Pay.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits. For Benefits we have a list. For Responsibilities we have list. For Qualifications we have list.
We need to use
for prose.
We must not repeat the job title as a heading (the page already shows it). Not needed.
We must not put Job ID/requisition numbers as headings — none present.
We must remove boilerplate: EEO, disclaimers, application instructions, etc. At end there is "Disclaimers TRC is an Equal Opportunity Employer..." etc. Remove that. Also "The complete job description and application are available on TRC’s career site. TRC accepts applications for this position on an ongoing, rolling basis and reserves the right to cancel this posting at any time." Remove.
Also remove "Benefits*:" maybe keep but note the asterisk? We'll keep benefits content.
We need to preserve all substantive information: include salary range: "Salary Range USD $91,936.00 - USD $120,000.00 /Yr." Also mention compensation varies based on experience etc. That's part of Pay section.
We also have "Other Compensation: Employee may be eligible for participation in the Company’s annual Discretionary Bonus Program which is contingent on Company, Business Segment, and Individual performance against Key Performance Indicators which vary by year and employee." That's also compensation info.
We need to include Pay section with that info.
We must not include filler like "commensurate with experience" etc. The posting includes "Compensation will vary based upon experience, education, skill level, geographical location, and other compensable factors." That's substantive, keep.
Now craft HTML.
Structure:
About Us
... (the About Us paragraph)
Overview
... (the Overview paragraph)
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- Medical, dental, vision, and disability insurance.
- 401k package that includes both traditional and Roth IRA options and Company match.
- Paid time off contingent upon full time or part-time status and level of seniority (ranging from 15 to 25 days per year).
- All full-time employees enjoy a minimum of 8 Paid Holidays per year.
- TRC ensures that all employees, including those that work part-time, receive paid sick, family, and disability leave in accordance with the laws of their state of residence.
- These benefits are applicable to US employees depending on their employment status (full time, part time, or temporary).
- TRC offers jurisdiction specific benefit packages for International and Puerto Rico employees.
Pay
In accordance with local law, the below salary range is applicable for the job and location associated with this requisition. Compensation will vary based upon experience
sections: one for "About Us" and one for "Overview". But the examples list didn't include About Us; but they didn't forbid. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those headings. But we could still use "About Us" as a heading; it's still an h3. The instruction didn't say we cannot use other headings. It just gave examples. So I think it's fine to use "About Us" and "Overview". However "Overview" is similar to "About the role". Might be redundant. Could combine.
Better to follow the spirit: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (company overview + overview of role). Responsibilities (list). Requirements (maybe qualifications). Qualifications (education/experience). Skills (maybe technical skills). Benefits (listed). Pay (salary range). Schedule (not mentioned). So we should omit Schedule.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, disclaimers, application instructions, cookie/navigation/legal, duplicated lines.
We need to output only HTML fragment.
Let's extract content.
About Us: "TRC, Member of WSP, is a global consulting environmental and engineering firm and one of the top design firms in the energy sector. Together, TRC and WSP’s 83,000 experts create positive, long-lasting impacts for our communities and our clients in the power and energy, transportation and infrastructure, environmental, and property and buildings sectors. As part of our team, you’ll discover a world of opportunities to connect with innovative thinkers, forge your path, and have fun tackling the world’s most challenging projects. At TRC, Member of WSP, you can have a rewarding career on every level. TRC has long set the bar for clients who require more than just engineering, combining science with the latest technology to devise innovative solutions that stand the test of time. From pipelines to power plants, roadways to reservoirs, schoolyards to security solutions, clients look to TRC for breakthrough thinking backed by the innovative follow-through of an industry leader. We recognize that the expertise of our staff is our strongest asset, so we generously reward employees for successful performance and invest in their careers through training and the development of new skills and certifications."
Overview: "TRC is seeking a qualified individual to manage technical reviews for commercial energy efficiency projects in Kansas City. Projects and responsibilities include direct supervision of several project engineers, peer review of energy efficiency calculations, technical and financial analysis for new and existing energy efficiency measures and developing energy efficiency measure calculations. Must be a proven collaborator, able to work across internal teams and external partners to drive alignment and achieve project goals. The individual will also be responsible for monitoring project engineers’ workloads, assigning work, ensuring quality of deliverables, and providing technical guidance to support consistent and high-quality project execution. Candidates must possess strong technical capabilities including knowledge of building systems, energy efficiency, and energy-related codes and standards. The desired candidate will work collaboratively with program staff and clients to promote energy efficiency and green building projects. The candidate will be presented with a diverse range of projects found in commercial energy systems. This position requires flexibility; diversity of technical expertise; strong written, verbal, and interpersonal communication skills; and excellent customer care skills. The candidate will rely on experience and judgment to plan and accomplish goals."
Responsibilities list: It appears as a paragraph with many items separated by periods. Need to convert to - . Let's parse:
"Develop data analysis to determine savings from retro commissioning and custom energy efficiency projects.
Review custom project technical analyses (both spreadsheets and/or building simulation models) to analyze energy use in buildings in compliance with program participation guidelines and energy code requirements.
Assist in the development of technical standards, protocols and requirements for innovative energy efficiency and green building programs.
Communicate with contractors and program administrators regarding program requirements.
Stay informed about energy issues and industry trends through regular technical reading and. participation in local and national professional organizations.
As needed, conduct site visits to identify and quantify opportunities for custom measures and retro commissioning, verify installation and operation of baseline and replacement energy-using equipment.
Energy efficiency projects involving natural gas savings.
Energy efficiency program market in the Pacific Northwest.
Retro commissioning and energy efficiency assessments on commercial buildings.
Data analytics experience using R or Python programming.
Proficiency with Trane TRACE 3D Plus and/or eQuest simulation modeling software.
Well-developed presentation/public speaking skills
Use of Customer Relationship Management (CRM) technologies
PE, CEM or LEED AP accreditation."
Note there is a stray period after "reading and." but we keep as is.
Qualifications: list:
"Bachelors or Master’s degree in Mechanical Engineering or equivalent field.
5+ years of experience within the energy efficiency, green building, building science, or related fields.
Experience with commercial energy audits, analytical requirements for commercial HVAC, central heating, and cooling plants.
Familiarity with energy modeling software (e.g. eQuest, Energy Plus, Trane TRACE) and reviewing energy model output reports.
Well-developed analytical, critical thinking, and problem-solving skills.
Excellent verbal and written communication skills, time management and organizational skills
Experience with managing project engineers’ workloads, assign tasks, ensure quality of deliverables, and provide technical guidance.
Proficiency in MS Office (Word, Excel, PowerPoint, Outlook) and Team player with ability to work in a fast-paced environment."
Skills: maybe overlapping with qualifications. But we could treat qualifications as education/experience, and skills as technical skills. However the instruction says prefer few substantive sections over many thin ones. Could combine Qualifications and Skills into one section "Qualifications". But we have both sections listed in the posting: "Qualifications" heading appears before the list of qualifications. There's also a "Skills" implied in responsibilities list (like presentation skills, CRM, etc). But we could create a "Skills" section for those skill items that are not strictly qualifications (like presentation/public speaking, CRM, PE/CEM/LEED). However the qualifications list already includes some skills like analytical, communication, etc. Might be okay to have just Qualifications section covering both education/experience and skills. But the instruction says include a section ONLY when posting has real, specific content for it. The posting has a "Qualifications" heading with content. It also has responsibilities list. It also has benefits, compensation. It does not have explicit "Skills" heading, but there are skill-like items in responsibilities and qualifications. Could still create a Skills section but would be thin? Might be better to not create a Skills section unless there is a distinct heading. The posting does not have a "Skills" heading. So we should not create one.
Thus sections: About Us (or About the role?), Overview, Responsibilities, Qualifications, Benefits, Pay.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits. For Benefits we have a list. For Responsibilities we have list. For Qualifications we have list.
We need to use
for prose.
We must not repeat the job title as a heading (the page already shows it). Not needed.
We must not put Job ID/requisition numbers as headings — none present.
We must remove boilerplate: EEO, disclaimers, application instructions, etc. At end there is "Disclaimers TRC is an Equal Opportunity Employer..." etc. Remove that. Also "The complete job description and application are available on TRC’s career site. TRC accepts applications for this position on an ongoing, rolling basis and reserves the right to cancel this posting at any time." Remove.
Also remove "Benefits*:" maybe keep but note the asterisk? We'll keep benefits content.
We need to preserve all substantive information: include salary range: "Salary Range USD $91,936.00 - USD $120,000.00 /Yr." Also mention compensation varies based on experience etc. That's part of Pay section.
We also have "Other Compensation: Employee may be eligible for participation in the Company’s annual Discretionary Bonus Program which is contingent on Company, Business Segment, and Individual performance against Key Performance Indicators which vary by year and employee." That's also compensation info.
We need to include Pay section with that info.
We must not include filler like "commensurate with experience" etc. The posting includes "Compensation will vary based upon experience, education, skill level, geographical location, and other compensable factors." That's substantive, keep.
Now craft HTML.
Structure:
About Us
... (the About Us paragraph)
Overview
... (the Overview paragraph)
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- Medical, dental, vision, and disability insurance.
- 401k package that includes both traditional and Roth IRA options and Company match.
- Paid time off contingent upon full time or part-time status and level of seniority (ranging from 15 to 25 days per year).
- All full-time employees enjoy a minimum of 8 Paid Holidays per year.
- TRC ensures that all employees, including those that work part-time, receive paid sick, family, and disability leave in accordance with the laws of their state of residence.
- These benefits are applicable to US employees depending on their employment status (full time, part time, or temporary).
- TRC offers jurisdiction specific benefit packages for International and Puerto Rico employees.
Pay
In accordance with local law, the below salary range is applicable for the job and location associated with this requisition. Compensation will vary based upon experience
- . Let's parse:
"Develop data analysis to determine savings from retro commissioning and custom energy efficiency projects.
Review custom project technical analyses (both spreadsheets and/or building simulation models) to analyze energy use in buildings in compliance with program participation guidelines and energy code requirements.
Assist in the development of technical standards, protocols and requirements for innovative energy efficiency and green building programs.
Communicate with contractors and program administrators regarding program requirements.
Stay informed about energy issues and industry trends through regular technical reading and. participation in local and national professional organizations.
As needed, conduct site visits to identify and quantify opportunities for custom measures and retro commissioning, verify installation and operation of baseline and replacement energy-using equipment.
Energy efficiency projects involving natural gas savings.
Energy efficiency program market in the Pacific Northwest.
Retro commissioning and energy efficiency assessments on commercial buildings.
Data analytics experience using R or Python programming.
Proficiency with Trane TRACE 3D Plus and/or eQuest simulation modeling software.
Well-developed presentation/public speaking skills
Use of Customer Relationship Management (CRM) technologies
PE, CEM or LEED AP accreditation."
Note there is a stray period after "reading and." but we keep as is.
Qualifications: list:
"Bachelors or Master’s degree in Mechanical Engineering or equivalent field.
5+ years of experience within the energy efficiency, green building, building science, or related fields.
Experience with commercial energy audits, analytical requirements for commercial HVAC, central heating, and cooling plants.
Familiarity with energy modeling software (e.g. eQuest, Energy Plus, Trane TRACE) and reviewing energy model output reports.
Well-developed analytical, critical thinking, and problem-solving skills.
Excellent verbal and written communication skills, time management and organizational skills
Experience with managing project engineers’ workloads, assign tasks, ensure quality of deliverables, and provide technical guidance.
Proficiency in MS Office (Word, Excel, PowerPoint, Outlook) and Team player with ability to work in a fast-paced environment."
Skills: maybe overlapping with qualifications. But we could treat qualifications as education/experience, and skills as technical skills. However the instruction says prefer few substantive sections over many thin ones. Could combine Qualifications and Skills into one section "Qualifications". But we have both sections listed in the posting: "Qualifications" heading appears before the list of qualifications. There's also a "Skills" implied in responsibilities list (like presentation skills, CRM, etc). But we could create a "Skills" section for those skill items that are not strictly qualifications (like presentation/public speaking, CRM, PE/CEM/LEED). However the qualifications list already includes some skills like analytical, communication, etc. Might be okay to have just Qualifications section covering both education/experience and skills. But the instruction says include a section ONLY when posting has real, specific content for it. The posting has a "Qualifications" heading with content. It also has responsibilities list. It also has benefits, compensation. It does not have explicit "Skills" heading, but there are skill-like items in responsibilities and qualifications. Could still create a Skills section but would be thin? Might be better to not create a Skills section unless there is a distinct heading. The posting does not have a "Skills" heading. So we should not create one.
Thus sections: About Us (or About the role?), Overview, Responsibilities, Qualifications, Benefits, Pay.
We need to use
for each section heading. We need to use
- for any list of duties/requirements/benefits. For Benefits we have a list. For Responsibilities we have list. For Qualifications we have list.
We need to use
for prose. We must not repeat the job title as a heading (the page already shows it). Not needed. We must not put Job ID/requisition numbers as headings — none present. We must remove boilerplate: EEO, disclaimers, application instructions, etc. At end there is "Disclaimers TRC is an Equal Opportunity Employer..." etc. Remove that. Also "The complete job description and application are available on TRC’s career site. TRC accepts applications for this position on an ongoing, rolling basis and reserves the right to cancel this posting at any time." Remove. Also remove "Benefits*:" maybe keep but note the asterisk? We'll keep benefits content. We need to preserve all substantive information: include salary range: "Salary Range USD $91,936.00 - USD $120,000.00 /Yr." Also mention compensation varies based on experience etc. That's part of Pay section. We also have "Other Compensation: Employee may be eligible for participation in the Company’s annual Discretionary Bonus Program which is contingent on Company, Business Segment, and Individual performance against Key Performance Indicators which vary by year and employee." That's also compensation info. We need to include Pay section with that info. We must not include filler like "commensurate with experience" etc. The posting includes "Compensation will vary based upon experience, education, skill level, geographical location, and other compensable factors." That's substantive, keep. Now craft HTML. Structure:
About Us
... (the About Us paragraph)
Overview
... (the Overview paragraph)
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- Medical, dental, vision, and disability insurance.
- 401k package that includes both traditional and Roth IRA options and Company match.
- Paid time off contingent upon full time or part-time status and level of seniority (ranging from 15 to 25 days per year).
- All full-time employees enjoy a minimum of 8 Paid Holidays per year.
- TRC ensures that all employees, including those that work part-time, receive paid sick, family, and disability leave in accordance with the laws of their state of residence.
- These benefits are applicable to US employees depending on their employment status (full time, part time, or temporary).
- TRC offers jurisdiction specific benefit packages for International and Puerto Rico employees.
Pay
In accordance with local law, the below salary range is applicable for the job and location associated with this requisition. Compensation will vary based upon experience
- for any list of duties/requirements/benefits. For Benefits we have a list. For Responsibilities we have list. For Qualifications we have list.
We need to use