Senior Manager
for sections: 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, job title is Senior Manager (Transportation team). Not to repeat as heading.
We need sections:
- About the role: maybe the introductory paragraph: "This Opportunity WSP USA is seeking a Senior Manager to join our Transportation team in our Springfield, IL office. This is an opportunity to grow our existing team of engineers, designing some of the most complex and impactful transportation projects in central and southern Illinois, including the metropolitan St. Louis area. At WSP, you’ll have the opportunity to shape your career to make it what you want it to be. Our central and southern Illinois team focuses on delivering projects for our clients while mentoring and developing team members to prepare them for future opportunities. Here at WSP, everything is within our reach-and yours as a WSP employee. Join us and help shape the future!" That's about the role.
- Your Impact: list of duties: bullet points. That could be Responsibilities.
- Who You Are: Required Qualifications and Preferred Qualifications. Could be Requirements and Qualifications sections.
- Skills: maybe list of skills like communication, OpenRoads Designer, Microsoft Office, etc.
- Benefits: WSP Benefits paragraph.
- Pay: Compensation Expected Salary: $107,2600-$183,800 (note typo: $107,2600 likely $107,260? but we preserve as given). Also note they mention compensation range.
- Schedule: Not mentioned. No schedule info. So we should not include Schedule section.
- Also maybe "About WSP" could be considered but not required heading; but we could include as "About the company"? Not in list. Probably ignore.
We must not include boilerplate like EEO, legal, etc.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to avoid repeating job title as heading.
We need to not put Job ID etc.
We need to output only HTML fragment.
Let's extract content.
First, "About the role" prose: combine the first paragraph(s) up to "Your Impact". Actually "Your Impact" is a heading in the original but we will treat as Responsibilities.
Thus:
About the role
WSP USA is seeking a Senior Manager to join our Transportation team in our Springfield, IL office. This is an opportunity to grow our existing team of engineers, designing some of the most complex and impactful transportation projects in central and southern Illinois, including the metropolitan St. Louis area. At WSP, you’ll have the opportunity to shape your career to make it what you want it to be. Our central and southern Illinois team focuses on delivering projects for our clients while mentoring and developing team members to prepare them for future opportunities. Here at WSP, everything is within our reach-and yours as a WSP employee. Join us and help shape the future!
Now Responsibilities: list from "Your Impact" bullet points.
Original bullet points (each line starts with a verb):
- Utilize relationships with clients to achieve WSP's business development goals
- Develop working relationships with clients and consultant partners
- Build and expand a local team to support client needs
- Mentor existing and new staff
- Lead tasks & design teams in the execution of projects
- Provide technical expertise in various stages of project, including preliminary design, final design, and contract documentation including cost estimates and specifications
- Discuss and propose solutions to technical issues during design
- 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
- Collaborate with key staff across disciplines (i.e. drainage, structures) as required
We need to put these in - .
Now Requirements: maybe "Who You Are Required Qualifications". That includes:
- B.S. in Civil Engineering or closely related field.
- 15+ years of experience in the Transportation engineering field
- Possess strong verbal and written communication skills
- Professional Engineer’s License in Illinois, Missouri, Iowa desired.
- Hands-on experience in OpenRoads Designer
- Proficiency in Microsoft Office, including Word and Excel
- Ability to implement WSP's Quality Control Procedures
We could put these under Requirements heading as a list.
Qualifications: maybe "Preferred Qualifications". That includes:
- Master’s degree in engineering.
- Experience managing small to mid-size projects.
- Leadership experience working with IDOT, and other local agencies
- Business development experience
- Experience in leading and mentoring a team
- The selected candidate must have the ability to work in the United States immediately.
- Occasional travel may be required depending on project-specific requirements.
We could put these under Qualifications heading as list.
Skills: maybe we could extract specific skills: strong verbal and written communication skills, OpenRoads Designer, Microsoft Office (Word, Excel), ability to implement WSP's Quality Control Procedures, etc. But we already have those in Requirements. Could still have a Skills section but might duplicate. The instruction: prefer a few substantive sections over many thin ones. Could combine skills into Requirements or Qualifications. But we have separate headings list; we can include Skills if there is specific content. We could list skills like: communication, OpenRoads Designer, Microsoft Office, QC procedures. However those are already in Requirements. Might be okay to have Skills section with those items.
But we need to avoid duplication? Not explicitly forbidden, but we should preserve all substantive information; duplication is okay if it's present in original? The original doesn't have a separate "Skills" section; it's embedded. Creating a Skills section might be considered inventing a section not present. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid creating a section that groups content that exists elsewhere, but we should not invent headings that aren't implied. However the list of allowed headings includes Skills, so we can use it if there is specific skill content. The posting does mention skills: strong verbal and written communication skills, Hands-on experience in OpenRoads Designer, Proficiency in Microsoft Office, Ability to implement WSP's Quality Control Procedures. Those are skills. So we can create a Skills section with those items.
But we must ensure we don't lose any info; we can keep them also in Requirements if we want, but that would duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's repeating. Might be okay but could be considered redundant. Safer to not duplicate; we can move skill items to Skills section and remove them from Requirements. However Requirements also includes qualifications like degree, years experience, PE license, etc. Those are not skills. So we can split.
Thus:
Requirements (list):
- B.S. in Civil Engineering or closely related field.
- 15+ years of experience in the Transportation engineering field
- Professional Engineer’s License in Illinois, Missouri, Iowa desired.
- Ability to implement WSP's Quality Control Procedures (maybe this is skill but also requirement). Actually it's a requirement. We'll keep it in Requirements.
Skills (list):
- Strong verbal and written communication skills
- Hands-on experience in OpenRoads Designer
- Proficiency in Microsoft Office, including Word and Excel
But note "Ability to implement WSP's Quality Control Procedures" could be considered a skill; but we already placed in Requirements. Could also move to Skills. Let's decide: Keep it in Requirements as it's a procedural ability.
Now Benefits: paragraph from WSP Benefits.
Original: "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."
We'll put that in
under Benefits heading.
Pay: Compensation Expected Salary: $107,2600-$183,800 plus explanation. We'll put that in
under Pay heading.
Schedule: none, so omit.
Now also there is "About WSP" paragraph after compensation. Could be considered "About the company" but not in allowed headings. Could ignore or maybe treat as "About the role"? Already have about role. The About WSP is more about the company; we could ignore as not required heading. The instruction: do not put Job ID etc. Not required to include everything; but we should preserve ALL substantive information. If we ignore About WSP, we lose substantive info about the company. However the allowed headings do not include "About the company". But we could incorporate that info into About the role section as additional prose. That would preserve it. Let's add to About the role paragraph after the initial paragraph: "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."
But note that some of that repeats benefits already covered; but it's okay to repeat? Might be considered duplication but preserving all info. However we already have Benefits section; repeating benefits details may be redundant but still preserving. Could be okay.
But we should avoid repeating the same benefit list twice? The instruction does not forbid duplication. It says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not summarizing away; it's preserving. So we can include.
But we need to be careful not to include boilerplate like EEO etc. The About WSP paragraph includes "WSP provides a flexible and agile workplace model..." etc. That's fine.
Now also there is "Are you ready to get started?" and EEO statement etc. Those are boilerplate; we should remove.
Also "Notice To Third Party Agencies" etc. Remove.
Now also "WSP USA (and all of its U.S. companies) is an Equal Opportunity Employer ..." Remove.
Now also "The selected candidate must be authorized to work in the United States." This is a requirement; we should keep it. It appears in Preferred Qualifications? Actually earlier: "The selected candidate must have the ability to work in the United States immediately." That's under Preferred Qualifications? It's listed after "Experience managing small to mid-size projects." Actually it's under Preferred Qualifications? Let's check original: Under Preferred Qualifications: "Master’s degree in engineering.Experience managing small to mid-size projects.Leadership experience working with IDOT, and other local agenciesBusiness development experienceExperience in leading and mentoring a teamThe selected candidate must have the ability to work in the United States immediately.Occasional travel may be required depending on project-specific requirements."
Thus the ability to work in US immediately is a requirement (maybe mandatory). We'll include it under Requirements or Qualifications. Since it's a mandatory condition, we can put under Requirements.
Occasional travel may be required depending on project-specific requirements. That's a condition; we could put under Requirements or maybe under Schedule? Not schedule. Could be under Requirements as a note.
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to avoid repeating job title as heading. We need to not put Job ID etc. We need to output only HTML fragment. Let's extract content. First, "About the role" prose: combine the first paragraph(s) up to "Your Impact". Actually "Your Impact" is a heading in the original but we will treat as Responsibilities. Thus:
About the role
WSP USA is seeking a Senior Manager to join our Transportation team in our Springfield, IL office. This is an opportunity to grow our existing team of engineers, designing some of the most complex and impactful transportation projects in central and southern Illinois, including the metropolitan St. Louis area. At WSP, you’ll have the opportunity to shape your career to make it what you want it to be. Our central and southern Illinois team focuses on delivering projects for our clients while mentoring and developing team members to prepare them for future opportunities. Here at WSP, everything is within our reach-and yours as a WSP employee. Join us and help shape the future!
Now Responsibilities: list from "Your Impact" bullet points. Original bullet points (each line starts with a verb): - Utilize relationships with clients to achieve WSP's business development goals - Develop working relationships with clients and consultant partners - Build and expand a local team to support client needs - Mentor existing and new staff - Lead tasks & design teams in the execution of projects - Provide technical expertise in various stages of project, including preliminary design, final design, and contract documentation including cost estimates and specifications - Discuss and propose solutions to technical issues during design - 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 - Collaborate with key staff across disciplines (i.e. drainage, structures) as required We need to put these in- .
Now Requirements: maybe "Who You Are Required Qualifications". That includes:
- B.S. in Civil Engineering or closely related field.
- 15+ years of experience in the Transportation engineering field
- Possess strong verbal and written communication skills
- Professional Engineer’s License in Illinois, Missouri, Iowa desired.
- Hands-on experience in OpenRoads Designer
- Proficiency in Microsoft Office, including Word and Excel
- Ability to implement WSP's Quality Control Procedures
We could put these under Requirements heading as a list.
Qualifications: maybe "Preferred Qualifications". That includes:
- Master’s degree in engineering.
- Experience managing small to mid-size projects.
- Leadership experience working with IDOT, and other local agencies
- Business development experience
- Experience in leading and mentoring a team
- The selected candidate must have the ability to work in the United States immediately.
- Occasional travel may be required depending on project-specific requirements.
We could put these under Qualifications heading as list.
Skills: maybe we could extract specific skills: strong verbal and written communication skills, OpenRoads Designer, Microsoft Office (Word, Excel), ability to implement WSP's Quality Control Procedures, etc. But we already have those in Requirements. Could still have a Skills section but might duplicate. The instruction: prefer a few substantive sections over many thin ones. Could combine skills into Requirements or Qualifications. But we have separate headings list; we can include Skills if there is specific content. We could list skills like: communication, OpenRoads Designer, Microsoft Office, QC procedures. However those are already in Requirements. Might be okay to have Skills section with those items.
But we need to avoid duplication? Not explicitly forbidden, but we should preserve all substantive information; duplication is okay if it's present in original? The original doesn't have a separate "Skills" section; it's embedded. Creating a Skills section might be considered inventing a section not present. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid creating a section that groups content that exists elsewhere, but we should not invent headings that aren't implied. However the list of allowed headings includes Skills, so we can use it if there is specific skill content. The posting does mention skills: strong verbal and written communication skills, Hands-on experience in OpenRoads Designer, Proficiency in Microsoft Office, Ability to implement WSP's Quality Control Procedures. Those are skills. So we can create a Skills section with those items.
But we must ensure we don't lose any info; we can keep them also in Requirements if we want, but that would duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's repeating. Might be okay but could be considered redundant. Safer to not duplicate; we can move skill items to Skills section and remove them from Requirements. However Requirements also includes qualifications like degree, years experience, PE license, etc. Those are not skills. So we can split.
Thus:
Requirements (list):
- B.S. in Civil Engineering or closely related field.
- 15+ years of experience in the Transportation engineering field
- Professional Engineer’s License in Illinois, Missouri, Iowa desired.
- Ability to implement WSP's Quality Control Procedures (maybe this is skill but also requirement). Actually it's a requirement. We'll keep it in Requirements.
Skills (list):
- Strong verbal and written communication skills
- Hands-on experience in OpenRoads Designer
- Proficiency in Microsoft Office, including Word and Excel
But note "Ability to implement WSP's Quality Control Procedures" could be considered a skill; but we already placed in Requirements. Could also move to Skills. Let's decide: Keep it in Requirements as it's a procedural ability.
Now Benefits: paragraph from WSP Benefits.
Original: "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."
We'll put that in
under Benefits heading. Pay: Compensation Expected Salary: $107,2600-$183,800 plus explanation. We'll put that in
under Pay heading. Schedule: none, so omit. Now also there is "About WSP" paragraph after compensation. Could be considered "About the company" but not in allowed headings. Could ignore or maybe treat as "About the role"? Already have about role. The About WSP is more about the company; we could ignore as not required heading. The instruction: do not put Job ID etc. Not required to include everything; but we should preserve ALL substantive information. If we ignore About WSP, we lose substantive info about the company. However the allowed headings do not include "About the company". But we could incorporate that info into About the role section as additional prose. That would preserve it. Let's add to About the role paragraph after the initial paragraph: "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." But note that some of that repeats benefits already covered; but it's okay to repeat? Might be considered duplication but preserving all info. However we already have Benefits section; repeating benefits details may be redundant but still preserving. Could be okay. But we should avoid repeating the same benefit list twice? The instruction does not forbid duplication. It says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not summarizing away; it's preserving. So we can include. But we need to be careful not to include boilerplate like EEO etc. The About WSP paragraph includes "WSP provides a flexible and agile workplace model..." etc. That's fine. Now also there is "Are you ready to get started?" and EEO statement etc. Those are boilerplate; we should remove. Also "Notice To Third Party Agencies" etc. Remove. Now also "WSP USA (and all of its U.S. companies) is an Equal Opportunity Employer ..." Remove. Now also "The selected candidate must be authorized to work in the United States." This is a requirement; we should keep it. It appears in Preferred Qualifications? Actually earlier: "The selected candidate must have the ability to work in the United States immediately." That's under Preferred Qualifications? It's listed after "Experience managing small to mid-size projects." Actually it's under Preferred Qualifications? Let's check original: Under Preferred Qualifications: "Master’s degree in engineering.Experience managing small to mid-size projects.Leadership experience working with IDOT, and other local agenciesBusiness development experienceExperience in leading and mentoring a teamThe selected candidate must have the ability to work in the United States immediately.Occasional travel may be required depending on project-specific requirements." Thus the ability to work in US immediately is a requirement (maybe mandatory). We'll include it under Requirements or Qualifications. Since it's a mandatory condition, we can put under Requirements. Occasional travel may be required depending on project-specific requirements. That's a condition; we could put under Requirements or maybe under Schedule? Not schedule. Could be under Requirements as a note.