Professional Engineer- Site Development
CME Associates · Las Vegas, NV · 3 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment only, with sections for headings where content exists. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions. Keep substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "At Horrocks, we believe the best work comes from companies with values, that our people are our greatest resource, and that we have a responsibility to the communities where we live and work." This is about company values; could be part of About the role? Probably "About the role" heading.
- Role Summary: "Serve as a project engineer leading private and municipal site development projects from due diligence through construction support, with accountability for scope, schedule, budget, quality, and risk management." That's role summary.
- Then "What are the core responsibilities for the role?" then a long list of responsibilities.
- Then after responsibilities, there is a paragraph about performing services with ordinary skill etc. That seems like professional standards; maybe part of responsibilities or qualifications? Could be part of responsibilities (ethical standards). We'll include under responsibilities.
- Then after that, there is a list of technical tasks: "Prepare grading, roadway, drainage, water, and sanitary sewer plans using Civil 3D and related tools." etc. Those are also responsibilities.
- Then "Microsoft 365; AutoCAD Civil 3D; Hydraflow/Storm and Sanitary Analysis or SWMM; WaterCAD; HEC‑RAS; GIS tools." That's skills/tools.
- Then "Qualifications, Skills, And Competencies" heading with bullet list: BS or MS in Civil Engineering from an accredited program. 2+ years of experience post PE Certification Demonstrated project management and delivery skills; ability to supervise staff and develop execution plans and deliverables
- Then "Why would a candidate want this job?" paragraph about competitive base salary and award-winning benefits, then list: Medical, dental, vision, life, and disability insurance; Generous paid time off; 401(k): 50% match of contribution up to 6%; Professional development opportunities including in-house training; Paid professional organization membership and professional licensure
- Then "For more information, visit our website at www.horrocks.com" (application instruction? maybe drop). Then EEO line: "Equal Opportunity Employer including disability and protected veteran status" drop.
We need sections: About the role (intro + role summary). Responsibilities (the big list). Requirements? The posting has qualifications but not separate Requirements; we have Qualifications, Skills, And Competencies. We could map that to Qualifications and Skills sections. The instruction says use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content.
We have About the role: yes.
Responsibilities: yes.
Qualifications: we have BS/MS, 2+ years experience post PE, demonstrated project management skills etc. That's qualifications.
Skills: we have Microsoft 365; AutoCAD Civil 3D; Hydraflow/Storm and Sanitary Analysis or SWMM; WaterCAD; HEC‑RAS; GIS tools. Also maybe "Demonstrated project management and delivery skills; ability to supervise staff and develop execution plans and deliverables" could be skills but it's already in qualifications. We'll keep skills as the tools list.
Benefits: we have list of benefits.
Pay: we have "competitive base salary" but no specific number. The instruction says do NOT create Pay section unless posting actually states them. It says "competitive base salary" is a statement but not a specific figure. Is that enough? It says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "competitive base salary" is vague but not exactly placeholder like those. However it's not a specific amount. Might be considered filler? The instruction says avoid sections unless posting actually states them. It does state "competitive base salary". I'd argue it's stating that there is a competitive base salary, which is a statement of pay. So we could include Pay section with that sentence. But we need to avoid filler like "commensurate with experience". "competitive base salary" is similar but maybe acceptable. I'd include Pay with that sentence.
Schedule: no mention of schedule (work hours, remote, etc). So omit Schedule.
Requirements: we might not have a separate Requirements section besides qualifications. Could we treat qualifications as Requirements? The headings list includes Requirements separate from Qualifications. But we have qualifications content; we could put that under Requirements. However we also have Skills separate. The instruction says use those headings when content exists. We have qualifications content; we could map to Requirements. But we also have a separate "Qualifications, Skills, And Competencies" heading in the source. That includes both qualifications and skills. We could split: Qualifications (education, experience) and Skills (tools). The instruction includes both Qualifications and Skills headings. So we should use Qualifications for education/experience, Skills for tools. Then we might not need Requirements. But we could also put the "demonstrated project management and delivery skills; ability to supervise staff..." under Qualifications or Skills. I'd put under Qualifications as part of experience.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
We must not include Requirements if no specific content.
Now format: Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions. Keep substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "At Horrocks, we believe the best work comes from companies with values, that our people are our greatest resource, and that we have a responsibility to the communities where we live and work." This is about company values; could be part of About the role? Probably "About the role" heading.
- Role Summary: "Serve as a project engineer leading private and municipal site development projects from due diligence through construction support, with accountability for scope, schedule, budget, quality, and risk management." That's role summary.
- Then "What are the core responsibilities for the role?" then a long list of responsibilities.
- Then after responsibilities, there is a paragraph about performing services with ordinary skill etc. That seems like professional standards; maybe part of responsibilities or qualifications? Could be part of responsibilities (ethical standards). We'll include under responsibilities.
- Then after that, there is a list of technical tasks: "Prepare grading, roadway, drainage, water, and sanitary sewer plans using Civil 3D and related tools." etc. Those are also responsibilities.
- Then "Microsoft 365; AutoCAD Civil 3D; Hydraflow/Storm and Sanitary Analysis or SWMM; WaterCAD; HEC‑RAS; GIS tools." That's skills/tools.
- Then "Qualifications, Skills, And Competencies" heading with bullet list: BS or MS in Civil Engineering from an accredited program. 2+ years of experience post PE Certification Demonstrated project management and delivery skills; ability to supervise staff and develop execution plans and deliverables
- Then "Why would a candidate want this job?" paragraph about competitive base salary and award-winning benefits, then list: Medical, dental, vision, life, and disability insurance; Generous paid time off; 401(k): 50% match of contribution up to 6%; Professional development opportunities including in-house training; Paid professional organization membership and professional licensure
- Then "For more information, visit our website at www.horrocks.com" (application instruction? maybe drop). Then EEO line: "Equal Opportunity Employer including disability and protected veteran status" drop.
We need sections: About the role (intro + role summary). Responsibilities (the big list). Requirements? The posting has qualifications but not separate Requirements; we have Qualifications, Skills, And Competencies. We could map that to Qualifications and Skills sections. The instruction says use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content.
We have About the role: yes.
Responsibilities: yes.
Qualifications: we have BS/MS, 2+ years experience post PE, demonstrated project management skills etc. That's qualifications.
Skills: we have Microsoft 365; AutoCAD Civil 3D; Hydraflow/Storm and Sanitary Analysis or SWMM; WaterCAD; HEC‑RAS; GIS tools. Also maybe "Demonstrated project management and delivery skills; ability to supervise staff and develop execution plans and deliverables" could be skills but it's already in qualifications. We'll keep skills as the tools list.
Benefits: we have list of benefits.
Pay: we have "competitive base salary" but no specific number. The instruction says do NOT create Pay section unless posting actually states them. It says "competitive base salary" is a statement but not a specific figure. Is that enough? It says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "competitive base salary" is vague but not exactly placeholder like those. However it's not a specific amount. Might be considered filler? The instruction says avoid sections unless posting actually states them. It does state "competitive base salary". I'd argue it's stating that there is a competitive base salary, which is a statement of pay. So we could include Pay section with that sentence. But we need to avoid filler like "commensurate with experience". "competitive base salary" is similar but maybe acceptable. I'd include Pay with that sentence.
Schedule: no mention of schedule (work hours, remote, etc). So omit Schedule.
Requirements: we might not have a separate Requirements section besides qualifications. Could we treat qualifications as Requirements? The headings list includes Requirements separate from Qualifications. But we have qualifications content; we could put that under Requirements. However we also have Skills separate. The instruction says use those headings when content exists. We have qualifications content; we could map to Requirements. But we also have a separate "Qualifications, Skills, And Competencies" heading in the source. That includes both qualifications and skills. We could split: Qualifications (education, experience) and Skills (tools). The instruction includes both Qualifications and Skills headings. So we should use Qualifications for education/experience, Skills for tools. Then we might not need Requirements. But we could also put the "demonstrated project management and delivery skills; ability to supervise staff..." under Qualifications or Skills. I'd put under Qualifications as part of experience.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
We must not include Requirements if no specific content.
Now format: Use for each heading. Then content: use
for prose,
- for lists.
We need to preserve all substantive information, not invent or summarize away detail.
Let's extract precise text.
About the role:
Paragraph 1: "At Horrocks, we believe the best work comes from companies with values, that our people are our greatest resource, and that we have a responsibility to the communities where we live and work."
Role Summary: "Serve as a project engineer leading private and municipal site development projects from due diligence through construction support, with accountability for scope, schedule, budget, quality, and risk management."
We could combine into one
or two. Probably one
containing both sentences. Responsibilities: The list after "What are the core responsibilities for the role?" includes many items. We need to capture each bullet as
- . The text includes headings like "Project Planning & Work Plans:", "Scope, Schedule, and Budget Control:", etc. Each is a category with description after colon. We should treat each as a list item, preserving the description. Let's list them: - Project Planning & Work Plans: Develop project execution plans, scopes of work, and phase plans; tailor delivery approach (predictive, agile/hybrid) to context while focusing on value delivery and outcomes. - Scope, Schedule, and Budget Control: Establish baselines; monitor progress; apply change management; maintain earned value/cost/schedule reporting appropriate to project scale. Follow Company change management procedures and delegation of authority (DOA). - Risk & Opportunity Management: Identify, analyze (qualitative/quantitative), respond to, and monitor risks; proactively escalate issues and capture opportunities. - Stakeholder & Client Engagement: Map stakeholders; maintain transparent communications; lead meetings and presentations; manage expectations and decisions. - Quality Management (QA/QC): Plan and execute design reviews, interdisciplinary checks, model reviews, and constructability reviews; maintain document control and versioning. - Resource & Subconsultant Management: Forecast and allocate staff; coordinate multi‑office workshare; manage subconsultant scopes, deliverables, and invoices. - Health, Safety, and Environmental Stewardship: Integrate safety-by-design and environmental considerations; uphold company and client procedures. - Commercial Management: Prepare fee proposals; track budgets; support invoicing and cash flow; manage contract compliance and modifications. - Documentation & Lessons Learned: Maintain decision logs; archive calculations and correspondence; conduct closeout, performance review, and lessons-learned sessions. Then after that paragraph: "Perform services with the ordinary skill and care of a reasonably prudent Professional Engineer practicing under similar circumstances at the same time and in the same or similar locality; perfection is not implied" Then: "Hold paramount the safety, health, and welfare of the public; practice only within areas of competence; act as a faithful agent to the client; maintain honesty and integrity in all communications." Then: "Comply with applicable laws, codes, standards, and permitting requirements; identify constraints and assumptions transparently." Then: "Avoid expanding obligations beyond insurable standard-of-care language unless expressly negotiated (e.g., “best,” “highest,” or “ensure” may inadvertently elevate liability)." Then: "Document key decisions, design bases, and limitations (including data gaps and uncertainties such as those arising from climate, geotechnical, or hydrologic variability)." Then: "Follow the firm’s Quality Management Plan (QMP)" Then: "Plan checklists and hold-gates for calculations, models, drawings, and specifications; incorporate independent technical reviews and interdisciplinary coordination." Then: "Ensure traceability of inputs, assumptions, and revisions; manage document control per project standards." Then: "Pursue continuous improvement via audits, corrective actions, and client feedback; use metrics to assess process effectiveness." Then: "Prepare grading, roadway, drainage, water, and sanitary sewer plans using Civil 3D and related tools." Then: "Develop technical memoranda, design plans, specifications, and reports from due diligence through final submittal and bidding." Then: "Prepare supporting calculations, construction specifications, permit packages, and responses to agency comments." Then: "Prepare construction cost models and opinions of probable cost across project phases; support bidding and procurement." Then: "Provide construction-phase support including contractor coordination and observation consistent with scope." Then: "Lead and mentor other team members, engineers, and designers; foster collaborative, inclusive teams across disciplines and offices." Then: "Coordinate with clients, agencies, and subconsultants; support pursuit efforts and proposals, including scopes, schedules, budgets, and presentations." All these are responsibilities. We need to ensure we don't miss any. Now Qualifications: - "BS or MS in Civil Engineering from an accredited program." - "2+ years of experience post PE Certification" - "Demonstrated project management and delivery skills; ability to supervise staff and develop execution plans and deliverables" We could also include "Professional Engineer (PE) certification" implied. Now Skills: - "Microsoft 365; AutoCAD Civil 3D; Hydraflow/Storm and Sanitary Analysis or SWMM; WaterCAD; HEC‑RAS; GIS tools." We could list each as separate
- or keep as one string. Probably better to split: Microsoft 365, AutoCAD Civil 3D, Hydraflow/Storm and Sanitary Analysis or SWMM, WaterCAD, HEC‑RAS, GIS tools.
Now Benefits:
List:
- Medical, dental, vision, life, and disability insurance
- Generous paid time off
- 401(k): 50% match of contribution up to 6%
- Professional development opportunities including in-house training
- Paid professional organization membership and professional licensure
Now Pay:
- "competitive base salary" (maybe also "award-winning benefits" but that's benefits). We'll include just the sentence: "At Horrocks, you can expect a competitive base salary and award-winning benefits." Actually that sentence includes benefits too. But we already have benefits list. We could extract "competitive base salary" as pay. The sentence: "At Horrocks, you can expect a competitive base salary and award-winning benefits." We'll put Pay: competitive base salary.
We should not duplicate benefits.
Now ensure we don't include boilerplate: "For more information, visit our website at www.horrocks.com" drop. EEO line drop.
Now output HTML.
Structure:
About the role
At Hor