Jobs · New Jersey

Structural Engineer - Bridge Inspection Team Leader

WSP in the U.S. · Oradell, NJ · 1 mo ago
Hybrid$89k–$135k/yrFull-time
We need to output HTML fragment with headings

for 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. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job description. Sections present: - About the role: The initial paragraph after "Job Description This Opportunity ..." includes description of role, location, etc. Could be "About the role". We'll include. - Responsibilities: The "Your Impact" bullet list (though not bullet but sentences). We'll extract responsibilities. - Requirements: The "Who You Are" includes Required Qualifications. Could be split into Requirements and Qualifications? The instruction says we can have sections Requirements and Qualifications. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = maybe preferred? But we have both Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements section, and Preferred Qualifications to Qualifications section. Also Skills could be separate: maybe list of skills like proficiency with software, communication, etc. But we can combine. We need to avoid filler sections like Pay/Schedule/Benefits unless actual content. We have Compensation (Pay) with salary range. Benefits section present. Schedule? Not explicitly given, but there is mention: "Ability to work schedules conducive to project-specific requirements that may extend beyond the typical workweek." Also "This position has the potential to work 50% of the time in the field and 50% in the office." That's schedule info (field/office split). So we can include Schedule section. We must not include placeholder like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove. We must preserve all substantive info. So we need to include details: location options, team leader role, responsibilities list, required qualifications (Bachelor's degree, NCBI certification, 3+ years experience, NHI courses, NJ PE license, proficiency, physical capabilities, 50/50 field/office, driver's license, interpersonal skills, ability to work independently, guidance, advanced proficiency with technical writing, MS Office, safety, ability to work schedules, occasional travel). Preferred qualifications list. Benefits list. Compensation range. About WSP description maybe could be part of About the role or separate? Could be included in About the role or maybe a separate "About WSP" but not in allowed headings. Since only allowed headings are those listed, we should fold About WSP into About the role or maybe into Responsibilities? Better to put in About the role as it's about the company and role. We must not include navigation/legal/EEO etc. So remove the Equal Opportunity Employer paragraph, notice to third party agencies, etc. We must output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (combined intro and location, team leader, WSP mission, etc.)

Responsibilities

  • ...
  • ...

Requirements

  • ...
  • ...

Qualifications

  • ...
  • ...
(for preferred qualifications)

Skills

  • ...
  • ...
