Transmission Siting and Permitting Project Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to keep substantive info: role description, responsibilities, qualifications, benefits, compensation. Let's extract sections: - About the role: The description includes "This Opportunity WSP is currently initiating a search for a Transmission Siting and Permitting Project Manager in New England. This position will be located in our Boston, Chelmsford, Foxboro, MA or Merrimack, NH office. Be involved in projects with our Earth & Environment Team and be a part of a growing organization that meets our client’s objectives and solves their challenges. The primary focus for this Transmission Siting and Permitting Project Manager will be on electric transmission line and substation routing and siting, along with renewable energy development projects in New England and adjacent states. The ideal candidate will have an established and successful history of experience in the New England and will be a collaborative and responsive professional with strong communication and organizational skills." That's about the role. - Responsibilities: The bullet list under "Your Impact" includes many items: Managing multiple projects at various stages and locations; Leading project teams for key clients; Leading business development efforts - develop/maintain client relationships and lead proposal preparation; Developing strategy for public involvement programs; attend and participate in open houses, public meetings, and public hearings; Serving as a siting and environmental permitting subject matter expert; Managing and directing routing/siting studies, analyses, and associated reports; Working collaboratively with multi-disciplinary teams which could include engineers, attorneys, planners, permitting and environmental specialists, and real estate experts; Mentoring staff to support their growth and professional development; Exercising responsible and ethical decision-making regarding company funds, resources and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures; Performing additional responsibilities, as required by business needs. We can put these as

• . - Requirements/Qualifications: There's "Who You Are Required Qualifications:" then list of required qualifications. Also "Preferred Qualifications". We can combine into Requirements section maybe separate Required and Preferred? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have a "Requirements" heading for required qualifications, and maybe a "Qualifications" heading for preferred? Or combine? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have multiple of those. We'll include sections that have content. Thus: - About the role (h3) - Responsibilities (h3) - Requirements (h3) for required qualifications - Qualifications (h3) for preferred qualifications (or maybe Skills) - Benefits (h3) for benefits description - Pay (h3) for compensation range - Schedule? Not provided explicitly; there is mention "Must be flexible to a variety of schedules to meet business needs". That's a schedule-related statement but not specific schedule. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we have a statement about flexibility but not a defined schedule. Might be considered schedule info? It says "Must be flexible to a variety of schedules to meet business needs". That's somewhat schedule-related but not a defined schedule. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about schedule flexibility, but not a specific schedule. I'd argue we can include a Schedule section with that statement? However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state something about schedule flexibility, so we could include Schedule. But they also said "Prefer a few substantive sections over many thin ones." Might be better to incorporate schedule flexibility into Requirements or Responsibilities. Since it's a requirement about flexibility, we could put under Requirements. I'd skip Schedule section to avoid thin. Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay. Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: EEO statements, etc. Also remove duplicated lines: there is a duplicated benefits paragraph later (under About WSP). We need to keep only one instance of benefits info. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine the paragraph(s). Ensure we keep all details: location options, involvement with Earth & Environment Team, primary focus, ideal candidate experience, collaborative/responsive, strong communication/organizational skills. We'll put in

  . Second, Responsibilities:

  • each item. Third, Requirements: required qualifications list. We'll need to keep each bullet as
  • . The required qualifications list includes: - Bachelor’s degree in Environmental Studies, Biology, Natural Sciences or Ecology, Environmental Planning, Environmental Science, or related field (or equivalent experience.) - Ten (10) + years of experience managing environmental permitting and planning projects, for a variety of energy-related projects - Ability to work independently and provide guidance and leadership to mid-level to senior level team or project members, with strict adherence to QA/QC - Strong leadership and interpersonal communication skills with the ability to effectively, persuasively, and tactfully interact with employees at all levels of the organization - Demonstrated knowledge and familiarity with New England State agency personnel and decision-makers - Experience in preparing proposals and presentations, and price structuring - Strong written and verbal communication skills, defining and understanding client requirements, managing expectations, and communicating with clients and project staff - Extensive critical thinking and problem-solving skills required to reach conclusions from field observation, data collation, to identify the most effective solutions and accomplish objectives of assigned projects - Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies - Must be flexible to a variety of schedules to meet business needs and able to prioritize responsibilities and quickly adapt to change in a pressure work environment - Occasional travel may be required depending on project-specific requirements We'll keep all. Fourth, Qualifications (preferred): list: - Master’s degree in Biology, Environmental Studies, Natural Sciences or Ecology, Environmental Planning, Environmental Science, or related degree - Project Management Professional certification; other professional certifications as applicable to technical expertise - Contract negotiations and management - Experience preparing and providing expert witness testimony Fifth, Benefits: The benefits description appears twice; we need to keep one comprehensive version. The first benefits paragraph: "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." Later under About WSP: "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." We should combine? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include both benefit statements? They are somewhat overlapping but not identical. The first includes more detail: 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. The second includes: flexible and agile workplace model; 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. We should include both as separate paragraphs under Benefits section, preserving all info. However we must avoid duplication: the second mentions benefits again but less detail. It's not duplicate exactly; it's additional info about flexible workplace model. So we keep both. Thus Benefits section:

    Benefits

    then

    first benefits paragraph

    second benefits paragraph

    . Sixth, Pay: compensation range: "Expected Salary (all locations): $118,500 - $146,500" plus explanation about WSP USA providing compensation range etc. We need to preserve all substantive information. So we include that paragraph. We should not include the EEO statement, the "About WSP" description beyond benefits? The "About WSP" includes description of WSP USA, etc. That is boilerplate? It's about the company; might be considered boilerplate but it's substantive? The instruction: 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 could be considered generic company description. However it's part of the posting; but we might keep it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About WSP" is substantive about the company. However many job postings include such boilerplate; but they didn't explicitly say to remove it. They said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep the About WSP description. However we already used Benefits section; the About WSP also includes a sentence about flexible and agile workplace model and benefits (which we already captured). There's also more: "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. Are you ready to get started?" This is quite a bit of company description. It's not explicitly excluded, so we should keep it. However we might consider it as part of "About the role" or separate section? There's no heading for "About WSP". We could add a section "About the Company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading not in that list. We could incorporate the company description into About the role? But About the role is supposed to be about the role, not company. However we could add a

    after About the role before Responsibilities that contains company info, but that would be without a heading. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having extra paragraphs without headings, but likely they expect sections only with those headings. Safer to include company description under About the role? Might be okay to add a paragraph about the company within About the role section. But the instruction: