Project Manager/ Estimator
Jobot · Springville, UT · 4 wk ago
On-siteProject Management$90k–$125k/yrFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines.
We need to parse the job posting.
Let's extract content:
Job title: Heavy Civil Estimator (but we must not repeat as heading). The posting says "Job details: Heavy Civil Estimator". We'll not output that as heading.
Hosted by: Bryna Rabin (maybe minor metadata; we can fold into short p or drop). Probably we can include as a short p.
"Are you a fit? Easy Apply now by clicking the "Easy Apply" button and sending us your resume." That's application instruction; we must remove application instructions. So we drop that line.
Salary: $90,000 - $125,000 per year => Pay section.
"A bit about us: If you are a Project Manager or Project Engineer looking for a change - we are looking for YOU! We have been in business for 44 years building municipal infrastructure. Based in Springville, Utah with satellite offices in Salt Lake County, Payson, and St. George, we have 35 office employees and 140 field employees including seven pipe crews, four mechanical crews, three concrete crews, and our own metal fabrication shop where we custom-make junctures, blow-offs, and other custom parts needed for unique situations. We are experienced in pipelines, water and wastewater treatment facilities, pump stations, lift stations, vaults and valves, diversion structures, dams, ponds, water tanks, bores, canals and culverts, parks, trails, and pedestrian bridges. Why join us? We Can Solve That, We've Done It Before!" This is about the company; could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put this under About the role (or maybe About the company). We'll use About the role.
"Job Details We are looking for a Project Manager and a Project Engineer. This role is a great fit for someone who is detailed oriented, tech-savvy, and familiar with the construction industry." This is also about role.
Then "Project Engineer Roles:" with list items. Actually they list responsibilities under Project Engineer Roles. Then "Responsibilities Job Description:" with list items. So we need Responsibilities section.
Then "Qualifications" heading with list.
Then "Additional Information Benefits:" with list of benefits.
We also have Pay (salary). No schedule info given. So we should not create Schedule section.
We also might have Skills? Not explicitly listed but qualifications include proficiency with Microsoft Office, strong interpersonal etc. Could be considered Skills. But we have Qualifications section already; we could put skills under Qualifications or separate Skills. The instruction: prefer a few substantive sections over many thin ones. So we could combine qualifications and skills into Qualifications. But we have a Qualifications heading already from posting; we should keep that. The instruction says use headings for those categories if content exists. So we will have Qualifications (as per posting). We might also have Skills if there are distinct skill items not covered. The qualifications list includes: 1 or more years in a receptionist/administrative position, 1 or more years in a construction environment preferred, Proficiency with Microsoft Office (Outlook, Word, Excel, PowerPoint), Strong interpersonal, verbal, and written communication skills, 2+ year experience Bachelor’s Degree OSHA 10. That's a mix of experience and skills. We'll keep as Qualifications.
Benefits: list.
Pay: salary.
About the role: combine the "A bit about us:" and "Job Details" paragraphs.
Responsibilities: combine the Project Engineer Roles list and Responsibilities Job Description list.
We must not include duplicated lines. Need to ensure we capture all substantive info.
Let's extract responsibilities list:
Under "Project Engineer Roles:" they list:
1. Deliver Project Documentation in Timely & Quality Manner
2. Maintain Project Schedule
3. Provide Timely Support to PM as assigned
Then under "Responsibilities Job Description:" they have numbered list with subpoints:
1. Deliver Project Documentation in Timely & Quality Manner
- Successfully read, understand, and evaluate drawings and specifications
- Comprehend and successfully complete submittals, RFI, pay applications, potential change orders, permits, SWPPP
- Use AutoCAD to review drawings
- Use Microsoft successfully to update documents
- Use Excel spreadsheets to manage data
- Understand job cost phasing and communicate with site staff
2. Maintain Project Schedule
- Update all parties
- Use KeyStyle to monitor field worker timecards
- Use P6 to create and update diverse project schedules
- Understand critical path and contract timelines
- Attend project meeting with schedule ready
- Create and maintain three-week schedule look ahead
- Maintain budget and stay within project phases
3. Provide Timely Support to PM as assigned
- Maintain timely communication with owner representative
- Complete SWPPP inspection and submit documentation
- Complete and submit traffic control plans
- Complete mobilization plans
- Coordinate with utility companies
- Coordinate with Blue Stakes
- Collect correct permits
We need to preserve all substantive info. We can combine these into a single responsibilities list, maybe grouping under each main responsibility.
We should not repeat the same heading lines duplicated. The "Deliver Project Documentation in Timely & Quality Manner" appears twice (as heading and as subheading). We'll include it once.
We need to output HTML:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines.
We need to parse the job posting.
Let's extract content:
Job title: Heavy Civil Estimator (but we must not repeat as heading). The posting says "Job details: Heavy Civil Estimator". We'll not output that as heading.
Hosted by: Bryna Rabin (maybe minor metadata; we can fold into short p or drop). Probably we can include as a short p.
"Are you a fit? Easy Apply now by clicking the "Easy Apply" button and sending us your resume." That's application instruction; we must remove application instructions. So we drop that line.
Salary: $90,000 - $125,000 per year => Pay section.
"A bit about us: If you are a Project Manager or Project Engineer looking for a change - we are looking for YOU! We have been in business for 44 years building municipal infrastructure. Based in Springville, Utah with satellite offices in Salt Lake County, Payson, and St. George, we have 35 office employees and 140 field employees including seven pipe crews, four mechanical crews, three concrete crews, and our own metal fabrication shop where we custom-make junctures, blow-offs, and other custom parts needed for unique situations. We are experienced in pipelines, water and wastewater treatment facilities, pump stations, lift stations, vaults and valves, diversion structures, dams, ponds, water tanks, bores, canals and culverts, parks, trails, and pedestrian bridges. Why join us? We Can Solve That, We've Done It Before!" This is about the company; could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put this under About the role (or maybe About the company). We'll use About the role.
"Job Details We are looking for a Project Manager and a Project Engineer. This role is a great fit for someone who is detailed oriented, tech-savvy, and familiar with the construction industry." This is also about role.
Then "Project Engineer Roles:" with list items. Actually they list responsibilities under Project Engineer Roles. Then "Responsibilities Job Description:" with list items. So we need Responsibilities section.
Then "Qualifications" heading with list.
Then "Additional Information Benefits:" with list of benefits.
We also have Pay (salary). No schedule info given. So we should not create Schedule section.
We also might have Skills? Not explicitly listed but qualifications include proficiency with Microsoft Office, strong interpersonal etc. Could be considered Skills. But we have Qualifications section already; we could put skills under Qualifications or separate Skills. The instruction: prefer a few substantive sections over many thin ones. So we could combine qualifications and skills into Qualifications. But we have a Qualifications heading already from posting; we should keep that. The instruction says use headings for those categories if content exists. So we will have Qualifications (as per posting). We might also have Skills if there are distinct skill items not covered. The qualifications list includes: 1 or more years in a receptionist/administrative position, 1 or more years in a construction environment preferred, Proficiency with Microsoft Office (Outlook, Word, Excel, PowerPoint), Strong interpersonal, verbal, and written communication skills, 2+ year experience Bachelor’s Degree OSHA 10. That's a mix of experience and skills. We'll keep as Qualifications.
Benefits: list.
Pay: salary.
About the role: combine the "A bit about us:" and "Job Details" paragraphs.
Responsibilities: combine the Project Engineer Roles list and Responsibilities Job Description list.
We must not include duplicated lines. Need to ensure we capture all substantive info.
Let's extract responsibilities list:
Under "Project Engineer Roles:" they list:
1. Deliver Project Documentation in Timely & Quality Manner
2. Maintain Project Schedule
3. Provide Timely Support to PM as assigned
Then under "Responsibilities Job Description:" they have numbered list with subpoints:
1. Deliver Project Documentation in Timely & Quality Manner
- Successfully read, understand, and evaluate drawings and specifications
- Comprehend and successfully complete submittals, RFI, pay applications, potential change orders, permits, SWPPP
- Use AutoCAD to review drawings
- Use Microsoft successfully to update documents
- Use Excel spreadsheets to manage data
- Understand job cost phasing and communicate with site staff
2. Maintain Project Schedule
- Update all parties
- Use KeyStyle to monitor field worker timecards
- Use P6 to create and update diverse project schedules
- Understand critical path and contract timelines
- Attend project meeting with schedule ready
- Create and maintain three-week schedule look ahead
- Maintain budget and stay within project phases
3. Provide Timely Support to PM as assigned
- Maintain timely communication with owner representative
- Complete SWPPP inspection and submit documentation
- Complete and submit traffic control plans
- Complete mobilization plans
- Coordinate with utility companies
- Coordinate with Blue Stakes
- Collect correct permits
We need to preserve all substantive info. We can combine these into a single responsibilities list, maybe grouping under each main responsibility.
We should not repeat the same heading lines duplicated. The "Deliver Project Documentation in Timely & Quality Manner" appears twice (as heading and as subheading). We'll include it once.
We need to output HTML: About the role
then
...
maybe multiple paragraphs. ThenResponsibilities
then- ...
- inside li for subpoints? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can do nested lists for subpoints.
Then
Qualifications
then- ...
Benefits
then- ...
Pay
then$90,000 - $125,000 per year
. We must not include Schedule. We must not include any boilerplate like EEO, privacy, etc. We must not include application instructions like "Easy Apply now". Remove those. We must not include "Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page!" (that's boilerplate). Remove. We must not include "Jobot is an Equal Opportunity Employer..." etc. We must not include "Sometimes Jobot is required to perform background checks..." etc. We must not include "Information collected and processed..." etc. We must not include "By applying for this job, you agree to receive calls..." etc. We must not include "You can access our privacy policy here:" etc. We must not include "Are you a fit? Easy Apply now by clicking the "Easy Apply" button and sending us your resume." (application instruction). Remove. We must not include "Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button." (application instruction). Remove. We must not include "Job Details" as heading? It's not a standard heading; we can treat as part of About the role. We must not include "Additional Information Benefits:" as heading; we will use Benefits. Now let's craft content. About the role: combine the two paragraphs: "If you are a Project Manager or Project Engineer looking for a change - we are looking for YOU! We have been in business for 44 years building municipal infrastructure. Based in Springville, Utah with satellite offices in Salt Lake County, Payson, and St. George, we have 35 office employees and 140 field employees including seven pipe crews, four mechanical crews, three concrete crews, and our own metal fabrication shop where we custom-make junctures, blow-offs, and other custom parts needed for unique situations. We are experienced in pipelines, water and wastewater treatment facilities, pump stations, lift stations, vaults and valves, diversion structures, dams, ponds, water tanks, bores, canals and culverts, parks, trails, and pedestrian bridges. Why join us? We Can Solve That, We've Done It Before!" Plus "Job Details We are looking for a Project Manager and a Project Engineer. This role is a great fit for someone who is detailed oriented, tech-savvy, and familiar with the construction industry." We can merge: "We are looking for a Project Manager and a Project Engineer. This role is a great fit for someone who is detail-oriented, tech-savvy, and familiar with the construction industry." (Note: original said detailed oriented; we can correct grammar? We should preserve exact wording? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Changing "detailed oriented" to "detail-oriented" is a minor edit but could be considered altering. Safer to keep as is: "detailed oriented". We'll keep original phrasing. Thus About the role paragraph: combine both. We'll output as...
. Possibly two paragraphs but we can combine. Now Responsibilities: We'll create a list with three main items, each containing sublist. We need to capture all subpoints exactly as given. Let's list them: Main 1: Deliver Project Documentation in Timely & Quality Manner Subpoints: - Successfully read, understand, and evaluate drawings and specifications - Comprehend and successfully complete submittals, RFI, pay applications, potential change orders, permits, SWPPP - Use AutoCAD to review drawings - Use Microsoft successfully to update documents - Use Excel spreadsheets to manage data - Understand job cost phasing and communicate with site staff Main 2: Maintain Project Schedule Subpoints: - Update all parties - Use KeyStyle to monitor field worker timecards - Use P6 to create and update diverse project schedules - Understand critical path and contract timelines - Attend project meeting with schedule ready - Create and maintain three-week schedule look ahead - Maintain budget and stay within project phases Main 3: Provide Timely Support to PM as assigned Subpoints: - Maintain timely communication with owner representative - Complete SWPPP inspection and submit documentation - Complete and submit traffic control plans - Complete mobilization plans - Coordinate with utility companies - Coordinate with Blue Stakes - Collect correct permits We'll output nested lists. Now Qualifications: list as given: - 1 or more years in a receptionist/administrative position - 1 or more years in a construction environment preferred - Proficiency with Microsoft Office (Outlook, Word, Excel, PowerPoint) - Strong interpersonal, verbal, and written communication skills - 2+ year experience Bachelor’s Degree OSHA 10 Note: The last item seems garbled: "2+ year experience Bachelor’s Degree OSHA 10". Likely means 2+ years experience, Bachelor's Degree, OSHA 10. We'll keep as is. Now Benefits: list: - 401(k) - 401(k) matching - Dental insurance - Disability insurance - Employee assistance program - Flexible spending account - Health insurance - Health savings account - Life insurance - Paid time off - Vision insurance Note there is duplicate "401(k)" and "401(k) matching". We'll keep both as they appear. Now Pay:$90,000
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can do nested lists for subpoints.
Then