Experienced Professional, Civil Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the job description. First part: "Job Description This Opportunity WSP is seeking an Experienced Professional, Civil Engineer to join Pacific Mountain West Transportation Engineering Team. This position will be based out of our Seattle, WA office. Take part in providing technical input into the design, development, and construction of infrastructure projects and systems in the public and private sector. Tasks may include assisting with the research, design, concept development, planning, and construction of roads, bridges, utilities, and other transportation civil infrastructure elements. Generates accurate and concise reports and documentation regarding material, installations, and construction specifications. Ensures that responsibilities are delivered and adhered to with a level of quality that meets acceptable industry standards for design, safety, and functionality. Work with a team to generate accurate and concise documentation regarding assigned aspects of the project." That's about the role and responsibilities. Then "Your Impact" bullet list: Collect, compile, and analyze data ... etc. That's responsibilities. Then "Who You Are" with Required Qualifications and Preferred Qualifications. Then "WSP Benefits" paragraph. Then "Compensation Expected Salary (all locations): $95,000 - $135,000" plus explanation. Then "About WSP" etc. That's company description, maybe not needed as a section? The instruction says we can include sections only when posting has real specific content. Could include "About WSP" but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. We need to decide which sections to include. - About the role: could be the introductory paragraph describing the opportunity, location, purpose. - Responsibilities: the tasks list (Your Impact bullet points). Could also include the earlier tasks. - Requirements: Required Qualifications. - Qualifications: maybe Preferred Qualifications? Or we could combine Required and Preferred under Qualifications? The instruction says separate sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have Required Qualifications list (bullet points). We have Preferred Qualifications list (Professional Engineering License (WA), prior design experience, member of professional orgs). Those could go under Qualifications. Skills: maybe we can extract skills from Required Qualifications: knowledge of civil engineering principles, experience with infrastructure planning, analytical mindset, interpersonal communication, self-leadership, ability to learn new techniques, moderate proficiency with technical writing, office automation, software, etc. Also ability to work schedules, occasional travel, uphold safety, ethical decision-making, experience with discipline-specific design software. Those could be Skills. But we must not invent or summarize away detail. We need to preserve ALL substantive information. So we need to include each piece somewhere, not lose any. We could create sections: - About the role: introductory paragraph. - Responsibilities: list of duties (Your Impact bullet points plus earlier tasks). - Requirements: Required Qualifications bullet list. - Qualifications: Preferred Qualifications bullet list. - Skills: maybe combine some of the Required Qualifications that are skill-like? But we already have Required Qualifications covering many items; maybe we can treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications, and Skills could be omitted if no specific skill section beyond those. However instruction says we can include a section only when posting has real specific content for it. If we don't have distinct skill content beyond what's already in Requirements/Qualifications, we could omit Skills section. But we need to preserve all substantive info; if we omit Skills, we must have placed that info elsewhere. Since Required Qualifications includes many skill-like items, we can keep them there. So we can omit Skills. - Benefits: WSP Benefits paragraph. - Pay: compensation range. - Schedule: mention of ability to work schedules conducive to project-specific requirements that may extend beyond typical workweek, occasional travel. That's schedule info. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include sections with filler like "commensurate with experience". We have actual content. Now we need to format: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information. Let's extract each piece. First, About the role: The introductory paragraph: "WSP is seeking an Experienced Professional, Civil Engineer to join Pacific Mountain West Transportation Engineering Team. This position will be based out of our Seattle, WA office. Take part in providing technical input into the design, development, and construction of infrastructure projects and systems in the public and private sector." Also maybe include "Tasks may include assisting with the research, design, concept development, planning, and construction of roads, bridges, utilities, and other transportation civil infrastructure elements. Generates accurate and concise reports and documentation regarding material, installations, and construction specifications. Ensures that responsibilities are delivered and adhered to with a level of quality that meets acceptable industry standards for design, safety, and functionality. Work with a team to generate accurate and concise documentation regarding assigned aspects of the project." That seems more like responsibilities. But we can split: About the role could be the first two sentences; Responsibilities could be the rest. Let's decide: About the role: "WSP is seeking an Experienced Professional, Civil Engineer to join Pacific Mountain West Transportation Engineering Team. This position will be based out of our Seattle, WA office. Take part in providing technical input into the design, development, and construction of infrastructure projects and systems in the public and private sector." Responsibilities: list of tasks: assisting with research, design, concept development, planning, and construction of roads, bridges, utilities, and other transportation civil infrastructure elements; generating accurate and concise reports and documentation regarding material, installations, and construction specifications; ensuring responsibilities are delivered and adhered to with a level of quality that meets acceptable industry standards for design, safety, and functionality; working with a team to generate accurate and concise documentation regarding assigned aspects of the project; plus the Your Impact bullet points. Your Impact bullet points: Collect, compile, and analyze data from the physical work site, surveys, blueprints, GIS data, subsurface utility information, maps, geotechnical data, and other matrices for project development, design, and construction. Perform professional civil engineering work and assist with conducting research and inspections of proposed and existing site conditions, resources, building, infrastructure, and transportation channels to determine conformance with applicable rules, standards, and construction or operating permits. Work as an individual or as part of a cross-functional team of engineers, planners, and scientific professionals to execute project work, assist with laying out installations, establishing reference points/elevations/grades to guide construction, calculating costs and quantities of material/equipment/labor, and ensuring project work conforms with specifications, permit applications, compliance documentation, and regulatory and technical analysis memos. Provide technical input during various stages of project, including preliminary design, final design and contract documentation including cost estimates and specifications. Perform basic design tasks and drawings using computer-aided design (CADD) to develop conceptual transportation projects in AutoCAD, Civil 3D, InRoads/OpenRoads and/or MicroStation. Assist with work plan preparation and coordination of field/site work and permitting. Perform standard computations and analysis. Discuss and propose solutions to technical issues. Maintain positive team relationships working with cross-functional teams in executing project work. Assist and coordinate with key staff across disciplines (i.e. drainage, structures) as required. Complete training on assigned tasks. We need to preserve all these as list items. Now Requirements: Required Qualifications bullet list: - Bachelor’s Degree in Engineering, or closely related discipline (or equivalent experience). - 3 to 5 years of relevant post education experience in engineering discipline and prior civil design experience. - Engineer in Training Certification. - Knowledge of civil engineering principles, practices, process, design/build, and the application to permitting and project work-related issues. - Experience with infrastructure planning, design, and construction management; including rehabilitation and new design. - Analytical mindset with an ability to exercise sound judgement in evaluating situations and making decisions. - Competent interpersonal and communication skills when interacting with others. - Capable self-leadership with attention to detail, multi-tasking, and prioritization of responsibilities in a dynamic work environment. - Ability to learn new techniques, perform multiple tasks simultaneously, follow instruction, work independently, and comply with company policies. - Moderate proficiency with technical writing, office automation, software, technology, math principles, spreadsheets, and other tools including Word, Excel, Outlook, Teams and PowerPoint. - Ability to work schedules conducive to project-specific requirements that may extend beyond the typical workweek. - Uphold workplace safety and abide by WSP’s health, safety and drug/alcohol and harassment policies. - Exercise responsible and ethical decision-making regarding company funds, resources and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures. - Occasional travel may be required depending on project-specific requirements. - Experience with discipline-specific design software (i.e., MicroStation, AutoCAD, Civil 3D, ArcGIS, InRoads,). Note: There's duplicate lines: "Ability to work schedules conducive to project-specific requirements that may extend beyond the typical workweek." appears twice; also "Occasional travel may be required depending on project-specific requirements." appears twice. We should deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines are substantive? They are repeated; we could keep only one instance to avoid redundancy but that might be considered summarizing away detail? However duplicates are likely accidental; but we could keep one instance as it's same info. The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. Good. Thus we need to remove duplicate lines. Now Preferred Qualifications: - Professional Engineering License (WA). - Prior design experience related to the degree of study and the specific engineering discipline. - A member of and/or actively participate in local professional practice organizations. Now Benefits: WSP provides a comprehensive suite of benefits focused on a providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings. We should preserve that as a list maybe? It's prose with semicolons; we could turn into

  • each benefit. The instruction: Use
    • for any list of duties/requirements/benefits. So we should list each benefit as
    • . Let's parse: - coverage related to medical - dental - vision - disability - life - retirement savings - paid sick leave - paid vacation (or other personal time) - paid parental leave - paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings. We could keep as separate items. Now Pay: Compensation Expected Salary (all locations): $95,000 - $135,000 plus explanation: "WSP USA is providing the compensation range that the company in good faith believes it might pay and offer for this position, based on the successful applicant’s education, experience, knowledge, skills, abilities in addition to internal equity and specific 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, and/or federal law." We need to preserve all substantive info. That's a bit long; we can put in

      . Now Schedule: we have ability to work schedules conducive to project-specific requirements that may extend beyond the typical work