Early Professional - Transportation Engineer
WSP in the U.S. · Tacoma, WA · 1 mo ago
Management$66k–$82k/yrVolunteer
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, EEO, legal, etc. Must preserve all substantive info.
Let's parse the job description.
Content:
- Opening: "Job Description This Opportunity WSP is currently initiating a search for a full-time, Early Career Civil Transportation Engineer for our Tacoma, WA office. Be involved in projects with our Pacific Mountain West Transportation Engineering Team and be a part of a growing organization that meets our client's objectives and solves their challenges. Take part in providing local technical assistance for the design, development, and construction of infrastructure projects and systems in the public and private sector. Tasks may include basic assistance with the research, design, concept development, and construction of transportation civil infrastructure. Work with a team to generate accurate and concise documentation regarding assigned aspects of the project. Deliver work product meeting acceptable industry standards for design, safety, and functionality."
That's about the role.
Then "Your Impact" bullet list of tasks/duties.
Then "Who You Are" with Required Qualifications and Preferred Qualifications.
Then "Compensation And Benefits" with benefits description and expected salary range.
Then "About WSP" with company description.
We need sections: About the role (maybe "About the role" heading). Responsibilities (list of duties). Requirements (maybe required qualifications). Qualifications (maybe preferred? but we have both required and preferred; could combine? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content.
We have content for About the role (intro). Responsibilities (Your Impact list). Requirements (Required Qualifications). Qualifications (Preferred Qualifications). Skills (maybe mention proficiency with software, etc). Benefits (benefits description). Pay (salary range). Schedule (maybe mention ability to work schedules conducive to project-specific requirements that may extend beyond typical workweek). That's schedule info.
We must not include sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title as heading. So no heading for Early Career Civil Transportation Engineer.
We must not put Job ID/requisition numbers as headings (none present).
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement at end, the "Notice To Third Party Agencies", the "About WSP" maybe we can keep as "About the role"? Actually "About WSP" is company description; could be part of About the role? But we already have About the role section for role description. The "About WSP" is more about company; could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description somewhere. Could be part of About the role? But that section is about the role, not company. Maybe we can include a section "About WSP" but not in the allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About the company. However we could incorporate company description into About the role or maybe into a brief paragraph under About the role. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. Company description could go under About the role? Might be okay.
We also have "Your Impact" list which is responsibilities.
We have "Who You Are" with required and preferred qualifications.
We have "Compensation And Benefits" with benefits and salary.
We have ability to work schedules beyond typical workweek -> schedule.
We have skills: proficiency with software, technical writing, etc.
Thus we can create sections:
About the role
About the role
... (intro + maybe company description)
Responsibilities
- ... each bullet from Your Impact
Requirements
- ... required qualifications
Qualifications
- ... preferred qualifications
Skills
- ... maybe list of skills: competent interpersonal and communication skills, proficient self-leadership, ability to work independently, basic proficiency with technical writing, software, technology, tools including Word, Excel, Outlook, Teams and PowerPoint, ability to work schedules..., uphold safety, exercise ethical decision-making, occasional travel.
About the role
... (intro + company description maybe)
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
... benefits description
Pay
Expected Salary: $65,600 - $82,000. WSP USA is providing the compensation range and general description of other compensation and benefits that the company in good faith believes it might pay and/or offer for this position based on the successful applicant’s education, experience, knowledge, skills, and abilities in addition to internal equity and geographic location. WSP USA reserves the right to ultimately pay more or less than the posted range and offer additional benefits and other compensation, depending on circumstances not related to an applicant’s sex or other status protected by local, state, or federal law.
Similar jobs
Transportation Engineer, Early Career
Managementapply on job-boards.greenhouse.io
Transportation Engineer, Early Career
apply on job-boards.greenhouse.io
Early Career Transportation Civil Engineer
Engineeringapply on emit.fa.ca3.oraclecloud.com
Early Professional, Civil Engineering
Engineering$60k–$70k/yrapply on emit.fa.ca3.oraclecloud.com
Early Professional, Civil Engineering
apply on emit.fa.ca3.oraclecloud.com
Early Professional, Civil Engineering
Engineering$61k–$100k/yrapply on emit.fa.ca3.oraclecloud.com