Deputy Project Manager - Transportation

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: About the role (the initial paragraph about opportunity). Responsibilities (the "Your Impact" bullet list). Requirements (the "Who You Are" includes Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe not explicit but could be derived from required qualifications like proficiency with software etc). Benefits (the "WSP Benefits" paragraph). Pay (the "Compensation Expected Salary" range). Schedule (maybe not explicit; there is mention of occasional travel, flexibility, but not schedule specifics. So we should not include Schedule unless there is real specific content. There's mention of "Strong ability to quickly adapt to change and demonstrate flexibility to a variety of schedules and hours to meet business needs." That's somewhat schedule but not specific. Probably we should not create Schedule section because it's not concrete. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated, Benefits stated, Schedule not specific, so omit. We need to not repeat job title as heading. No Job ID. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About WSP" maybe? That's about the company; could be considered boilerplate? It's not EEO but it's generic about company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About WSP" is not explicitly listed but could be considered boilerplate? It's not required to keep; but it's substantive info about the company. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About WSP paragraph as it's substantive. However, we need to decide where to place it. Could be under a heading "About the company" but we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". So maybe we should not create a heading for it; we could embed it in a

  without heading? But 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. those). Likely they expect only those headings. So we should not add a heading for About WSP; we could incorporate it into a

  under maybe "About the role"? But that would mix. Better to keep it as a

  without heading? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other headings, but they give examples. Safer to stick to those. So we need to fit content into those sections. We have: - About the role: initial paragraph about opportunity, maybe also the "About WSP" could be considered part of role? Might be okay to include under About the role. - Responsibilities: the "Your Impact" bullet list (multiple sentences). We'll turn each sentence into

  . - Requirements: Required Qualifications bullet list. - Qualifications: Preferred Qualifications. - Skills: maybe we can extract skill-related items from Required Qualifications: proficiency with office automation, discipline-specific design software, etc. Could be a separate Skills section. But we already have Required Qualifications includes many skill items. Could we treat Required Qualifications as Requirements and Preferred Qualifications as Qualifications, and Skills maybe not needed. However we need to avoid thin sections. If we put Skills with little content, better to omit. So we can omit Skills. - Benefits: the WSP Benefits paragraph. - Pay: compensation range. - Schedule: omit. We need to ensure we don't include boilerplate like "WSP USA is providing the compensation range..." that's part of Pay, we keep. We need to remove duplicated lines, EEO statements, etc. At the end there is EEO statement, Notice To Third Party Agencies, etc. Remove those. Also remove "Are you ready to get started?" etc. Now craft HTML. Structure:

  About the role

  WSP is currently initiating a search for a Deputy Project Manager for our New York City, NY office. Be involved in projects with our Transportation and Infrastructure Team and be a part of a growing organization that meets our client’s objectives and solves their challenges. This role provides leadership within a sector of organization to ensure transit and rail engineering subject matter, technical deliverables, infrastructure projects and programs are delivered with a level of quality that meets or exceeds acceptable industry and company standards for design, safety, and functionality. Responsible for SME innovation and administration, ensuring corporate compliance with all Local, State, and Federal engineering, construction, and safety regulations, and providing pragmatic direction to address current and future challenges in a rapidly-changing and complex business climate.

  Then Responsibilities:

  Responsibilities

  • Provide proactive and strategic leadership for transportation and infrastructure engineering disciplines and functions, offering direction, expertise, and support to ensure project and work site deliverables are successfully achieved within the business sector.
  • Lead larger-scale more complex projects ensuring contributors know what they are required to do and by when, preparing and overseeing relevant project budgets, monitoring external events, tracking hours and expenses, ensuring satisfactory performance, and supervising subcontractors, contract work, and employees.
  • Lead technical aspects of contract negotiation, presentations, and meetings.
  • Responsible for the profitable performance of the individual projects and the successful completion of the projects within the specified area.
  • Ensure that engineering discipline certifications, accreditations, and value proposition is developed and continuously improved.
  • Conduct needs analyses and client value surveys to align the engineering discipline’s function with business and project strategy, identifying and addressing any skill gaps or risks within the sector business operations.
  • Schedule engineering discipline meetings, providing updates and recommendations to ensure that all reasonable and proper measures are taken to inculcate discipline expertise and innovation into project work.
  • Develop and inform proposal and project scopes, timelines, pricing, and budgetary metrics – and accountable for planning, development and management of projects in compliance with all applicable City/State/Federal codes and regulations, and in accordance with all acceptable engineering practices.
  • Interpret and summarize data, including reports and documents that result in sound engineering and regulatory conclusions.
  • Provide verbal and/or written inputs to multi-disciplinary project teams and contribute to providing high level strategic advice to clients.
  • Mentor staff to support their growth and professional development.
  • Manage and provide performance guidance and leadership to assigned staff.
  • Remain current in latest transit and rail engineering techniques and practices.
  • Collaborate with professionals from a variety of disciplines to provide “trusted advisor” service and future ready solutions for clients.
  • 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.

  Requirements (Required Qualifications):

  Requirements

  • Bachelor’s Degree in Engineering, or closely related discipline.
  • 10+ years of relevant post education experience in engineering, prior transit and rail experience, and infrastructure design.
  • Engineer license required (multi-state preferred).
  • Project management and quality management experience leading a team of quality engineers, inspectors, and assessors.
  • Proficiency with transportation and infrastructure engineering principles, practices, process, and design/build, standard of care, and the application to permitting and project work-related issues.
  • Advanced proficiency with making technical computations and calculations involving the application of engineering principles, understanding plans and specifications and making factual comparisons to the appropriate regulations.
  • Works independently and provides guidance and leadership to mid-level to senior level team or project members, with strict adherence to QA/QC.
  • Excellent leadership and interpersonal communication skills with the ability to effectively, persuasively, and tactfully interact with employees at all levels of the organization.
  • Tactical lateral thinking and strong analytical skills with attention to detail and prioritization of responsibilities in a pressure work environment.
  • Ability to elicit cooperation from a wide variety of sources, including senior management, clients, regulators, and company-wide staff, including those with whom no formal hierarchical relationship exits.
  • Proficiency with office automation, discipline-specific design software (i.e., MicroStation, AutoCAD, Civil 3D, OpenRail), technology, math principles, predictive models, spreadsheets, and tools.
  • Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies.
  • Strong ability to quickly adapt to change and demonstrate flexibility to a variety of schedules and hours to meet business needs.
  • Occasional travel may be required depending on project-specific requirements.

  Qualifications (Preferred Qualifications):

  Qualifications

  • Master’s Degree in Engineering.
  • Strong experience in managing the review and approval of documents and discipline-specific deliverables, certifications, processes, and plans in a multi-project environment is highly desirable.

  Benefits:

  Benefits

  WSP provides a comprehensive suite of benefits focused on 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.

  Pay:

  Pay

  Expected Salary (all locations): $143,600 - $205,000. 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 should not include Schedule. Check for any duplicated lines: we have not included duplicated. Check for boilerplate: removed EEO, Notice To Third Party Agencies, "Are you ready to get started?", "WSP USA (and all of its U.S. companies) is an Equal Opportunity Employer..." etc. Check for any mention of "About WSP" we omitted; but we kept some of that content in About the role? Actually we included the initial paragraph about opportunity but not the later "About WSP" paragraph. That later paragraph is somewhat duplicate of earlier but includes more details about WSP USA. Could be considered substantive. Should we include it? It's about the company, not the role. The instruction says preserve ALL substantive information. If we omit it, we lose substantive info about the company. However we have no heading for it; we could incorporate it into About the role as additional paragraph. That would be okay: we can add another

  under About the