Engineering Team Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
Content includes:
- About Us (company description). Could map to "About the role"? Actually "About Us" is about company, not role. The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for description of role? But we have "About Us" describing company. Could we treat that as "About the role"? Might be okay but better to reflect actual content: maybe we can have a section "About the company" but not in allowed list. However instruction says use those headings as examples; we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. If we have company description, maybe we can put under "About the role"? Not ideal but maybe acceptable. However we could also omit that section if not needed? But we must preserve ALL substantive information. So we need to include company description somewhere. Could embed in a
without heading? The instruction says use headings for sections; but we could have a
without heading? It says use
for section headings (e.g. ...). It doesn't forbid having a
without heading, but likely they expect sections with headings. We could create a section "About the company" but not in list; maybe they'd accept. But they said "e.g." meaning examples, not exhaustive. So we can use other headings as needed. Safer to use "About the company" heading.
But we also have Responsibilities (duties). That's a list.
Education And Experience Requirements -> that's qualifications/requirements.
Required Special Skills -> skills.
Benefits* section -> benefits.
Compensation -> pay.
Also there is mention of Job Type: Full Time, Rate of Pay: $155,188.80 per year, Salary Range USD $155,188.80 - USD $170,188.80 /Yr. So we have pay info.
Schedule? Not given besides full time. Could we create Schedule section? The posting says Job Type: Full Time. That's schedule info (full-time). Could include Schedule section with "Full Time". But instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Job Type: Full Time, so we can include Schedule.
But also there is "Other Compensation: Employee may be eligible for participation in the Company’s annual Discretionary Bonus Program". That's compensation detail.
We need to preserve all substantive information. So we need to include details about responsibilities list, education/experience requirements, special skills, benefits, compensation, schedule, about us.
We must remove boilerplate: EEO, disclaimers, application instructions like "Apply online.", "The complete job description and application are available on TRC’s career site.", etc. Also remove duplicated lines.
We need to format lists with
- . For prose use
.
We need to avoid filler like "commensurate with experience". Not present.
Now craft HTML.
We'll have sections:
About the company
... (the About Us paragraph)
Responsibilities
- ... each duty
Qualifications
maybe combine Education And Experience Requirements and Required Special Skills? But we could separate: Requirements and Skills. The instruction list includes Requirements, Qualifications, Skills. We could have Requirements for education/experience, Qualifications maybe not needed, Skills for special skills. But we have both Education And Experience Requirements and Required Special Skills. Could make two sections: Requirements
for education/experience, and Skills
for special skills.
We also have Benefits* section: Benefits
- ... each benefit
Pay: Pay
... salary info
Schedule: Schedule
Full Time
We need to ensure we don't repeat job title or requisition.
We need to preserve all substantive info: include location (Cleveland, Ohio), remote option (home office anywhere in US), reports to TRC's office in Cleveland, OH. Also mention that applicants may work from a home office anywhere in the United States. This is substantive; where to put? Could be under About the role or maybe under Schedule? Not exactly. Could add a under About the company? Might be better to add a section "Job Details" but not in list. Could incorporate into About the company paragraph? Might be okay to add a separate
after About the company: maybe under a heading "Job Overview". But instruction says use those headings as examples; we can add other headings if needed. However to keep few sections, we could add that info under About the company paragraph as additional sentences.
Let's extract About Us paragraph:
"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."
That's the About Us.
Now responsibilities list: need to extract each duty bullet.
From text:
"Duties: Acts as the primary technical resource for Advanced Metering Infrastructure (AMI) implementation and integration projects within the company's Digital Solutions utility practice and is responsible for the overall technical success of a project.
Manages the technical deliverables of implementation projects, including overseeing a team of technical resources, scheduling, configuring, testing, tracking, and managing technical tasks.
Works closely with Solution Architects and Project Managers to ensure technical solutions meet customer needs and business objectives.
Ensures the delivery of technical solutions falls within the company's Digital Solutions standard processes and tools.
Owns the technical aspect of a project and ensures no obstacles negatively impact project management.
Works closely with software vendor partners, clients, and onshore and offshore project teams to deliver world class solutions that solve customers' current and future challenges.
Assists the Project Manager with scope management, project planning, milestones, and work and resource estimates.
Provides end-to-end technical oversight and assumes overall responsibility for the success and integrity of a proposed technical solution.
Provides technical leadership for subcontractor work and deliverables.
Presents project deliverables to client project team members at the end of the design phase.
Participates in the build and test phase of a project (configures and tests) and provides technical leadership to team members to ensure smooth and timely solution delivery while adhering to technical “best practices.”
Owns the quality assurance process to ensure a solution is thoroughly tested prior to system integration and user acceptance testing.
Documents requirements for custom development and ensures requirements are met.
Develops and delivers onsite end user training.
Supports proposals and participates in post- bid activities, including clarifications, short list presentation support, and supporting scope definition in contract development and negotiations."
We need each as
- .
Now Education And Experience Requirements:
"Bachelor’s degree in computer science, computer information systems, management information technology or related field and five (5) years of software delivery experience related to system integration, performing data mapping, and data transformation.
In The Alternative Master’s degree in computer science, computer information systems, management information technology or related field and three (3) years of software delivery experience related to system integration, performing data mapping, and data transformation."
We'll put as
- items.
Now Required Special Skills: It's a long paragraph with multiple DE items. We need to break into list items? The instruction: Use
- for any list of duties/requirements/benefits. For skills, it's also a list (though it's a paragraph with multiple DE statements). We'll split into separate
- each DE statement.
Let's parse:
"Demonstrated expertise (DE) configuring, testing, troubleshooting, designing, and conducting performance tuning for EnergyIP/GridscaleX and its adapters for multiple Customer Information Systems (CIS) and Head End Systems (HES) leveraging SQL Developer for database productivity, SoapUI for API testing, Putty for Unix connectivity, and Prometheus and Grafana for performance monitoring.
DE optimizing operational, data processing, and integration workflows leveraging Python, Ruby, PL/SQL or JavaScript scripting languages to automate data validation, monitoring, exception handling, and testing processes to reduce manual effort, enhance data quality, minimize operational risk, promote reuse, and accelerate project work.
DE extracting, transforming, loading, and validating data between Meter Data Management (MDM) systems, customer information, billing platforms, data lakes, web portals, analytics environments, and Head End systems according to design specifications leveraging Web Services Description Language (WSDL), XML Schema Definition (XSD) interfaces, and RESTful APIs to enable seamless system integration, high quality data exchange, and reliable data flow between systems.
DE streamlining delivery processes, proactively reducing issues or reworks, and improving overall customer satisfaction throughout a project lifecycle leveraging data engineering practices, including JIRA for workflow management; Git for version-controlled development; and DevOps for continuous integration and continuous delivery (CI/CD) automation to streamline processes, reduce defects, and accelerate delivery."
We'll make each as
- .
Now Benefits*:
"TRC offers a competitive benefit package consisting of:
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
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. Content includes: - About Us (company description). Could map to "About the role"? Actually "About Us" is about company, not role. The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for description of role? But we have "About Us" describing company. Could we treat that as "About the role"? Might be okay but better to reflect actual content: maybe we can have a section "About the company" but not in allowed list. However instruction says use those headings as examples; we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. If we have company description, maybe we can put under "About the role"? Not ideal but maybe acceptable. However we could also omit that section if not needed? But we must preserve ALL substantive information. So we need to include company description somewhere. Could embed in a
without heading? The instruction says use headings for sections; but we could have a
without heading? It says use
for section headings (e.g. ...). It doesn't forbid having a
without heading, but likely they expect sections with headings. We could create a section "About the company" but not in list; maybe they'd accept. But they said "e.g." meaning examples, not exhaustive. So we can use other headings as needed. Safer to use "About the company" heading. But we also have Responsibilities (duties). That's a list. Education And Experience Requirements -> that's qualifications/requirements. Required Special Skills -> skills. Benefits* section -> benefits. Compensation -> pay. Also there is mention of Job Type: Full Time, Rate of Pay: $155,188.80 per year, Salary Range USD $155,188.80 - USD $170,188.80 /Yr. So we have pay info. Schedule? Not given besides full time. Could we create Schedule section? The posting says Job Type: Full Time. That's schedule info (full-time). Could include Schedule section with "Full Time". But instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Job Type: Full Time, so we can include Schedule. But also there is "Other Compensation: Employee may be eligible for participation in the Company’s annual Discretionary Bonus Program". That's compensation detail. We need to preserve all substantive information. So we need to include details about responsibilities list, education/experience requirements, special skills, benefits, compensation, schedule, about us. We must remove boilerplate: EEO, disclaimers, application instructions like "Apply online.", "The complete job description and application are available on TRC’s career site.", etc. Also remove duplicated lines. We need to format lists with
- . For prose use
. We need to avoid filler like "commensurate with experience". Not present. Now craft HTML. We'll have sections:
About the company
... (the About Us paragraph)
Responsibilities
- ... each duty
Qualifications
maybe combine Education And Experience Requirements and Required Special Skills? But we could separate: Requirements and Skills. The instruction list includes Requirements, Qualifications, Skills. We could have Requirements for education/experience, Qualifications maybe not needed, Skills for special skills. But we have both Education And Experience Requirements and Required Special Skills. Could make two sections:Requirements
for education/experience, andSkills
for special skills. We also have Benefits* section:Benefits
- ... each benefit
Pay
... salary info
Schedule:Schedule
Full Time
We need to ensure we don't repeat job title or requisition. We need to preserve all substantive info: include location (Cleveland, Ohio), remote option (home office anywhere in US), reports to TRC's office in Cleveland, OH. Also mention that applicants may work from a home office anywhere in the United States. This is substantive; where to put? Could be under About the role or maybe under Schedule? Not exactly. Could add aunder About the company? Might be better to add a section "Job Details" but not in list. Could incorporate into About the company paragraph? Might be okay to add a separate
after About the company: maybe under a heading "Job Overview". But instruction says use those headings as examples; we can add other headings if needed. However to keep few sections, we could add that info under About the company paragraph as additional sentences. Let's extract About Us paragraph: "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." That's the About Us. Now responsibilities list: need to extract each duty bullet. From text: "Duties: Acts as the primary technical resource for Advanced Metering Infrastructure (AMI) implementation and integration projects within the company's Digital Solutions utility practice and is responsible for the overall technical success of a project. Manages the technical deliverables of implementation projects, including overseeing a team of technical resources, scheduling, configuring, testing, tracking, and managing technical tasks. Works closely with Solution Architects and Project Managers to ensure technical solutions meet customer needs and business objectives. Ensures the delivery of technical solutions falls within the company's Digital Solutions standard processes and tools. Owns the technical aspect of a project and ensures no obstacles negatively impact project management. Works closely with software vendor partners, clients, and onshore and offshore project teams to deliver world class solutions that solve customers' current and future challenges. Assists the Project Manager with scope management, project planning, milestones, and work and resource estimates. Provides end-to-end technical oversight and assumes overall responsibility for the success and integrity of a proposed technical solution. Provides technical leadership for subcontractor work and deliverables. Presents project deliverables to client project team members at the end of the design phase. Participates in the build and test phase of a project (configures and tests) and provides technical leadership to team members to ensure smooth and timely solution delivery while adhering to technical “best practices.” Owns the quality assurance process to ensure a solution is thoroughly tested prior to system integration and user acceptance testing. Documents requirements for custom development and ensures requirements are met. Develops and delivers onsite end user training. Supports proposals and participates in post- bid activities, including clarifications, short list presentation support, and supporting scope definition in contract development and negotiations." We need each as
- . Now Education And Experience Requirements: "Bachelor’s degree in computer science, computer information systems, management information technology or related field and five (5) years of software delivery experience related to system integration, performing data mapping, and data transformation. In The Alternative Master’s degree in computer science, computer information systems, management information technology or related field and three (3) years of software delivery experience related to system integration, performing data mapping, and data transformation." We'll put as
- items.
Now Required Special Skills: It's a long paragraph with multiple DE items. We need to break into list items? The instruction: Use
- for any list of duties/requirements/benefits. For skills, it's also a list (though it's a paragraph with multiple DE statements). We'll split into separate
- each DE statement. Let's parse: "Demonstrated expertise (DE) configuring, testing, troubleshooting, designing, and conducting performance tuning for EnergyIP/GridscaleX and its adapters for multiple Customer Information Systems (CIS) and Head End Systems (HES) leveraging SQL Developer for database productivity, SoapUI for API testing, Putty for Unix connectivity, and Prometheus and Grafana for performance monitoring. DE optimizing operational, data processing, and integration workflows leveraging Python, Ruby, PL/SQL or JavaScript scripting languages to automate data validation, monitoring, exception handling, and testing processes to reduce manual effort, enhance data quality, minimize operational risk, promote reuse, and accelerate project work. DE extracting, transforming, loading, and validating data between Meter Data Management (MDM) systems, customer information, billing platforms, data lakes, web portals, analytics environments, and Head End systems according to design specifications leveraging Web Services Description Language (WSDL), XML Schema Definition (XSD) interfaces, and RESTful APIs to enable seamless system integration, high quality data exchange, and reliable data flow between systems. DE streamlining delivery processes, proactively reducing issues or reworks, and improving overall customer satisfaction throughout a project lifecycle leveraging data engineering practices, including JIRA for workflow management; Git for version-controlled development; and DevOps for continuous integration and continuous delivery (CI/CD) automation to streamline processes, reduce defects, and accelerate delivery." We'll make each as
- . Now Benefits*: "TRC offers a competitive benefit package consisting of: 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