Civil Project Engineer - Entry Level
AHBL Inc. · Tacoma, WA · 2 wk ago
On-siteEngineering$32.93–$41.35/hrFull-time
We need to output HTML fragment only, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam warning, application instructions, navigation, cookie, legal. Also remove "WHY AHBL?" maybe not a standard heading; could be considered "About the role" or maybe "Benefits"? Actually "WHY AHBL?" is about culture; could be part of "About the role" or maybe we can include as a separate section? The instruction says use headings for those specific section names; we should not create other headings. So we should incorporate that content into appropriate existing sections, maybe "About the role" or "Benefits". But we must not create headings not listed. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to see if posting has content for each.
Let's parse the posting:
- Intro: "Step into a role where your talent drives real-world impact. At AHBL, we’re looking for professionals who thrive in a collaborative environment and see every project as an adventure. If you enjoy working closely with clients and cross-functional teams to bring projects from concept to construction, we want to meet you! At AHBL, we don’t just shape cities—we help to build vibrant communities where the work is rewarding. Our teams enjoy coming to work and flourish through innovation and creativity. Since 1969, our multi-discipline firm has delivered innovative solutions in engineering, planning, landscape architecture, and land surveying. Our team is passionate about creative problem-solving, and we take pride in the meaningful, diverse projects we deliver."
That's about the company and role; could go under "About the role".
- "What You Will Do In this role you will work on a wide range of projects, including public K-12 schools, higher education, municipal buildings, stormwater, retrofits/parks, Department of Defense, and healthcare facilities. You will collaborate with clients and other team members in preparing civil engineering designs and calculations for site developments, local roads, stormwater, and utility improvements, including grading, drainage, sanitary sewer, water, and other related work."
That's responsibilities.
- "What We Are Looking For A high level of organization and communication to help us drive projects to completion. Diligent attention to detail because the details are what make a project successful. A desire to make a positive impact in the communities we serve. Motivation to meet our clients’ deadlines and rise to the occasion when the pressure is on."
That's maybe "Requirements" or "Qualifications". Then "Here's our list of must-haves: Bachelor of Science in Civil EngineeringEITExperience with AutoCADStrong written and verbal communication skillsSelf-motivated with a positive attitude and a willingness to learn". That's qualifications/requirements.
- "Anything on this list would be an asset, but is not required: Familiarity with stormwater modeling using WWHM, MGS Flood and other softwareFamiliarity with Civil 3DExperience preparing storm drainage reports". That's "Skills" maybe.
- "COMPENSATION AND BENEFITS The salary range for this position is dependent on which of our internal company levels the selected candidate aligns with. This role could be filled by candidates at either a Project Engineer I or Project Engineer II level, and the hiring team will determine which level is most appropriate for each candidate based on their relevant background and experience. Actual pay will be based on experience and other job-related factors permitted by lawProject Engineer I - $32.93 - $41.35 per hourAnnual discretionary performance-based bonus100% paid employee medical, dental, vision, prescription coverage, life insurance and long-term disability protection. Subsidized dependent coverageOption of PPO health plan or HDHP with Health Savings Account (HSA) with company contributionOptional Flexible Spending Account (FSA)Paid Time Off (PTO) Benefits. PTO is accrued at 16.5 days (132 hours) annually for new hires8 company-paid holidays each calendar yearDiscretionary company-matched 401(k) planEmployee Assistance Program (EAP)Additional voluntary benefits include voluntary hospital indemnity coverage, voluntary accident insurance, and voluntary critical illness insurance"
That's Pay and Benefits.
- "WHY AHBL? We offer a fun and friendly atmosphere with team outings and ensure that the work is always enjoyableWe encourage out of the box thinking and innovative approaches to every projectOur teams celebrate successes and support each other through challenges. Our projects are primarily in the Pacific Northwest, so our work shapes the communities where we live and workWe offer continuous learning and professional development to advance your career". This could be part of "About the role" or maybe "Benefits"? It's more about culture; we could incorporate into "About the role". Since we cannot create a new heading, we will add to "About the role".
- Then EEO boilerplate etc to remove.
Thus we have content for:
About the role: includes intro + WHY AHBL? content.
Responsibilities: "What You Will Do" paragraph.
Requirements: maybe combine "What We Are Looking For" and must-haves? Actually "What We Are Looking For" is more like soft skills; must-haves are qualifications. We could split: Requirements = must-haves (Bachelor of Science in Civil Engineering, EIT, Experience with AutoCAD, Strong written and verbal communication skills, Self-motivated with a positive attitude and a willingness to learn). Qualifications = maybe the "What We Are Looking For" (organization, communication, attention to detail, desire to make impact, motivation to meet deadlines). But the instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what goes where.
We have:
- Must-haves (hard qualifications): Bachelor of Science in Civil Engineering, EIT, Experience with AutoCAD, Strong written and verbal communication skills, Self-motivated with a positive attitude and a willingness to learn.
- Nice-to-haves (assets): Familiarity with stormwater modeling using WWHM, MGS Flood and other software, Familiarity with Civil 3D, Experience preparing storm drainage reports.
- Soft skills/attributes: high level of organization and communication, diligent attention to detail, desire to make positive impact, motivation to meet deadlines and rise to occasion.
We could map:
Requirements: the must-haves (hard qualifications). Qualifications: the nice-to-haves? Or maybe Qualifications = the must-haves and Requirements = the soft skills? Usually Requirements are the must-haves, Qualifications are nice-to-haves, Skills are specific technical skills. But we have both must-haves and nice-to-haves. Let's assign:
- Requirements: Bachelor of Science in Civil Engineering, EIT, Experience with AutoCAD, Strong written and verbal communication skills, Self-motivated with a positive attitude and a willingness to learn.
- Qualifications: Familiarity with stormwater modeling using WWHM, MGS Flood and other software, Familiarity with Civil 3D, Experience preparing storm drainage reports.
- Skills: high level of organization and communication, diligent attention to detail, desire to make a positive impact, motivation to meet clients’ deadlines and rise to the occasion when pressure is on.
But "Skills" might be better for technical skills; but we can still use it for these attributes. The instruction says use sections only when posting has real specific content. All three have content.
Now Benefits and Pay: we have both. The posting includes compensation and benefits combined. We need separate sections for Pay and Benefits if they have specific content. Pay: we have salary range: Project Engineer I - $32.93 - $41.35 per hour. Also mention that actual pay based on experience, discretionary bonus. That's pay info.
Benefits: list of medical, dental, vision, prescription, life insurance, long-term disability, subsidized dependent coverage, PPO or HDHP with HSA, FSA, PTO accrual, holidays, 401(k) match, EAP, voluntary benefits.
Schedule: Not mentioned. So we should NOT include Schedule section because no specific content. Similarly, if any section lacks content, we omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We must not include Schedule.
Now format: Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam warning, application instructions, navigation, cookie, legal. Also remove "WHY AHBL?" maybe not a standard heading; could be considered "About the role" or maybe "Benefits"? Actually "WHY AHBL?" is about culture; could be part of "About the role" or maybe we can include as a separate section? The instruction says use headings for those specific section names; we should not create other headings. So we should incorporate that content into appropriate existing sections, maybe "About the role" or "Benefits". But we must not create headings not listed. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to see if posting has content for each.
Let's parse the posting:
- Intro: "Step into a role where your talent drives real-world impact. At AHBL, we’re looking for professionals who thrive in a collaborative environment and see every project as an adventure. If you enjoy working closely with clients and cross-functional teams to bring projects from concept to construction, we want to meet you! At AHBL, we don’t just shape cities—we help to build vibrant communities where the work is rewarding. Our teams enjoy coming to work and flourish through innovation and creativity. Since 1969, our multi-discipline firm has delivered innovative solutions in engineering, planning, landscape architecture, and land surveying. Our team is passionate about creative problem-solving, and we take pride in the meaningful, diverse projects we deliver."
That's about the company and role; could go under "About the role".
- "What You Will Do In this role you will work on a wide range of projects, including public K-12 schools, higher education, municipal buildings, stormwater, retrofits/parks, Department of Defense, and healthcare facilities. You will collaborate with clients and other team members in preparing civil engineering designs and calculations for site developments, local roads, stormwater, and utility improvements, including grading, drainage, sanitary sewer, water, and other related work."
That's responsibilities.
- "What We Are Looking For A high level of organization and communication to help us drive projects to completion. Diligent attention to detail because the details are what make a project successful. A desire to make a positive impact in the communities we serve. Motivation to meet our clients’ deadlines and rise to the occasion when the pressure is on."
That's maybe "Requirements" or "Qualifications". Then "Here's our list of must-haves: Bachelor of Science in Civil EngineeringEITExperience with AutoCADStrong written and verbal communication skillsSelf-motivated with a positive attitude and a willingness to learn". That's qualifications/requirements.
- "Anything on this list would be an asset, but is not required: Familiarity with stormwater modeling using WWHM, MGS Flood and other softwareFamiliarity with Civil 3DExperience preparing storm drainage reports". That's "Skills" maybe.
- "COMPENSATION AND BENEFITS The salary range for this position is dependent on which of our internal company levels the selected candidate aligns with. This role could be filled by candidates at either a Project Engineer I or Project Engineer II level, and the hiring team will determine which level is most appropriate for each candidate based on their relevant background and experience. Actual pay will be based on experience and other job-related factors permitted by lawProject Engineer I - $32.93 - $41.35 per hourAnnual discretionary performance-based bonus100% paid employee medical, dental, vision, prescription coverage, life insurance and long-term disability protection. Subsidized dependent coverageOption of PPO health plan or HDHP with Health Savings Account (HSA) with company contributionOptional Flexible Spending Account (FSA)Paid Time Off (PTO) Benefits. PTO is accrued at 16.5 days (132 hours) annually for new hires8 company-paid holidays each calendar yearDiscretionary company-matched 401(k) planEmployee Assistance Program (EAP)Additional voluntary benefits include voluntary hospital indemnity coverage, voluntary accident insurance, and voluntary critical illness insurance"
That's Pay and Benefits.
- "WHY AHBL? We offer a fun and friendly atmosphere with team outings and ensure that the work is always enjoyableWe encourage out of the box thinking and innovative approaches to every projectOur teams celebrate successes and support each other through challenges. Our projects are primarily in the Pacific Northwest, so our work shapes the communities where we live and workWe offer continuous learning and professional development to advance your career". This could be part of "About the role" or maybe "Benefits"? It's more about culture; we could incorporate into "About the role". Since we cannot create a new heading, we will add to "About the role".
- Then EEO boilerplate etc to remove.
Thus we have content for:
About the role: includes intro + WHY AHBL? content.
Responsibilities: "What You Will Do" paragraph.
Requirements: maybe combine "What We Are Looking For" and must-haves? Actually "What We Are Looking For" is more like soft skills; must-haves are qualifications. We could split: Requirements = must-haves (Bachelor of Science in Civil Engineering, EIT, Experience with AutoCAD, Strong written and verbal communication skills, Self-motivated with a positive attitude and a willingness to learn). Qualifications = maybe the "What We Are Looking For" (organization, communication, attention to detail, desire to make impact, motivation to meet deadlines). But the instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what goes where.
We have:
- Must-haves (hard qualifications): Bachelor of Science in Civil Engineering, EIT, Experience with AutoCAD, Strong written and verbal communication skills, Self-motivated with a positive attitude and a willingness to learn.
- Nice-to-haves (assets): Familiarity with stormwater modeling using WWHM, MGS Flood and other software, Familiarity with Civil 3D, Experience preparing storm drainage reports.
- Soft skills/attributes: high level of organization and communication, diligent attention to detail, desire to make positive impact, motivation to meet deadlines and rise to occasion.
We could map:
Requirements: the must-haves (hard qualifications). Qualifications: the nice-to-haves? Or maybe Qualifications = the must-haves and Requirements = the soft skills? Usually Requirements are the must-haves, Qualifications are nice-to-haves, Skills are specific technical skills. But we have both must-haves and nice-to-haves. Let's assign:
- Requirements: Bachelor of Science in Civil Engineering, EIT, Experience with AutoCAD, Strong written and verbal communication skills, Self-motivated with a positive attitude and a willingness to learn.
- Qualifications: Familiarity with stormwater modeling using WWHM, MGS Flood and other software, Familiarity with Civil 3D, Experience preparing storm drainage reports.
- Skills: high level of organization and communication, diligent attention to detail, desire to make a positive impact, motivation to meet clients’ deadlines and rise to the occasion when pressure is on.
But "Skills" might be better for technical skills; but we can still use it for these attributes. The instruction says use sections only when posting has real specific content. All three have content.
Now Benefits and Pay: we have both. The posting includes compensation and benefits combined. We need separate sections for Pay and Benefits if they have specific content. Pay: we have salary range: Project Engineer I - $32.93 - $41.35 per hour. Also mention that actual pay based on experience, discretionary bonus. That's pay info.
Benefits: list of medical, dental, vision, prescription, life insurance, long-term disability, subsidized dependent coverage, PPO or HDHP with HSA, FSA, PTO accrual, holidays, 401(k) match, EAP, voluntary benefits.
Schedule: Not mentioned. So we should NOT include Schedule section because no specific content. Similarly, if any section lacks content, we omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We must not include Schedule.
Now format: Use for each section heading. Then content: use
for prose,
- for lists.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must not repeat job title. Not include Job ID etc.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, navigation, cookie, legal. Also remove "Powered by JazzHR va1RUXiwSh". Also remove "WHY AHBL?" heading but we incorporate its content.
Now craft HTML.
Let's extract content precisely.
About the role: combine intro paragraph and WHY AHBL? content.
Intro: "Step into a role where your talent drives real-world impact. At AHBL, we’re looking for professionals who thrive in a collaborative environment and see every project as an adventure. If you enjoy working closely with clients and cross-functional teams to bring projects from concept to construction, we want to meet you! At AHBL, we don’t just shape cities—we help to build vibrant communities where the work is rewarding. Our teams enjoy coming to work and flourish through innovation and creativity. Since 1969, our multi-discipline firm has delivered innovative solutions in engineering, planning, landscape architecture, and land surveying. Our team is passionate about creative problem-solving, and we take pride in the meaningful, diverse projects we deliver."
WHY AHBL? content: "We offer a fun and friendly atmosphere with team outings and ensure that the work is always enjoyableWe encourage out of the box thinking and innovative approaches to every projectOur teams celebrate successes and support each other through challenges. Our projects are primarily in the Pacific Northwest, so our work shapes the communities where we live and workWe offer continuous learning and professional development to advance your career"
Note there are missing spaces between sentences; we should preserve as is? The original had no spaces after periods? Actually it's "We offer a fun and friendly atmosphere with team outings and ensure that the work is always enjoyableWe encourage out of the box thinking...". There's missing space. We should preserve exactly as given? Probably we should keep the text as is, but we can add a space for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space could be considered inventing? It's minor formatting; but safer to keep exactly as given. However the original text likely missing spaces due to copy-paste; but we should not add new content. We'll keep as is, but it's awkward. Maybe we can keep as is; it's still substantive.
We'll combine into one
maybe two paragraphs. Responsibilities: "In this role you will work on a wide range of projects, including public K-12 schools, higher education, municipal buildings, stormwater, retrofits/parks, Department of Defense, and healthcare facilities. You will collaborate with clients and other team members in preparing civil engineering designs and calculations for site developments, local roads, stormwater, and utility improvements, including grading, drainage, sanitary sewer, water, and other related work." We could keep as
. Requirements (must-haves): list: - Bachelor of Science in Civil Engineering - EIT - Experience with AutoCAD - Strong written and verbal communication skills - Self-motivated with a positive attitude and a willingness to learn Note the original had "Bachelor of Science in Civil EngineeringEITExperience with AutoCADStrong written and verbal communication skillsSelf-motivated with a positive attitude and a willingness to learn". No spaces. We need to preserve the content but we can separate into list items