Civil Designer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job description and decide which sections to include.
Given the content:
- Job Title: Civil Designer (not to be used as heading)
- Job Description: paragraph about role.
- Responsibilities: list of bullet points (Prepare civil engineering designs..., Manage general site planning..., Design roadway projects..., Create residential..., Develop storm water..., Design water and sewer..., Prepare sediment...). These are duties.
- Essential Skills: list (Bachelor's degree..., Professional Engineer license..., 2-4 years..., Proficiency in AutoCAD Civil 3D..., Strong computer literacy..., Excellent verbal...). These are qualifications/skills.
- Additional Skills & Qualifications: list (Engineering-in-Training (EIT) certification preferred, Experience with Microstation v8 and Power In-Roads is a plus, Ability to manage multiple projects..., Strong organizational skills..., Ability to work independently and collaboratively...). Could be considered Skills or Qualifications.
- Work Environment: paragraph about team composition, office environment, flexible remote schedule (2 days remote per week), 6% 401k match, end-of-year bonus, recognized as Best Places to Work.
- Job Type & Location: Contract to Hire position based out of MILLERSVILLE, MD.
- Pay And Benefits: pay range $26.44 - $45.67/hr, benefits list (Medical, dental & vision, Critical Illness, Accident, and Hospital, 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available, Life Insurance (Voluntary Life & AD&D for the employee and dependents), Short and long-term disability, Health Spending Account (HSA), Transportation benefits, Employee Assistance Program, Time Off/Leave (PTO, Vacation or Sick Leave)). Also note eligibility etc.
- Workplace Type: hybrid position in MILLERSVILLE,MD.
- Application Deadline: anticipated to close on Oct 2, 2026.
- About Actalent: company description (boilerplate? Might be considered "About the company" but not required; we can include as "About the role"? Actually "About the role" is a heading we can use for the job description paragraph. The "About Actalent" is company info; could be considered boilerplate but maybe we keep as "About the company"? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" is not exactly boilerplate but could be considered company description; we might keep it as a short paragraph under a heading like "About the Company" but the allowed headings list does not include "About the Company". The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings.
We need to decide which sections to include based on actual content.
- About the role: we have a paragraph: "We are seeking a skilled Civil Designer to prepare civil engineering designs for permit and construction. The role involves general site planning, including civil engineering land development, roadway design projects, residential and commercial site design, storm water management design, storm drain design, water and sewer design, and sediment and erosion control plans." That's substantive.
- Responsibilities: we have list of duties.
- Requirements / Qualifications / Skills: we have essential skills and additional skills. Could combine into Requirements (education, licensure, experience) and Skills (technical, soft). But we must not create thin sections; prefer a few substantive sections. We could have one section "Requirements" that includes education, licensure, experience, technical proficiency, etc. Or we could have "Skills" for technical and soft skills. The instruction says we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements: could include Bachelor's degree, PE license or ability to become licensed, 2-4 years experience.
- Qualifications: maybe include Engineering-in-Training certification preferred, experience with Microstation v8 and Power In-Roads plus.
- Skills: could include proficiency in AutoCAD Civil 3D, computer literacy, communication skills, ability to manage multiple projects, organizational skills, ability to work independently/collaboratively.
But we might combine Requirements and Qualifications into one section to avoid thin sections. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements/Skills (combined), Benefits, Pay, Schedule (if we have schedule info). We have schedule info: flexible remote schedule, allowing 2 days of remote work per week. That's schedule info. Also Workplace Type: hybrid position. So we could include a Schedule section.
We have Pay And Benefits: pay range and benefits list. So we need Pay and Benefits sections? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay range and benefits, so we can include both Pay and Benefits sections. However we could combine Pay and Benefits into one section? The headings list includes both Pay and Benefits separate. We could keep them separate if we have substantive content for each. Pay: we have pay range. Benefits: we have list of benefits. Both are substantive.
Schedule: we have remote schedule info (2 days remote per week) and hybrid workplace. That's schedule.
Thus we could have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's many sections but each is substantive. However we might combine Requirements and Skills into one to reduce number. But the instruction says prefer a few substantive sections over many thin ones. Having 7 sections might be many but each is substantive. Could we reduce to About the role, Responsibilities, Requirements (including education, licensure, experience, technical skills, soft skills), Benefits, Pay, Schedule? That's 6 sections. Still many.
Maybe we can combine Benefits and Pay into a "Compensation and Benefits" section but not allowed headings. The allowed headings are specific; we must use those headings if we include them. We could choose to include only Pay and Benefits if we have both, but we could also omit Schedule if we consider schedule info minor? But schedule info is substantive: flexible remote schedule, 2 days remote per week, hybrid. So we should include Schedule.
Thus we will include: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler placeholder text. All have content.
Now we need to format:
- Use
for section headings.
- 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 remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to strip:
- Application Deadline? That's not boilerplate; it's substantive info about when position closes. Should we include? It's not in the allowed headings list. Could we include it as a short paragraph under About the role or maybe under a separate heading? Not allowed. Could we fold it into a short
under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe under About the role or at end. But we need to preserve ALL substantive information; does application deadline count as substantive? It's not about the role duties but it's still info. The instruction says fold minor metadata into a short
or drop it. So we can include it as a short paragraph somewhere, maybe after About the role.
- About Actalent: that's company description; could be considered boilerplate? It's not exactly legal/EEO but it's generic company info. Might be considered boilerplate; we could drop it. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not explicitly listed, but it's kind of boilerplate. Safer to drop it.
- The sections about equal opportunity employer, accommodation, San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of AI: these are legal/EEO boilerplate; must remove.
- Duplicated lines: we need to avoid duplication.
Now we need to extract the substantive content.
Let's list the substantive content:
**About the role paragraph**: "We are seeking a skilled Civil Designer to prepare civil engineering designs for permit and construction. The role involves general site planning, including civil engineering land development, roadway design projects, residential and commercial site design, storm water management design, storm drain design, water and sewer design, and sediment and erosion control plans."
**Responsibilities list**:
- Prepare civil engineering designs for permit and construction.
- Manage general site planning for civil engineering land development projects.
- Design roadway projects in accordance with MD State Highway Administration standards.
- Create residential and commercial site designs.
- Develop storm water management and storm drain designs.
- Design water and sewer systems.
- Prepare sediment and erosion control plans.
**Requirements (education, licensure, experience)**:
- Bachelor's degree in Civil Engineering or Environmental Engineering.
- Professional Engineer (PE) license or ability to become licensed within one year.
- 2-4 years of relevant land development engineering experience.
**Skills** (technical and soft):
- Proficiency in AutoCAD Civil 3D with at least 1-3 years of experience.
- Strong computer literacy including Microsoft Office Suite.
- Excellent verbal, written, and interpersonal skills.
- Engineering-in-Training (EIT) certification preferred.
- Experience with Microstation v8 and Power In-Roads is a plus.
- Ability to manage multiple projects and deliverables simultaneously.
- Strong organizational skills and a sense of urgency to meet client deadlines.
- Ability to work independently and collaboratively within a team.
**Work Environment / Schedule**:
- The design team is comprised of 2 Professional Engineers, 1 Environmental Engineer, and 1 CAD Technician.
- The company employs over 150 people, with 12 individuals working in the office and the remainder as construction managers and inspectors.
- Design work is performed in an office environment with no fieldwork required.
- The company offers a flexible remote schedule, allowing 2 days of remote work per week.
- They offer a 6% 401k match and an end-of-year bonus based on revenue.
- They were recognized as one of the 'Best Places to Work' by The Washington Post in 2019.
- Job Type & Location: This is a Contract to Hire position based out of MILLERSVILLE, MD.
- Workplace Type: This
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job description and decide which sections to include. Given the content: - Job Title: Civil Designer (not to be used as heading) - Job Description: paragraph about role. - Responsibilities: list of bullet points (Prepare civil engineering designs..., Manage general site planning..., Design roadway projects..., Create residential..., Develop storm water..., Design water and sewer..., Prepare sediment...). These are duties. - Essential Skills: list (Bachelor's degree..., Professional Engineer license..., 2-4 years..., Proficiency in AutoCAD Civil 3D..., Strong computer literacy..., Excellent verbal...). These are qualifications/skills. - Additional Skills & Qualifications: list (Engineering-in-Training (EIT) certification preferred, Experience with Microstation v8 and Power In-Roads is a plus, Ability to manage multiple projects..., Strong organizational skills..., Ability to work independently and collaboratively...). Could be considered Skills or Qualifications. - Work Environment: paragraph about team composition, office environment, flexible remote schedule (2 days remote per week), 6% 401k match, end-of-year bonus, recognized as Best Places to Work. - Job Type & Location: Contract to Hire position based out of MILLERSVILLE, MD. - Pay And Benefits: pay range $26.44 - $45.67/hr, benefits list (Medical, dental & vision, Critical Illness, Accident, and Hospital, 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available, Life Insurance (Voluntary Life & AD&D for the employee and dependents), Short and long-term disability, Health Spending Account (HSA), Transportation benefits, Employee Assistance Program, Time Off/Leave (PTO, Vacation or Sick Leave)). Also note eligibility etc. - Workplace Type: hybrid position in MILLERSVILLE,MD. - Application Deadline: anticipated to close on Oct 2, 2026. - About Actalent: company description (boilerplate? Might be considered "About the company" but not required; we can include as "About the role"? Actually "About the role" is a heading we can use for the job description paragraph. The "About Actalent" is company info; could be considered boilerplate but maybe we keep as "About the company"? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" is not exactly boilerplate but could be considered company description; we might keep it as a short paragraph under a heading like "About the Company" but the allowed headings list does not include "About the Company". The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. We need to decide which sections to include based on actual content. - About the role: we have a paragraph: "We are seeking a skilled Civil Designer to prepare civil engineering designs for permit and construction. The role involves general site planning, including civil engineering land development, roadway design projects, residential and commercial site design, storm water management design, storm drain design, water and sewer design, and sediment and erosion control plans." That's substantive. - Responsibilities: we have list of duties. - Requirements / Qualifications / Skills: we have essential skills and additional skills. Could combine into Requirements (education, licensure, experience) and Skills (technical, soft). But we must not create thin sections; prefer a few substantive sections. We could have one section "Requirements" that includes education, licensure, experience, technical proficiency, etc. Or we could have "Skills" for technical and soft skills. The instruction says we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: could include Bachelor's degree, PE license or ability to become licensed, 2-4 years experience. - Qualifications: maybe include Engineering-in-Training certification preferred, experience with Microstation v8 and Power In-Roads plus. - Skills: could include proficiency in AutoCAD Civil 3D, computer literacy, communication skills, ability to manage multiple projects, organizational skills, ability to work independently/collaboratively. But we might combine Requirements and Qualifications into one section to avoid thin sections. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements/Skills (combined), Benefits, Pay, Schedule (if we have schedule info). We have schedule info: flexible remote schedule, allowing 2 days of remote work per week. That's schedule info. Also Workplace Type: hybrid position. So we could include a Schedule section. We have Pay And Benefits: pay range and benefits list. So we need Pay and Benefits sections? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay range and benefits, so we can include both Pay and Benefits sections. However we could combine Pay and Benefits into one section? The headings list includes both Pay and Benefits separate. We could keep them separate if we have substantive content for each. Pay: we have pay range. Benefits: we have list of benefits. Both are substantive. Schedule: we have remote schedule info (2 days remote per week) and hybrid workplace. That's schedule. Thus we could have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's many sections but each is substantive. However we might combine Requirements and Skills into one to reduce number. But the instruction says prefer a few substantive sections over many thin ones. Having 7 sections might be many but each is substantive. Could we reduce to About the role, Responsibilities, Requirements (including education, licensure, experience, technical skills, soft skills), Benefits, Pay, Schedule? That's 6 sections. Still many. Maybe we can combine Benefits and Pay into a "Compensation and Benefits" section but not allowed headings. The allowed headings are specific; we must use those headings if we include them. We could choose to include only Pay and Benefits if we have both, but we could also omit Schedule if we consider schedule info minor? But schedule info is substantive: flexible remote schedule, 2 days remote per week, hybrid. So we should include Schedule. Thus we will include: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We need to ensure we don't create sections with filler placeholder text. All have content. Now we need to format: - Use
for section headings.
- 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 remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to strip:
- Application Deadline? That's not boilerplate; it's substantive info about when position closes. Should we include? It's not in the allowed headings list. Could we include it as a short paragraph under About the role or maybe under a separate heading? Not allowed. Could we fold it into a short
under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe under About the role or at end. But we need to preserve ALL substantive information; does application deadline count as substantive? It's not about the role duties but it's still info. The instruction says fold minor metadata into a short
or drop it. So we can include it as a short paragraph somewhere, maybe after About the role.
- About Actalent: that's company description; could be considered boilerplate? It's not exactly legal/EEO but it's generic company info. Might be considered boilerplate; we could drop it. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not explicitly listed, but it's kind of boilerplate. Safer to drop it.
- The sections about equal opportunity employer, accommodation, San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of AI: these are legal/EEO boilerplate; must remove.
- Duplicated lines: we need to avoid duplication.
Now we need to extract the substantive content.
Let's list the substantive content:
**About the role paragraph**: "We are seeking a skilled Civil Designer to prepare civil engineering designs for permit and construction. The role involves general site planning, including civil engineering land development, roadway design projects, residential and commercial site design, storm water management design, storm drain design, water and sewer design, and sediment and erosion control plans."
**Responsibilities list**:
- Prepare civil engineering designs for permit and construction.
- Manage general site planning for civil engineering land development projects.
- Design roadway projects in accordance with MD State Highway Administration standards.
- Create residential and commercial site designs.
- Develop storm water management and storm drain designs.
- Design water and sewer systems.
- Prepare sediment and erosion control plans.
**Requirements (education, licensure, experience)**:
- Bachelor's degree in Civil Engineering or Environmental Engineering.
- Professional Engineer (PE) license or ability to become licensed within one year.
- 2-4 years of relevant land development engineering experience.
**Skills** (technical and soft):
- Proficiency in AutoCAD Civil 3D with at least 1-3 years of experience.
- Strong computer literacy including Microsoft Office Suite.
- Excellent verbal, written, and interpersonal skills.
- Engineering-in-Training (EIT) certification preferred.
- Experience with Microstation v8 and Power In-Roads is a plus.
- Ability to manage multiple projects and deliverables simultaneously.
- Strong organizational skills and a sense of urgency to meet client deadlines.
- Ability to work independently and collaboratively within a team.
**Work Environment / Schedule**:
- The design team is comprised of 2 Professional Engineers, 1 Environmental Engineer, and 1 CAD Technician.
- The company employs over 150 people, with 12 individuals working in the office and the remainder as construction managers and inspectors.
- Design work is performed in an office environment with no fieldwork required.
- The company offers a flexible remote schedule, allowing 2 days of remote work per week.
- They offer a 6% 401k match and an end-of-year bonus based on revenue.
- They were recognized as one of the 'Best Places to Work' by The Washington Post in 2019.
- Job Type & Location: This is a Contract to Hire position based out of MILLERSVILLE, MD.
- Workplace Type: This
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip: - Application Deadline? That's not boilerplate; it's substantive info about when position closes. Should we include? It's not in the allowed headings list. Could we include it as a short paragraph under About the role or maybe under a separate heading? Not allowed. Could we fold it into a short
under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe under About the role or at end. But we need to preserve ALL substantive information; does application deadline count as substantive? It's not about the role duties but it's still info. The instruction says fold minor metadata into a short
or drop it. So we can include it as a short paragraph somewhere, maybe after About the role. - About Actalent: that's company description; could be considered boilerplate? It's not exactly legal/EEO but it's generic company info. Might be considered boilerplate; we could drop it. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not explicitly listed, but it's kind of boilerplate. Safer to drop it. - The sections about equal opportunity employer, accommodation, San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of AI: these are legal/EEO boilerplate; must remove. - Duplicated lines: we need to avoid duplication. Now we need to extract the substantive content. Let's list the substantive content: **About the role paragraph**: "We are seeking a skilled Civil Designer to prepare civil engineering designs for permit and construction. The role involves general site planning, including civil engineering land development, roadway design projects, residential and commercial site design, storm water management design, storm drain design, water and sewer design, and sediment and erosion control plans." **Responsibilities list**: - Prepare civil engineering designs for permit and construction. - Manage general site planning for civil engineering land development projects. - Design roadway projects in accordance with MD State Highway Administration standards. - Create residential and commercial site designs. - Develop storm water management and storm drain designs. - Design water and sewer systems. - Prepare sediment and erosion control plans. **Requirements (education, licensure, experience)**: - Bachelor's degree in Civil Engineering or Environmental Engineering. - Professional Engineer (PE) license or ability to become licensed within one year. - 2-4 years of relevant land development engineering experience. **Skills** (technical and soft): - Proficiency in AutoCAD Civil 3D with at least 1-3 years of experience. - Strong computer literacy including Microsoft Office Suite. - Excellent verbal, written, and interpersonal skills. - Engineering-in-Training (EIT) certification preferred. - Experience with Microstation v8 and Power In-Roads is a plus. - Ability to manage multiple projects and deliverables simultaneously. - Strong organizational skills and a sense of urgency to meet client deadlines. - Ability to work independently and collaboratively within a team. **Work Environment / Schedule**: - The design team is comprised of 2 Professional Engineers, 1 Environmental Engineer, and 1 CAD Technician. - The company employs over 150 people, with 12 individuals working in the office and the remainder as construction managers and inspectors. - Design work is performed in an office environment with no fieldwork required. - The company offers a flexible remote schedule, allowing 2 days of remote work per week. - They offer a 6% 401k match and an end-of-year bonus based on revenue. - They were recognized as one of the 'Best Places to Work' by The Washington Post in 2019. - Job Type & Location: This is a Contract to Hire position based out of MILLERSVILLE, MD. - Workplace Type: This