Highway/Roadway Engineer 4
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We include only sections with real specific content.
We need to parse the posting.
Company Overview: It's a paragraph describing company. Could be "About the role"? Actually "Company Overview" could be considered "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly.
We have:
- Company Overview: description of company, mission, etc. Could be "About the role"? Might be better as "About the role" but that's about the job. However we have "Job Description" which includes overview of role. So we could have "About the role" heading with the job description paragraph: "Join CDM Smith’s New England Transportation team as a Task Leader for highway design projects..." etc.
- Responsibilities: list of key responsibilities bullet points.
- Skills & Abilities: list of skills.
- Qualifications: list of qualifications (degree, certification, experience, travel, equivalent experience).
- Pay: we have Pay Range Min and Max.
- Schedule? Not mentioned.
- Benefits? Not mentioned explicitly; there is mention of employee experience but not specific benefits. So we should not create Benefits section unless specific content.
- Travel: mention "Domestic and/or international travel may be required. The frequency of travel is contingent..." This could be considered Schedule? Not exactly. There's no separate heading for Travel in allowed list, but we could incorporate into Qualifications or maybe as a note under Qualifications. Since we cannot create new headings not in list, we should fold travel info into Qualifications (maybe as a sentence). Or we could put under "Schedule"? Not appropriate. Better to include travel info within Qualifications paragraph.
- Also there is "Amount Of Travel Required 10% or less". That's specific.
- Also there is EEO statement, background check, etc. Those are boilerplate to remove.
- Also "Additional Pay Range Information" etc. We have pay range.
- Also "Visa Sponsorship Available No". That's not a heading we have; could be included in Qualifications or maybe as a note. But we should preserve substantive information. It says "Visa Sponsorship Available No-We will not support sponsorship in the United States, i.e. H-1B or TN Visas for this position". That's substantive. We could include under Qualifications or maybe a separate section? Not in allowed headings. Could fold into Qualifications as a note.
- Also "Additional Compensation All bonuses at CDM Smith are discretionary and may or may not apply to this position." That's substantive about compensation; could be included under Pay section.
- Also "Pay Range Max USD $175,365.00 Pay Range Min USD $100,194.00". Already.
- Also "Additional Pay Range Information ..." paragraph about compensation factors. Could be included under Pay.
Thus sections:
About the role
-> paragraph with job description overview.
Responsibilities
-> list of responsibilities.
Skills
-> list of skills & abilities.
Qualifications
-> list of qualifications (degree, certification, experience, travel, equivalent experience, visa sponsorship, etc.)
Pay
-> with pay range and additional compensation info.
We should not include Benefits or Schedule as no specific content.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, background check, legal, etc. Remove those.
We need to ensure we keep all substantive details from the posting: company overview? Actually we might not need to include company overview as a separate section because we have About the role covering job description. The company overview paragraph is about the company, not the role. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive. But we don't have a heading for "Company Overview". Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could treat company overview as part of About the role? But About the role is supposed to be about the role, not company. However we could still include company overview as a paragraph under About the role? Might be mixing. But we need to preserve it; we could include it as a paragraph before the About the role heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid having extra paragraphs not under headings. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't say we cannot have other paragraphs outside headings. But we should prefer a few substantive sections over many thin ones. We could include a short intro paragraph for company overview before the headings. That would preserve it.
Thus structure:
Company overview paragraph(s)
About the role
Job description paragraph (the role overview)
Responsibilities
...
Skills
...
Qualifications
...
Pay
Pay range and additional compensation info.
We must not include headings for Requirements (we have Qualifications). Could also include Requirements as synonyms but we have Qualifications.
We must not repeat job title as heading.
Now extract specifics.
Company Overview paragraph(s): The text starts:
"Company Overview Check out this video and find out why our team loves to work here! Join Us! CDM Smith – where amazing career journeys unfold. Imagine a place committed to offering an unmatched employee experience. Where you work on projects that are meaningful to you. Where you play an active part in shaping your career journey. Where your co-workers are invested in you and your success. Where you are encouraged and supported to do your very best and given the tools and resources to do so. Where it’s a priority that the company takes good care of you and your family. Our employees are the heart of our company. As an employer of choice, our goal is to provide a challenging, progressive and inclusive work environment which fosters personal leadership, career growth and development for every employee. We value passionate individuals who challenge the norm, deliver world-class solutions and bring diverse perspectives. Join our team, and together we will make a difference and change the world."
We need to keep all that. Remove "Check out this video and find out why our team loves to work here! Join Us!" maybe that's promotional but still part of overview. It's substantive? It's a call to action; but we can keep it. It's not boilerplate. We'll keep.
Now About the role: The job description paragraph after "Job Description". It says:
"Join CDM Smith’s New England Transportation team as a Task Leader for highway design projects in the New England region. This position can be based in either our Boston, MA, East Hartford, CT, or Manchester, NH offices. You’ll play a pivotal role in advancing technical excellence, mentoring junior staff, and delivering innovative solutions for complex transportation challenges."
That's the overview. We'll put that as .
Now Responsibilities: list under "Key Responsibilities". Items:
- Project Leadership: Coordinate the technical advancement of highway design projects, communicate the vision for final deliverables, and ensure technical accuracy throughout the project lifecycle.
- Oversight & Management: Provide day-to-day direct oversight of transportation planning and design projects, ensuring milestones and quality standards are met.
- Mentorship: Supervise, review, and mentor junior engineers. Provide technical guidance, training, and support for professional growth within the discipline and firm.
- Design Development: Develop project design criteria, alignments, construction plans, specifications, and cost estimates.
- Collaboration: Work closely with Project Technical Leaders and Project Managers to deliver high-complexity projects tailored to unique client requirements.
- Compliance: Review draft designs for compliance with federal, state, and local regulations. Sign and seal engineering designs as required.
- Site Studies: Perform site reviews and studies to ensure designs align with location specifications; update design requirements as needed.
- Proposal Support: Collaborate with sales staff to create proposals in response to client RFPs. Review draft proposals for adherence to firm, industry, and regulatory standards.
We'll make each as
- .
Now Skills & Abilities: list:
- Expert Knowledge of computer assisted design and drafting (CADD) 3D and 4D software and practices.
- Expert Knowledge of engineer principles of design.
- Expert Knowledge of Microsoft business software (excel, word, etc.).
- Excellent verbal and written communications skills.
- Strong knowledge of federal, state and local regulations.
- Basic knowledge of design standards (AASHTO, NACTO, etc.).
We'll make
- .
Now Qualifications: list:
- Bachelor's degree in Civil, Transportation, or Structural Engineering or related discipline.
- Certification as an Engineer in Training (EIT) or passing the Fundamentals of Engineering (FE) exam in states where an EIT is not obtainable (within 18 months of hire or promotion or transfer).
- 5 years of related experience.
- Domestic and/or international travel may be required. The frequency of travel is contingent on specific duties, responsibilities, and the essential functions of the position, which may vary depending on workload and project demands.
- Equivalent additional directly related experience will be considered in lieu of a degree.
- Amount Of Travel Required 10% or less.
- Visa Sponsorship Available No-We will not support sponsorship in the United States, i.e. H-1B or TN Visas for this position.
We need to preserve all. We'll make each as
- . Note: The travel sentence and amount of travel required could be combined but we keep separate.
Now Pay: we have:
"Additional Pay Range Information CDM Smith is committed to fair and equitable compensation practices. This pay range is a good faith estimate representative of all experience levels for the geographic location assigned to the position. In addition to geographic location, a candidate’s salary is determined by several other factors including, but not limited to, the role, function and associated responsibilities, relevant work experience, skills, required certifications, and education/training.
Additional Compensation All bonuses at CDM Smith are discretionary and may or may not apply to this position.
Pay Range Max USD $175,365.00 Pay Range Min USD $100,194.00"
We'll combine into a paragraph.
We should not include "Additional Pay Range Information" as heading; just paragraph.
Now ensure we removed boilerplate: EEO Statement, Background Check and Drug Testing Information, Massachusetts Applicants, Agency Disclaimer, etc.
Also remove "Check out this video and find out why our team loves to work here! Join Us!"? It's not boilerplate but it's a call to action; we can keep.
Now produce HTML.
We need to ensure proper nesting:
for prose,
- for lists.
We'll output:
Company Overview ...
About the role
Join CDM Smith’s New England Transportation team as a Task Leader for highway design projects in the New England region. This position can be based in either our Boston, MA, East Hartford, CT, or Manchester, NH offices. You’ll play a pivotal role in advancing technical excellence, mentoring junior staff, and delivering innovative solutions for complex transportation challenges.
Responsibilities
- Project Leadership: Coordinate the technical advancement of highway design projects, communicate the vision
Skills
->- list of skills & abilities.
- for any list of duties/requirements/benefits, and
for prose. It doesn't say we cannot have other paragraphs outside headings. But we should prefer a few substantive sections over many thin ones. We could include a short intro paragraph for company overview before the headings. That would preserve it. Thus structure:
Company overview paragraph(s)
About the role
Job description paragraph (the role overview)
Responsibilities
- ...
Skills
- ...
Qualifications
- ...
Pay
Pay range and additional compensation info.
We must not include headings for Requirements (we have Qualifications). Could also include Requirements as synonyms but we have Qualifications. We must not repeat job title as heading. Now extract specifics. Company Overview paragraph(s): The text starts: "Company Overview Check out this video and find out why our team loves to work here! Join Us! CDM Smith – where amazing career journeys unfold. Imagine a place committed to offering an unmatched employee experience. Where you work on projects that are meaningful to you. Where you play an active part in shaping your career journey. Where your co-workers are invested in you and your success. Where you are encouraged and supported to do your very best and given the tools and resources to do so. Where it’s a priority that the company takes good care of you and your family. Our employees are the heart of our company. As an employer of choice, our goal is to provide a challenging, progressive and inclusive work environment which fosters personal leadership, career growth and development for every employee. We value passionate individuals who challenge the norm, deliver world-class solutions and bring diverse perspectives. Join our team, and together we will make a difference and change the world." We need to keep all that. Remove "Check out this video and find out why our team loves to work here! Join Us!" maybe that's promotional but still part of overview. It's substantive? It's a call to action; but we can keep it. It's not boilerplate. We'll keep. Now About the role: The job description paragraph after "Job Description". It says: "Join CDM Smith’s New England Transportation team as a Task Leader for highway design projects in the New England region. This position can be based in either our Boston, MA, East Hartford, CT, or Manchester, NH offices. You’ll play a pivotal role in advancing technical excellence, mentoring junior staff, and delivering innovative solutions for complex transportation challenges." That's the overview. We'll put that as. Now Responsibilities: list under "Key Responsibilities". Items: - Project Leadership: Coordinate the technical advancement of highway design projects, communicate the vision for final deliverables, and ensure technical accuracy throughout the project lifecycle. - Oversight & Management: Provide day-to-day direct oversight of transportation planning and design projects, ensuring milestones and quality standards are met. - Mentorship: Supervise, review, and mentor junior engineers. Provide technical guidance, training, and support for professional growth within the discipline and firm. - Design Development: Develop project design criteria, alignments, construction plans, specifications, and cost estimates. - Collaboration: Work closely with Project Technical Leaders and Project Managers to deliver high-complexity projects tailored to unique client requirements. - Compliance: Review draft designs for compliance with federal, state, and local regulations. Sign and seal engineering designs as required. - Site Studies: Perform site reviews and studies to ensure designs align with location specifications; update design requirements as needed. - Proposal Support: Collaborate with sales staff to create proposals in response to client RFPs. Review draft proposals for adherence to firm, industry, and regulatory standards. We'll make each as
- . Now Skills & Abilities: list: - Expert Knowledge of computer assisted design and drafting (CADD) 3D and 4D software and practices. - Expert Knowledge of engineer principles of design. - Expert Knowledge of Microsoft business software (excel, word, etc.). - Excellent verbal and written communications skills. - Strong knowledge of federal, state and local regulations. - Basic knowledge of design standards (AASHTO, NACTO, etc.). We'll make
- . Now Qualifications: list: - Bachelor's degree in Civil, Transportation, or Structural Engineering or related discipline. - Certification as an Engineer in Training (EIT) or passing the Fundamentals of Engineering (FE) exam in states where an EIT is not obtainable (within 18 months of hire or promotion or transfer). - 5 years of related experience. - Domestic and/or international travel may be required. The frequency of travel is contingent on specific duties, responsibilities, and the essential functions of the position, which may vary depending on workload and project demands. - Equivalent additional directly related experience will be considered in lieu of a degree. - Amount Of Travel Required 10% or less. - Visa Sponsorship Available No-We will not support sponsorship in the United States, i.e. H-1B or TN Visas for this position. We need to preserve all. We'll make each as
- . Note: The travel sentence and amount of travel required could be combined but we keep separate.
Now Pay: we have:
"Additional Pay Range Information CDM Smith is committed to fair and equitable compensation practices. This pay range is a good faith estimate representative of all experience levels for the geographic location assigned to the position. In addition to geographic location, a candidate’s salary is determined by several other factors including, but not limited to, the role, function and associated responsibilities, relevant work experience, skills, required certifications, and education/training.
Additional Compensation All bonuses at CDM Smith are discretionary and may or may not apply to this position.
Pay Range Max USD $175,365.00 Pay Range Min USD $100,194.00"
We'll combine into a paragraph.
We should not include "Additional Pay Range Information" as heading; just paragraph.
Now ensure we removed boilerplate: EEO Statement, Background Check and Drug Testing Information, Massachusetts Applicants, Agency Disclaimer, etc.
Also remove "Check out this video and find out why our team loves to work here! Join Us!"? It's not boilerplate but it's a call to action; we can keep.
Now produce HTML.
We need to ensure proper nesting:
for prose,
- for lists.
We'll output:
Company Overview ...
About the role
Join CDM Smith’s New England Transportation team as a Task Leader for highway design projects in the New England region. This position can be based in either our Boston, MA, East Hartford, CT, or Manchester, NH offices. You’ll play a pivotal role in advancing technical excellence, mentoring junior staff, and delivering innovative solutions for complex transportation challenges.
Responsibilities
- Project Leadership: Coordinate the technical advancement of highway design projects, communicate the vision
- for lists.
We'll output:
Qualifications
->- list of qualifications (degree, certification, experience, travel, equivalent experience, visa sponsorship, etc.)
Pay
->with pay range and additional compensation info. We should not include Benefits or Schedule as no specific content. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, background check, legal, etc. Remove those. We need to ensure we keep all substantive details from the posting: company overview? Actually we might not need to include company overview as a separate section because we have About the role covering job description. The company overview paragraph is about the company, not the role. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive. But we don't have a heading for "Company Overview". Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could treat company overview as part of About the role? But About the role is supposed to be about the role, not company. However we could still include company overview as a paragraph under About the role? Might be mixing. But we need to preserve it; we could include it as a paragraph before the About the role heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid having extra paragraphs not under headings. It says use