(maybe combine some skill items from required and preferred? But we already have required and qualifications sections; maybe Skills can include technical proficiencies: MicroStation, Visio, AutoCAD, MS Office, engineering calculation software, etc. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. Could combine Required Qualifications and Preferred Qualifications into Requirements and Qualifications sections; Skills maybe not needed if covered. But we need to decide. We have sections allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Benefits, Pay (compensation), Schedule (field/office split, ability to work schedules, occasional travel). Skills maybe we can include technical skills like proficiency with MicroStation, Visio, AutoCAD, MS Office, engineering calculation software, etc. But some of those are already in required qualifications (proficient knowledge of structural engineering principles, practices, process, design/build, and application to project work-related issues; demonstrated interest; physically capable; etc.) and also "Advanced proficiency with technical writing, office automation, software, spreadsheets, technology, and tools." and "Working knowledge of Microsoft Office (Word, Excel, Powerpoint) is required." Also "Proficient knowledge of structural engineering principles..." etc. Could treat those as Skills. But we already have Required Qualifications covering many. To avoid duplication, maybe we put Skills separate for specific tools: MicroStation, Visio, AutoCAD, engineering calculation software (AASHTOWare Bridge Rating (BrR), Bentley LARS, Mathcad, Sap2000, etc.), MS Office, etc. However some of those appear in Preferred Qualifications (experience with engineering calculation software). So we could put Skills section for tools and technical abilities. But we must not repeat content; we can still include but ensure we preserve all info. Duplication is okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to avoid duplication but still preserve all info by distributing across sections. Let's plan: About the role: intro paragraph about opportunity, location, team leader, WSP mission, impact. Responsibilities: list of duties from "Your Impact" bullet points. Requirements: list of required qualifications (Bachelor's degree, NCBI certification, 3+ years experience, NHI courses, NJ PE license, proficiency in structural engineering principles, demonstrated interest, physically capable, 50/50 field/office, driver's license, interpersonal communication skills, ability to work independently and provide guidance, advanced proficiency with technical writing/office automation/spreadsheets/technology/tools, working knowledge of MS Office, safety record, ability to work schedules, occasional travel). Also maybe include "Successful completion of a Motor Vehicle Record check and a valid Driver’s License is required." That's part of requirements. Qualifications: list of preferred qualifications (NHI NSTM course, experience with engineering calculation software, comfortable working at heights 40ft+, interest in ropes/SPRAT, enjoys outdoors, experience inspecting complex bridges, FAA Part 107 or interest in UAS drone, familiarity with NDT techniques, interest in programming/databases/data analytics/APIs). Skills: maybe we can list specific technical skills: MicroStation, Visio, AutoCAD, MS Office, engineering calculation software (AASHTOWare Bridge Rating (BrR), Bentley LARS, Mathcad, Sap2000), technical writing, office automation, spreadsheets, etc. But many already in requirements. To avoid duplication, maybe we skip Skills section and put those under Requirements or Qualifications. However the instruction says we can include Skills section only if posting has real specific content for it. The posting does mention specific tools: MicroStation, Visio, AutoCAD, MS Office, engineering calculation software. So we could create Skills section for those. But we must ensure we don't lose any info; we can still mention them in Skills and not repeat elsewhere (or we can mention them only in Skills). However the required qualifications also mention "Advanced proficiency with technical writing, office automation, software, spreadsheets, technology, and tools." and "Working knowledge of Microsoft Office (Word, Excel, Powerpoint) is required." Those are skills. So we could move those to Skills section and not duplicate in Requirements. But then Requirements would lose mention of those skills. However we could keep them in Requirements as part of "advanced proficiency..." but that's okay if we also list them in Skills; duplication is not prohibited but maybe not ideal. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have fewer sections: combine Skills into Requirements or Qualifications. Since we already have Requirements and Qualifications, we can keep them there. So we may omit Skills section entirely. But we need to decide if we must include Skills if we have content. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It does not say we must include Skills if we have content; we can choose not to include it if we prefer fewer sections. So we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to write HTML. We'll need to escape any HTML special characters? Not needed as plain text. Let's craft About the role paragraph: "WSP is seeking a Structural Engineer - Bridge Inspection Team Leader to join our Bridge & Infrastructure Inspection Team. This role can be based out of any WSP office in New Jersey such as Newark-NJ, Lawrenceville-NJ, Morristown-NJ, and more. It is an exciting opportunity for an experienced team leader with people leadership skills ready to lead within the Bridge & Infrastructure Inspection Team. At WSP, we are driven by inspiring the right people to be part of our future-focused business objectives, building communities and expanding our skylines through teamwork. Join a collaborative team of experts and contribute to projects that help shape communities and the future." We can combine. Now Responsibilities: extract from "Your Impact" list: - Work with our Bridge & Infrastructure Inspection Team on a variety of inspection related projects. - Work as a Team Leader on Bridge, Tunnel & Ancillary Inspections. - Perform professional structural engineering work and inspections. - Assist in the preparation of Bridge & Tunnel Load Ratings. - Assist with the development of plans/sketches using MicroStation, Visio, and AutoCAD. - Work as an individual or as part of a cross-functional team of engineers, architects, planners, and scientific professionals to execute project work on multiple concurrent projects. - Provide guidance and training to entry-level engineers. - Support a variety of engineering tasks with the goal to develop technical, social, and ethical skills. - Assist with project research, field work, and preliminary design calculations and analysis. - Support preparation of cost proposals and scope of work documents. - Assist in collecting and maintaining project documentation. - Complete training on assignment specific tasks. - Remain current in latest structural engineering techniques and practices. - 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. - Perform additional responsibilities as required by business needs. We'll put each as
  • . Now Requirements (required qualifications): List: - Bachelor’s Degree in Structural or Civil Engineering, or equivalent. - Nationally Certified Bridge Inspector (NCBI) certification through the successful completion of an FHWA approved comprehensive bridge inspection training course. - 3+ years of experience in bridge, tunnel and/or ancillary inspection or design or other infrastructure related work. - NHI Course 130055 Safety Inspection of In-Service Bridges Certificate and if required, NHI Course 130053 Refresher Certificate. - New Jersey PE license or the ability to obtain it promptly. - Proficient knowledge of structural engineering principles, practices, process, design/build, and the application to project work-related issues. - Demonstrated interest in structures, transportation or related field and have a strong desire to advance skills related to WSP’s work and projects. - Physically capable of performing continuous field work, including working at heights and in close quarters; climbing; carrying ladders and gear; working in adverse weather conditions; working in and around water; working at night; around moving vehicles; etc. - This position has the potential to work 50% of the time in the field and 50% in the office. (Maybe schedule but we can keep here.) - Successful completion of a Motor Vehicle Record check and a valid Driver’s License is required. - Competent interpersonal and communication skills when interacting with others, expressing ideas effectively and professionally to an engineering and non-engineering audience. -
  • Similar jobs