Senior Civil Project Engineer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes:
- Summary Of The Role (could be "About the role")
- Responsibilities (list)
- Qualifications (list)
- Benefits: there is a section "Why Professionals Choose Core States Group" with bullet points: COMPENSATION – Competitive wages and bonus programs; RETIREMENT – 401(k) match; HEALTHCARE – health benefits; VACATION – PTO; PERKS – team wellness challenges, Costco membership reimbursement, half-day Fridays; WORK-LIFE BALANCE – flexible work environment; PAID PARENTAL LEAVE – four weeks; TUITION REIMBURSEMENT – tuition reimbursement.
We need to decide which sections to output: About the role (Summary), Responsibilities, Qualifications, Benefits. Possibly also Skills? The qualifications include required skills: Bachelor's degree, P.E., 8+ years, AutoCAD, MS Office, Civil3D, AI tools usage, etc. Those could go under Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose to put qualifications under Qualifications heading, and maybe skills under Skills heading if we separate. But we must not create thin sections. Better to combine qualifications and skills into Qualifications (since they are qualifications). Or we could have Qualifications heading for education/experience, and Skills heading for technical skills. However the posting lumps them together. To avoid thin sections, we can have Qualifications heading containing both education/experience and technical skills as a list.
Benefits: we have many bullet points; we can output Benefits heading with ul.
Pay: The posting mentions "Competitive wages and bonus programs" under COMPENSATION. That is pay info. Should we create a Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation: "Competitive wages and bonus programs". That's pay info. So we could have a Pay section with that detail. However we also have benefits section that includes retirement, healthcare, vacation, perks, work-life balance, parental leave, tuition reimbursement. The compensation bullet could be part of Benefits or separate Pay. The instruction says prefer a few substantive sections over many thin ones. Could combine compensation into Benefits? But they are distinct: compensation vs benefits. However we could have Benefits heading that includes compensation as a bullet. But the heading list includes Benefits separate from Pay. Since we have both compensation and benefits details, we could make two sections: Pay and Benefits. That's okay if both have substantive content. Pay: "Competitive wages and bonus programs". That's a bit thin but still specific. Benefits: many items.
Schedule: Not mentioned. No schedule info (like full-time, hours). So we omit Schedule.
Requirements: Could be same as Qualifications. The instruction includes Requirements as possible heading. We could use Requirements heading for mandatory qualifications (education, P.E., years, software) and Qualifications heading for preferred? But the posting lumps required and preferred? It says "The following qualifications will help you succeed in this role:" then list: Bachelor’s degree required, P.E. required, 8+ years required, AutoCAD and MS Office required, Experience working within Civil3D required, Demonstrated ability and willingness to identify practical uses for company-approved AI tools..., Demonstrated ability to review AI-generated content... So all are required. So we could have Requirements heading for those. Then maybe Skills heading for soft skills? Not much. Better to just have Qualifications heading covering all.
Thus sections: About the role (Summary), Responsibilities, Requirements (or Qualifications), Benefits. Possibly also Pay.
Let's decide: Use About the role (h3) for Summary Of The Role. Responsibilities (h3) for Responsibilities list. Requirements (h3) for the qualifications list (education, experience, skills). Benefits (h3) for the benefits list (including compensation, retirement, healthcare, vacation, perks, work-life balance, parental leave, tuition reimbursement). Pay could be omitted if we include compensation in Benefits. But the instruction says never create Pay section unless posting actually states them. It does state compensation, but we could treat compensation as part of Benefits. However the heading list includes Benefits separate; but we can still put compensation under Benefits. That's okay. The instruction: "Prefer a few substantive sections over many thin ones." So combining compensation into Benefits reduces number of sections. So we will have About the role, Responsibilities, Requirements, Benefits.
Now we need to output HTML fragment only, no /. Use for each section heading. 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 etc.
We need to include the summary paragraph: "The Senior Civil Project Engineer is responsible for the supervision of a design team and management of civil engineering projects from conception to completion. You will apply your experience in: site layout, grading, utility design and profiles, erosion and sediment control, SWPPP preparation, and stormwater management. As part of a multi-disciplined firm, you will be coordinating with Architects, MEP Engineers, Structural Engineers, and Construction Project Managers. You will be responsible for the production of civil engineering construction documents while adhering to client requirements, code requirements and site adjustments."
That's prose; put in
.
Responsibilities: list each bullet. Need to capture all responsibilities lines. Let's extract them:
- Manage a team of Civil Engineering Designers and Civil Project Engineers.
- Engage in client interaction throughout projects.
- Coordinate with sub-consultants.
- Assist in preparing and negotiating contracts and change orders with clients and sub-contractors.
- Design full site plans or with little or no direction.
- Conduct site visits and generate reports and recommendations based on findings.
- Prepare design calculations and reports.
- Establish and maintain project, phase, and task level budgets and schedules.
- Prepare responses to construction RFI’s and submittals.
- Assist in coordinating the work of a multi-disciplined team throughout the design development and contract document phases of a project.
- Demonstrate practical and functional knowledge of municipal codes.
- Coordinate and meet with authorities having jurisdiction through all phases of projects.
- Organize and maintain project files.
- Maintain timesheets daily.
- Demonstrate an understanding of liability issues related to design.
- Demonstrate an understanding of constructability and complex design.
- Develop and mentor staff.
- Other duties as assigned.
We'll put each as
- .
Requirements: list qualifications:
- Bachelor’s degree in Civil Engineering required
- P.E. in Civil Engineering required
- 8+ years of site/civil production, preferably with commercial projects such as retail, restaurants, convenience, and/or fueling
- AutoCAD and MS Office required
- Experience working within Civil3D required
- Demonstrated ability and willingness to identify practical uses for company-approved AI tools to improve team processes, support better decisions, and increase efficiency.
- Demonstrated ability to review AI-generated content for accuracy, protect confidential information, and remain responsible for the final work product.
We could also include "Work Location" maybe as a paragraph under Requirements? But it's location info; not a requirement. Could be separate section? Not in headings list. Could be placed as a
after Requirements? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Work location is metadata; we could include as a
after Requirements, maybe under a heading? Not needed. Could include as a
under Requirements? But better to add a
after Requirements with the work location list. However the instruction says preserve ALL substantive information; we should not drop work location. So we need to include it somewhere. Since there is no specific heading for location, we can add a
after the Requirements section (or before Benefits) containing the work location list. That's acceptable.
Similarly, Company Overview and A Note to Candidates are substantive; we should preserve them. They are not under headings list but we can include as
paragraphs after Benefits maybe. The instruction: "Prefer a few substantive sections over many thin ones." But we need to preserve all substantive info. We could add a
for Company Overview and a
for A Note to Candidates. That's fine.
We must not include boilerplate like cookie/navigation/legal/EEO etc. The posting includes "A Note to Candidates" which is not boilerplate; it's substantive encouraging diverse applicants. Keep it.
Now format.
We'll output:
About the role
...summary...
Responsibilities
- ...
...
Requirements
- ...
...
Work Location: Kent, WA; Bellevue, WA; Puyallup, WA; Richland, WA; Scottsdale, AZ; Roseville, CA; Long Beach, CA; Ontario, CA; Frisco, TX; Bentonville, AR; Naperville, IL; Tampa, FL; Burlington, MA; Minneapolis, MN; Charleston, NC; Somerville, NJ; Philadelphia, PA; or King of Prussia, PA.
Benefits
- Competitive wages and bonus programs
- Great 401(k) match to help you invest in your future and grow your retirement savings with confidence.
- Excellent health benefits, life insurance options, and supplemental benefit options, giving you the flexibility to choose the coverage that best fits your needs and lifestyle.
- Generous PTO time to help you recharge, relax, and maintain a healthy work-life balance.
- Team wellness challenges, Costco membership reimbursement, half-day Fridays during summer months + much more!
- A flexible work environment that supports a healthy work-life balance, whether you’re in the office, working remotely, or somewhere in between.
- Four weeks of fully paid parental leave to give you time to bond with your new addition and support your growing family.
- Tuition reimbursement to support your learning journey.
Company Overview: Core States Group is an industry-leading architecture, engineering, and construction (A/E/C) firm trusted by many of the world’s most notable brands. With 26 offices across the United States and Canada, the firm delivers speed to market, cost certainty, and compelling design for national multisite programs and projects. Established in 1999, Core States Group drives innovation and improves everyday life for countless people across several markets, including Convenience, Distributed Generation, Financial, Grocery, Housing, Industrial, Restaurants, Retail, Semiconductor, Zero-Emission Vehicle (ZEV) Infrastructure, and more.
A Note to Candidates: Please do not be concerned if you do not meet every requirement. At Core States we are dedicated to building a diverse and inclusive workplace, so if you are excited about this role but your experience does not align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles.
Check for any repeated lines: we have not duplicated.
Check for any boilerplate removed: we removed "Why Professionals Choose Core States Group Here's What You Can Expect" heading; we turned its content into benefits list. We removed "Summary Of The Role" heading (we used About the role). We removed "Work Location" heading (we made a paragraph). We removed "Company Overview" heading (we made a paragraph). We removed "A Note to Candidates" heading (we made a paragraph). Good.
Check that we didn't include any headings with empty content. All have content.
Check that we didn
- 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 etc. We need to include the summary paragraph: "The Senior Civil Project Engineer is responsible for the supervision of a design team and management of civil engineering projects from conception to completion. You will apply your experience in: site layout, grading, utility design and profiles, erosion and sediment control, SWPPP preparation, and stormwater management. As part of a multi-disciplined firm, you will be coordinating with Architects, MEP Engineers, Structural Engineers, and Construction Project Managers. You will be responsible for the production of civil engineering construction documents while adhering to client requirements, code requirements and site adjustments." That's prose; put in
. Responsibilities: list each bullet. Need to capture all responsibilities lines. Let's extract them: - Manage a team of Civil Engineering Designers and Civil Project Engineers. - Engage in client interaction throughout projects. - Coordinate with sub-consultants. - Assist in preparing and negotiating contracts and change orders with clients and sub-contractors. - Design full site plans or with little or no direction. - Conduct site visits and generate reports and recommendations based on findings. - Prepare design calculations and reports. - Establish and maintain project, phase, and task level budgets and schedules. - Prepare responses to construction RFI’s and submittals. - Assist in coordinating the work of a multi-disciplined team throughout the design development and contract document phases of a project. - Demonstrate practical and functional knowledge of municipal codes. - Coordinate and meet with authorities having jurisdiction through all phases of projects. - Organize and maintain project files. - Maintain timesheets daily. - Demonstrate an understanding of liability issues related to design. - Demonstrate an understanding of constructability and complex design. - Develop and mentor staff. - Other duties as assigned. We'll put each as
- .
Requirements: list qualifications:
- Bachelor’s degree in Civil Engineering required
- P.E. in Civil Engineering required
- 8+ years of site/civil production, preferably with commercial projects such as retail, restaurants, convenience, and/or fueling
- AutoCAD and MS Office required
- Experience working within Civil3D required
- Demonstrated ability and willingness to identify practical uses for company-approved AI tools to improve team processes, support better decisions, and increase efficiency.
- Demonstrated ability to review AI-generated content for accuracy, protect confidential information, and remain responsible for the final work product.
We could also include "Work Location" maybe as a paragraph under Requirements? But it's location info; not a requirement. Could be separate section? Not in headings list. Could be placed as a
after Requirements? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Work location is metadata; we could include as a
after Requirements, maybe under a heading? Not needed. Could include as a
under Requirements? But better to add a
after Requirements with the work location list. However the instruction says preserve ALL substantive information; we should not drop work location. So we need to include it somewhere. Since there is no specific heading for location, we can add a
after the Requirements section (or before Benefits) containing the work location list. That's acceptable. Similarly, Company Overview and A Note to Candidates are substantive; we should preserve them. They are not under headings list but we can include as
paragraphs after Benefits maybe. The instruction: "Prefer a few substantive sections over many thin ones." But we need to preserve all substantive info. We could add a
for Company Overview and a
for A Note to Candidates. That's fine. We must not include boilerplate like cookie/navigation/legal/EEO etc. The posting includes "A Note to Candidates" which is not boilerplate; it's substantive encouraging diverse applicants. Keep it. Now format. We'll output:
About the role
...summary...
Responsibilities
- ... ...
Requirements
- ... ...
Work Location: Kent, WA; Bellevue, WA; Puyallup, WA; Richland, WA; Scottsdale, AZ; Roseville, CA; Long Beach, CA; Ontario, CA; Frisco, TX; Bentonville, AR; Naperville, IL; Tampa, FL; Burlington, MA; Minneapolis, MN; Charleston, NC; Somerville, NJ; Philadelphia, PA; or King of Prussia, PA.
Benefits
- Competitive wages and bonus programs
- Great 401(k) match to help you invest in your future and grow your retirement savings with confidence.
- Excellent health benefits, life insurance options, and supplemental benefit options, giving you the flexibility to choose the coverage that best fits your needs and lifestyle.
- Generous PTO time to help you recharge, relax, and maintain a healthy work-life balance.
- Team wellness challenges, Costco membership reimbursement, half-day Fridays during summer months + much more!
- A flexible work environment that supports a healthy work-life balance, whether you’re in the office, working remotely, or somewhere in between.
- Four weeks of fully paid parental leave to give you time to bond with your new addition and support your growing family.
- Tuition reimbursement to support your learning journey.
Company Overview: Core States Group is an industry-leading architecture, engineering, and construction (A/E/C) firm trusted by many of the world’s most notable brands. With 26 offices across the United States and Canada, the firm delivers speed to market, cost certainty, and compelling design for national multisite programs and projects. Established in 1999, Core States Group drives innovation and improves everyday life for countless people across several markets, including Convenience, Distributed Generation, Financial, Grocery, Housing, Industrial, Restaurants, Retail, Semiconductor, Zero-Emission Vehicle (ZEV) Infrastructure, and more.
A Note to Candidates: Please do not be concerned if you do not meet every requirement. At Core States we are dedicated to building a diverse and inclusive workplace, so if you are excited about this role but your experience does not align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles.
Check for any repeated lines: we have not duplicated. Check for any boilerplate removed: we removed "Why Professionals Choose Core States Group Here's What You Can Expect" heading; we turned its content into benefits list. We removed "Summary Of The Role" heading (we used About the role). We removed "Work Location" heading (we made a paragraph). We removed "Company Overview" heading (we made a paragraph). We removed "A Note to Candidates" heading (we made a paragraph). Good. Check that we didn't include any headings with empty content. All have content. Check that we didn