Project Engineer - Kingfield, Maine

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse the posting: - Intro: description about company, location, role, etc. This could be "About the role" or maybe "About the role" heading. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have

About the role

then a paragraph describing. - Responsibilities: list: site design development of drawings stormwater management design coordination with project stakeholders regulatory permitting construction administration. Also maybe "Acorn’s current projects include:" but that's not responsibilities; it's more about projects. Could be part of responsibilities or maybe separate "Projects" but not required. We'll include responsibilities list. - Requirements: list: Bachelor’s Degree in Civil Engineering, 2-6 years’ experience with design, permitting and construction administration for various site design projects within Maine, Strong technical and engineering design skills, Proficiency in AutoCAD, Civil 3D & HydroCAD, Understanding of Local, Maine and Federal permitting regulations and applications, Experience with stormwater treatment design, EI Certification required. Candidates actively pursuing PE licensure are strongly encouraged to apply. Upper limit of salary range may be increased pending licensure credentials. That last sentence about salary is maybe Pay? But they said only include Pay if posting actually states them. It mentions "Upper limit of salary range may be increased pending licensure credentials." That's a mention of salary but not a specific number. It's vague. Should we include Pay section? The rule: 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. Here they mention salary range may be increased pending licensure credentials. That's not a specific figure, but it's still some info about pay. It's not filler like "commensurate with experience"? It's somewhat vague but still mentions salary. I'd consider it as stating something about pay, albeit not a number. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about salary (upper limit may be increased). So we could include a Pay section with that sentence. However we need to avoid filler placeholder like "varies" etc. This is somewhat similar to "varies". Might be considered filler. Safer to not include Pay section because it's not a concrete statement. The instruction: "Prefer a few substantive sections over many thin ones." So maybe omit Pay. - Benefits: list: Health insurance, Dental insurance, Company paid ST/LT/Life insurance, ESOP participation, 401(k), Paid time off, Paid holidays, Professional development, Licensure support, Continuing education reimbursement. Also "Employees will be provided with a laptop to enable work within our hybrid work model." That's a benefit? Could be part of Benefits or maybe separate. Also hybrid remote model: 3 days in office, 2 days remote after onboarding. That's Schedule. So we have Schedule info: "It’s anticipated the hybrid remote model would include 3 days in the Kingfield office and 2 days remote following an onboarding period." That's specific schedule. So we should include Schedule section. - Benefits section: include the list. - Also maybe "Qualifications" vs "Requirements". The posting has Requirements. We'll use Requirements heading. - Skills: maybe not separate; we could embed skills in Requirements. But we could have Skills section if we want. However we should avoid thin sections. The posting mentions "Strong technical and engineering design skills", "Proficiency in AutoCAD, Civil 3D & HydroCAD", etc. Those are skills. Could be part of Requirements. We'll keep Requirements. - About the role: include description paragraphs. - Also maybe "Projects" not needed. - Ensure we don't repeat job title as heading. - Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. - Remove duplicated lines. - Output only HTML fragment. Let's craft:

About the role

Acorn Engineering, Inc., a Maine-based, 100% employee-owned civil engineering, construction administration, land surveying, and landscape architecture firm, has a full-time opportunity for a Project Engineer in our Kingfield office. While Acorn's primary office is located in Portland, we established our Kingfield location in 2023 to better serve clients and communities throughout Western Maine. As our project portfolio continues to grow across the region, we are seeking a motivated engineer to help shape the future of this expanding office and work on a variety of exciting projects. This position offers a unique opportunity to be part of a growing branch of the company, working directly alongside local leadership and playing a meaningful role in its long-term success. Unlike larger firms where engineers may become specialized in a narrow range of projects, Acorn's Kingfield office offers exposure to a diverse and ever-changing workload. This role is ideal for someone who enjoys variety, values hands-on involvement, and is energized by new challenges and opportunities. The successful candidate will work on projects spanning a broad geographic area, while collaborating with colleagues across Acorn's multiple disciplines and office locations. As an integral member of the project team, the Project Engineer will be involved throughout the full project lifecycle, from initial planning and design through permitting and construction. Whether your interests include skiing, mountain biking, hiking, paddling, fishing, or simply living and working close to Maine's natural resources, Kingfield offers a unique setting to build both a career and lifestyle.

Responsibilities

• Site design development of drawings
• Stormwater management design
• Coordination with project stakeholders
• Regulatory permitting
• Construction administration

