Project Engineer (Entry Level)
Garver · College Station, TX · 1 mo ago
EngineeringVolunteer
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Job title: Project Engineer (Entry Level). Not to repeat as heading.
We need sections:
- About the role: description of role, team, responsibilities? Usually "About the role" includes overview. We'll include a paragraph summarizing.
- Responsibilities: list of duties: engineering calculations, detailed design for variety of projects, working with clients, production of design phase deliverables (reports, technical memoranda, design manuals, plans, sections, details, specifications). Also maybe "ensure expectations of service are exceeded". We'll list.
- Requirements: Bachelor's degree in civil, environmental, or biological/biosystems engineering from ABET accredited program; Registered as EIT or able to obtain in next 6 months; Strong communications skills; Strong working knowledge of MS Word, Excel, PowerPoint, Project and Outlook.
- Qualifications: maybe Preferred Skills? Actually "Preferred Skills" includes internship experience, Master's degree, Microstation, WaterCAD, SewerCAD, process modeling software Hydromantis GPS-X or BioWin. Those are preferred qualifications. Could be under "Qualifications" or "Skills". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can separate Requirements (must-have) and Qualifications (preferred) and Skills (technical). But we need to avoid thin sections. Let's think.
We have:
- Requirements (must): Bachelor's degree, EIT, strong communications, MS Office.
- Preferred Skills: 0-1 years internship experience related to design of water/wastewater systems; Master's degree; Microstation, WaterCAD, SewerCAD experience; Experience in process modeling software, Hydromantis GPS-X or BioWin.
We could combine Preferred Skills into "Qualifications" or "Skills". Since they are skills/qualifications, maybe put under "Qualifications". But we also have "Skills" heading for technical skills like MS Office, Microstation etc. However we already have MS Office in Requirements. Could put technical skills under "Skills". Let's decide:
- Requirements: education, EIT, communication skills.
- Qualifications: preferred qualifications (internship, Master's degree).
- Skills: technical skills: MS Word, Excel, PowerPoint, Project, Outlook; Microstation, WaterCAD, SewerCAD; process modeling software Hydromantis GPS-X or BioWin.
But we have duplication: MS Office appears both in Requirements and Skills. Could keep it under Requirements as "Strong working knowledge of MS Word, Excel, PowerPoint, Project and Outlook". Then Skills could list the specialized software: Microstation, WaterCAD, SewerCAD, Hydromantis GPS-X, BioWin.
Alternatively, we could have only Requirements and Skills, and omit Qualifications. But we have preferred qualifications like Master's degree and internship experience; those are not strictly skills but qualifications. Could put them under "Qualifications". That seems appropriate.
Now Benefits: The posting mentions "Garver offers its employees programs such as company-paid professional memberships, company support for industry licenses and continuing education opportunities that foster a progressive atmosphere. Garver provides the tools, resources, and environment to develop leaders, stimulate ideas, and accomplish projects. By offering highly competitive salary packages, attractive benefits, and a comprehensive wellness program; Garver walks the talk when it comes to work-life balance." So we have benefits: company-paid professional memberships, support for industry licenses, continuing education opportunities, tools/resources, comprehensive wellness program. Also "highly competitive salary packages" but that's Pay. We'll treat Pay separate if specific salary not given. The posting does not give specific salary numbers, just "highly competitive salary packages". According to rule: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (company-paid professional memberships, etc.) and mentions "attractive benefits" and "comprehensive wellness program". So we can include Benefits section with those specifics. Pay: they mention "highly competitive salary packages" but no specific numbers or range. That's vague; rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "highly competitive salary packages" is somewhat vague but still a statement. However it's not a specific number or range. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "highly competitive salary packages". That is a statement about pay, albeit not specific. But it's not a placeholder like "commensurate with experience". It's a qualitative statement. I'd say we can include Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." If we include Pay with just that phrase, it's thin. Might be better to omit Pay because it's not specific. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (highly competitive salary packages). But also "Prefer a few substantive sections over many thin ones." So we could combine Pay into Benefits? But they are separate headings. Could we omit Pay and just mention salary in Benefits? Not ideal. I'd lean to omit Pay because it's not specific and could be considered thin. However the instruction says "include a section ONLY when the posting has real, specific content for it". "highly competitive salary packages" is not specific; it's generic. So maybe we should omit Pay.
Schedule: No mention of schedule (full-time, part-time, hours). So omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
Now we need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting.
Let's extract details:
About the role: "Garver is seeking a Project Engineer (Entry-Level) in College Station, TX to join our established Water team. The Project Engineer will be led by a Project Manager on a team consisting of multi-discipline design engineers focused on the production of design phase deliverables including reports, technical memoranda, design manuals, plans, sections, details and specifications. The Project Engineer must be capable of working closely with clients to ensure their expectations of service are exceeded."
We can put that as a paragraph.
Responsibilities: "This position will be responsible for engineering calculations and detailed design for a variety of projects, such as: Water distribution and wastewater collection, including pumping and storage Sewer distribution and collection, pumping and lifts Water and wastewater treatment plants Improvements and retrofitting of existing treatment facilities"
We can list as bullet list.
Also maybe include "production of design phase deliverables" but that's already in About the role. Could also be responsibility. But we already covered.
Requirements: Bachelor's degree in civil, environmental, or biological/biosystems engineering from an ABET accredited program; Registered as an Engineer In Training (EIT) or able to obtain in the next 6 months; Strong communications skills; Strong working knowledge of MS Word, Excel, PowerPoint, Project and Outlook.
Qualifications (preferred): 0-1 years of internship experience related to design of water/wastewater systems; Master’s degree in civil, environmental, or biological/biosystems engineering from an ABET accredited program.
Skills: Microstation, WaterCAD, or SewerCAD experience; Experience in process modeling software, Hydromantis GPS-X or BioWin.
Also maybe include "Strong working knowledge of MS Word, Excel, PowerPoint, Project and Outlook" as skill but we already have in Requirements. Could duplicate but okay. However to avoid duplication, we could keep it in Requirements and not repeat in Skills. But Skills heading expects technical skills; we could still include MS Office there but it's okay. However we might want to avoid duplication. I'd keep MS Office in Requirements only.
Benefits: company-paid professional memberships; company support for industry licenses; continuing education opportunities; tools, resources, and environment to develop leaders, stimulate ideas, and accomplish projects; comprehensive wellness program. Also "highly competitive salary packages" but we omitted Pay. Could mention "attractive benefits" but that's vague. We'll list the concrete benefits.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...