Early Career Electrical Engineer (Mission Critical/Data Center)
for section headings.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details, but we can format as lists.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, the notice to third party agencies, the "About WSP" duplicate maybe? The "About WSP" section includes some description of the company; is that considered boilerplate? It's not exactly boilerplate but it's generic about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About WSP" is not explicitly listed as boilerplate, but it's somewhat generic. However it's part of the job posting; we might keep it if it's substantive. But the instruction says "Prefer a few substantive sections over many thin ones." The About WSP could be considered "About the company" but not requested as a section heading. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings like "About WSP". So we should incorporate relevant info from About WSP into existing sections if appropriate, or drop it if not fitting. The About WSP paragraph includes: "WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career. At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base. Your daily contributions to your team will be essential in meeting client objectives, goals and challenges."
This contains some benefits info (already covered) and some generic company description. Since we don't have a section for company description, we could incorporate the benefits part into Benefits section (already have). The rest could be considered fluff; maybe we can drop it as it's not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description might be considered substantive? It's generic but still part of posting. However the allowed headings don't include a company overview; we could maybe put it under About the role? But About the role is supposed to describe the role, not the company. 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 says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect only those headings. So we should not add other headings. So we need to decide where to put company description. Could we incorporate it into About the role as a brief context? That might be okay but might deviate from role description. However the instruction says preserve ALL substantive information; we cannot drop it if it's substantive. But maybe it's considered boilerplate? It's not exactly legal/EEO etc. It's more marketing. The instruction didn't explicitly say to remove marketing boilerplate, only cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should keep it. But we have no heading for it; we could put it as a
before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray paragraphs outside sections. But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other elements. However they likely expect sections only. To be safe, we could incorporate the company description into a paragraph under About the role (maybe as an introductory sentence). But that would mix role and company. Might be okay.
Alternatively, we could treat the company description as part of Benefits (since it mentions benefits). But it's more than benefits.
Given the instruction to prefer few substantive sections, we could combine About the role and company description into About the role section. That would be substantive.
Thus About the role section will contain: description of the opportunity (the initial paragraph) plus maybe the company description from About WSP (the part about WSP USA). We'll need to avoid duplication.
Let's extract the initial paragraph: "This Opportunity WSP is currently initiating a search for an Early Career Electrical Engineer for our Troy, NY office Takes part in providing local technical assistance for the due diligence, investigation, remediation, impact assessment, permitting, design, development, and construction of utility, industrial, and commercial scale projects in the public and private sector. Tasks may include basic assistance with the research, design, concept development, and construction of transmission and distribution substations, power distribution, power regulation, renewable energy, as well as protection and control systems in a wide variety of contexts (utilities, transportation, building, and Federal, State, and local government projects)."
Note there is a missing space after "This Opportunity WSP". We'll keep as is.
Now the About WSP paragraph: "WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career. At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base. Your daily contributions to your team will be essential in meeting client objectives, goals and challenges."
We can incorporate the benefits sentence into Benefits section later; the rest can be part of About the role.
Now Responsibilities: we need to list each duty as
- . Let
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details, but we can format as lists. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, the notice to third party agencies, the "About WSP" duplicate maybe? The "About WSP" section includes some description of the company; is that considered boilerplate? It's not exactly boilerplate but it's generic about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About WSP" is not explicitly listed as boilerplate, but it's somewhat generic. However it's part of the job posting; we might keep it if it's substantive. But the instruction says "Prefer a few substantive sections over many thin ones." The About WSP could be considered "About the company" but not requested as a section heading. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings like "About WSP". So we should incorporate relevant info from About WSP into existing sections if appropriate, or drop it if not fitting. The About WSP paragraph includes: "WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career. At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base. Your daily contributions to your team will be essential in meeting client objectives, goals and challenges." This contains some benefits info (already covered) and some generic company description. Since we don't have a section for company description, we could incorporate the benefits part into Benefits section (already have). The rest could be considered fluff; maybe we can drop it as it's not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description might be considered substantive? It's generic but still part of posting. However the allowed headings don't include a company overview; we could maybe put it under About the role? But About the role is supposed to describe the role, not the company. 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 says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect only those headings. So we should not add other headings. So we need to decide where to put company description. Could we incorporate it into About the role as a brief context? That might be okay but might deviate from role description. However the instruction says preserve ALL substantive information; we cannot drop it if it's substantive. But maybe it's considered boilerplate? It's not exactly legal/EEO etc. It's more marketing. The instruction didn't explicitly say to remove marketing boilerplate, only cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should keep it. But we have no heading for it; we could put it as a
before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray paragraphs outside sections. But they said "use