Maybe also include "Acorn’s current projects include:" but that's not responsibilities; could be part of About the role? Might be extra detail. Could add a paragraph about projects under About the role or separate "Projects" but not required. The instruction: Prefer few substantive sections over many thin ones. So maybe incorporate that into About the role as a sentence. But we already have a long paragraph; we could add a sentence: "Acorn’s current projects include municipal infrastructure projects, resort development, erosion and sedimentation control inspections, stream smart culvert replacements and assessment projects, trail master planning and design, workforce and affordable housing projects, and single family home site design and permitting." That adds detail. Let's add to About the role paragraph. Also mention "Acorn partners with high-quality clientele and champions their projects from initial concept, through planning board approval to final completion." Could add. Also mention "This is an exciting opportunity to assist a small (but growing) firm with a variety of tasks. We offer opportunities to grow professionally, volunteer, collaborate on exciting projects and develop lasting relationships both inside and outside of our firm. We look to empower our employees and provide them with the tools to be successful." Could add. But we must not invent or summarize away detail; we can include these as they are in posting. Let's rewrite About the role to include all those details. We'll produce a paragraph that includes: - Acorn Engineering description. - Kingfield office established 2023. - Growing portfolio, seeking motivated engineer. - Opportunity to be part of growing branch, work alongside local leadership. - Exposure to diverse workload. - Ideal for someone who enjoys variety, hands-on involvement, new challenges. - Work on projects spanning broad geographic area, collaborating across disciplines and offices. - Involved throughout full project lifecycle. - Lifestyle: skiing, mountain biking, hiking, paddling, fishing, close to natural resources. - Responsibilities list (we already have separate). - Acorn’s current projects include: municipal infrastructure projects, resort development, erosion and sedimentation control inspections, stream smart culvert replacements and assessment projects, trail master planning and design, workforce and affordable housing projects, single family home site design and permitting. - Acorn partners with high-quality clientele and champions their projects from initial concept, through planning board approval to final completion. - Exciting opportunity to assist a small (but growing) firm with a variety of tasks. - Opportunities to grow professionally, volunteer, collaborate on exciting projects and develop lasting relationships. - Empower employees, provide tools to be successful. - Employees provided with laptop for hybrid work model. - Hybrid remote model: 3 days in Kingfield office, 2 days remote after onboarding. - Benefits list. - Requirements list. We need to avoid duplication: responsibilities already listed; we shouldn't repeat them in About the role. But we can keep responsibilities separate. We need to ensure we don't repeat the same content in multiple places; but it's okay if some overlap as long as we preserve all info. However we should aim not to duplicate exactly same sentences. We'll keep About the role with narrative, and Responsibilities as list. Now Benefits: list as

• ...

. Schedule: we have hybrid model: 3 days in office, 2 days remote after onboarding. That's schedule. We'll create

Schedule

It’s anticipated the hybrid remote model would include 3 days in the Kingfield office and 2 days remote following an onboarding period.

Now Requirements: list. We'll also include note about EI Certification required, candidates pursuing PE licensure encouraged, upper limit of salary range may be increased pending licensure credentials. That last note about salary maybe we could include in Requirements or maybe a separate Pay section. Since it's about salary, but it's vague. I'd rather include it in Requirements as a note? But it's not a requirement; it's about salary. Could add a separate Pay section but risk being considered filler. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about salary (upper limit may be increased). So we could create Pay section with that sentence. However it's not a specific number; but it's still stating something about pay. I'd lean to include Pay section because it's actual content about pay, albeit not a number. The rule about filler: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "Upper limit of salary range may be increased pending licensure credentials." is not exactly filler like "varies" but it's still vague. Might be considered placeholder? I'd say it's not filler; it's a statement about potential increase. So we can include Pay section. Thus we will have Pay section:

Pay

Upper limit of salary range may be increased pending licensure credentials.

But we also have mention of "Candidates actively pursuing PE licensure are strongly encouraged to apply." That's more of a preference/encouragement, could be part of Requirements or Qualifications. We'll include in Requirements as a bullet. Now we need to ensure we don't include any boilerplate like EEO etc. Not present. Now produce HTML fragment. Let's craft:

About the role

Acorn Engineering, Inc., a Maine-based, 100% employee-owned civil engineering, construction administration, land surveying, and landscape architecture firm, has a full-time opportunity for a Project Engineer in our Kingfield office. While Acorn's primary office is located in Portland, we established our Kingfield location in 2023 to better serve clients and communities throughout Western Maine. As our project portfolio continues to grow across the region, we are seeking a motivated engineer to help shape the future of this expanding office and work on a variety of exciting projects. This position offers a unique opportunity to be part of a growing branch of the company,