Civil Engineer (Project Engineer) - Mid Level
Mace · New York, United States · 2 wk ago
HybridInformation Technology$12/hrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description about Mace, purpose, project details. That could be "About the role" or maybe "About the project". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. We have responsibilities list, requirements list, qualifications? The posting includes "You’ll Be Responsible For" then bullet-like sentences separated by periods. We need to turn those into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. We have responsibilities list, requirements list, qualifications? The posting includes "You’ll Be Responsible For" then bullet-like sentences separated by periods. We need to turn those into - . Also "You’ll Need To Have" list of qualifications/skills. Also note salary: "Note: The estimated starting salary for this position is $130k. Starting salary may vary based on permissible, non-discriminatory factors such as experience, skills and qualifications." That is pay info, so we can include a Pay section with that sentence. Benefits? Not mentioned. Schedule? Not mentioned. So we can have sections: About the role (maybe intro paragraph), Responsibilities, Requirements (or Qualifications?), Skills? The posting includes both qualifications and skills mixed. We could combine into Requirements (education, experience) and Skills (technical proficiencies). But we need to avoid thin sections. Perhaps we can have: About the role (intro paragraph), Responsibilities, Requirements (education + experience + knowledge), Skills (technical proficiencies + soft skills), Pay. That seems reasonable.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. The posting includes values and inclusive employer statements; those could be considered boilerplate? They are not navigation/legal/EEO but they are values statements. Might be considered fluff but they are substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The values statements are not exactly EEO but could be considered boilerplate? Might be okay to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Values are not that. However they are generic corporate values; could be considered boilerplate but not explicitly prohibited. Safer to keep them? Might be considered filler. I'd keep them as part of About the role maybe.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, requirements, skills, salary.
Let's extract responsibilities sentences:
- Assist with design reviews, resolve technical issues, and coordinate design change documentation.
- Provide technical support during construction, review contractor submittals, and monitor progress against milestones.
- Facilitate communication among stakeholders, schedule meetings, and assist with project documentation, including drawings and specifications.
- Provide opinions on constructability, means and methods, and the impacts of technical decisions on the overall project, including analysis of critical path schedule impacts and scenario analyses.
- Support the integration and coordination of all HTP Packages, ensuring comprehensive interface management and collaboration among design, construction, and operations teams.
- Assist with programmatic oversight and management of project controls functions, including schedule, cost, change, risk, and document management.
- Update project controls procedures, workflow processes, and tools as requested.
- Prepare and submit monthly and quarterly project reports, including safety, quality, environmental, and milestone status updates.
- Maintain a “lessons learned” register and master “issues log” for the HTP.
- Support BIM technology implementation, including development and maintenance of digital models, coordination with designers, and integration of project information.
- Assist with configuration and implementation of project management information systems (PMIS) and other technology tools.
Now requirements/qualifications:
- Bachelor’s degree in Civil Engineering or related field.
- 3–7 years of experience in civil engineering, preferably on large infrastructure or transportation projects.
- Roadway engineering skills such as geometric design, grading, access management, permitting, utilities, stormwater management, roadway drainage design, 3D roadway modeling, traffic/accident analysis and traffic control and staging plans.
- Familiarity with project controls, scheduling, cost management, and risk management.
- Knowledge of federal, state, and local regulations relevant to major capital projects (NJDOT, NJDEP, NEPA, USACE, County or Municipal agencies, etc.).
- Experience with quality assurance, construction monitoring, and technical documentation.
- Proficiency with BIM, AutoCAD, MicroStation, PMIS, and Microsoft Office Suite.
- Strong communication, organizational, and problem-solving skills.
- Ability to work collaboratively with multidisciplinary teams and external stakeholders.
Now salary: "Note: The estimated starting salary for this position is $130k. Starting salary may vary based on permissible, non-discriminatory factors such as experience, skills and qualifications."
Now about the role/intro: The first paragraph about Mace purpose, project details. Let's capture that as About the role.
Paragraph: "At Mace, our purpose is to redefine the boundaries of ambition. We believe in creating places that are responsible, bringing transformative impact to our people, communities, and societies across the globe. To learn more about our purpose, culture, and priorities, visit our strategy site. Within our consult business we harness our unique combination of leading-edge practical expertise and project delivery consultancy to unlock the potential in every project. The Project Mace, as part of MPA delivery partner joint venture of Mace-Parsons-Arcadis, have been selected as the Gateway Development Commissions partners of choice to support the GDC across the Gateway Program in New York, inclusive of the Hudson Tunnel Project. The busiest rail connection between New York, New Jersey, and the Northeast Corridor, the Hudson Tunnel Project will improve capacity, reliability, and resiliency of commuter and intercity rail transit serving 800,000 daily passengers from Washington, D.C. to New York and New England. A milestone project supported by the bipartisan Infrastructure Investment and Jobs Act (IIJA), the project is slated to receive nearly $12 billion in federal funding, the largest investment in a mass transit project in modern history."
We can keep that as About the role.
Now we need to output HTML fragment only, no /. Use
for each section heading. Use - for lists. Use
for prose.
We need to decide which sections: About the role, Responsibilities, Requirements, Skills, Pay. Could combine Requirements and Skills? But we have distinct lists: education/experience/knowledge (requirements) and technical proficiencies + soft skills (skills). Might be okay to split.
We must not create sections with filler like "commensurate with experience". We have real content.
Now produce HTML:
About the role
At Mace, our purpose is to redefine the boundaries of ambition. We believe in creating places that are responsible, bringing transformative impact to our people, communities, and societies across the globe. To learn more about our purpose, culture, and priorities, visit our strategy site. Within our consult business we harness our unique combination of leading-edge practical expertise and project delivery consultancy to unlock the potential in every project. The Project Mace, as part of MPA delivery partner joint venture of Mace-Parsons-Arcadis, have been selected as the Gateway Development Commissions partners of choice to support the GDC across the Gateway Program in New York, inclusive of the Hudson Tunnel Project. The busiest rail connection between New York, New Jersey, and the Northeast Corridor, the Hudson Tunnel Project will improve capacity, reliability, and resiliency of commuter and intercity rail transit serving 800,000 daily passengers from Washington, D.C. to New York and New England. A milestone project supported by the bipartisan Infrastructure Investment and Jobs Act (IIJA), the project is slated to receive nearly $12 billion in federal funding, the largest investment in a mass transit project in modern history.
Responsibilities
- Assist with design reviews, resolve technical issues, and coordinate design change documentation.
- Provide technical support during construction, review contractor submittals, and monitor progress against milestones.
- Facilitate communication among stakeholders, schedule meetings, and assist with project documentation, including drawings and specifications.
- Provide opinions on constructability, means and methods, and the impacts of technical decisions on the overall project, including analysis of critical path schedule impacts and scenario analyses.
- Support the integration and coordination of all HTP Packages, ensuring comprehensive interface management and collaboration among design, construction, and operations teams.
- Assist with programmatic oversight and management of project controls functions, including schedule, cost, change, risk, and document management.
- Update project controls procedures, workflow processes, and tools as requested.
- Prepare and submit monthly and quarterly project reports, including safety, quality, environmental, and milestone status updates.
- Maintain a “lessons learned” register and master “issues log” for the HTP.
- Support BIM technology implementation, including development and maintenance of digital models, coordination with designers, and integration of project information.
- Assist with configuration and implementation of project management information systems (PMIS) and other technology tools.
Requirements
- Bachelor’s degree in Civil Engineering or related field.
- 3–7 years of experience in civil engineering, preferably on large infrastructure or transportation projects.
- Roadway engineering skills such as geometric design, grading, access management, permitting, utilities, stormwater management, roadway drainage design, 3D roadway modeling, traffic/accident analysis and traffic control and staging plans.
- Familiarity with project controls, scheduling, cost management, and risk management.
- Knowledge of federal, state, and local regulations relevant to major capital projects (NJDOT, NJDEP, NEPA, USACE, County or Municipal agencies, etc.).
- Experience with quality assurance, construction monitoring, and technical documentation.
Skills
- Proficiency with BIM, AutoCAD, MicroStation, PMIS, and Microsoft Office Suite.
- Strong communication, organizational, and problem-solving skills.
- Ability to work collaboratively with multidisciplinary teams and external stakeholders.
Pay
Note: The estimated starting salary for this position is $130k. Starting salary may vary based on permissible, non-discriminatory factors such as experience, skills and qualifications.
We should not include any extra sections like Benefits, Schedule.
Check for any duplicated lines: none.
Make sure we didn't include any boilerplate like values statements. We omitted them. That's okay; we removed them as they might be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values statements are not those, but we removed them; is that allowed? We must preserve ALL substantive information. Are values statements substantive? They are generic corporate values; might be considered boilerplate but not explicitly prohibited. However the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Values are not listed. So we should keep them if they are substantive. But they are generic; still they are part of posting. The instruction says "Preserve ALL substantive information". If we remove them, we might be removing substantive info? It's arguable. Safer to include them maybe in About the role as a paragraph. But we already have a long paragraph; we could append a sentence about values. However the values list includes multiple bullet points; we could incorporate them as a paragraph.
Let's include a short paragraph about values after the About the role paragraph, maybe as part of same section.
We can add: "Our values: Safety first - Going home safe and well: We champion a safe, diverse and inclusive working environment, understanding the importance of wellbeing in every team. Client focus - Deliver on our promise: We own the quality of deliverables
for each section heading. Use - for lists. Use
for prose.
We need to decide which sections: About the role, Responsibilities, Requirements, Skills, Pay. Could combine Requirements and Skills? But we have distinct lists: education/experience/knowledge (requirements) and technical proficiencies + soft skills (skills). Might be okay to split.
We must not create sections with filler like "commensurate with experience". We have real content.
Now produce HTML:
About the role
At Mace, our purpose is to redefine the boundaries of ambition. We believe in creating places that are responsible, bringing transformative impact to our people, communities, and societies across the globe. To learn more about our purpose, culture, and priorities, visit our strategy site. Within our consult business we harness our unique combination of leading-edge practical expertise and project delivery consultancy to unlock the potential in every project. The Project Mace, as part of MPA delivery partner joint venture of Mace-Parsons-Arcadis, have been selected as the Gateway Development Commissions partners of choice to support the GDC across the Gateway Program in New York, inclusive of the Hudson Tunnel Project. The busiest rail connection between New York, New Jersey, and the Northeast Corridor, the Hudson Tunnel Project will improve capacity, reliability, and resiliency of commuter and intercity rail transit serving 800,000 daily passengers from Washington, D.C. to New York and New England. A milestone project supported by the bipartisan Infrastructure Investment and Jobs Act (IIJA), the project is slated to receive nearly $12 billion in federal funding, the largest investment in a mass transit project in modern history.
Responsibilities
- Assist with design reviews, resolve technical issues, and coordinate design change documentation.
- Provide technical support during construction, review contractor submittals, and monitor progress against milestones.
- Facilitate communication among stakeholders, schedule meetings, and assist with project documentation, including drawings and specifications.
- Provide opinions on constructability, means and methods, and the impacts of technical decisions on the overall project, including analysis of critical path schedule impacts and scenario analyses.
- Support the integration and coordination of all HTP Packages, ensuring comprehensive interface management and collaboration among design, construction, and operations teams.
- Assist with programmatic oversight and management of project controls functions, including schedule, cost, change, risk, and document management.
- Update project controls procedures, workflow processes, and tools as requested.
- Prepare and submit monthly and quarterly project reports, including safety, quality, environmental, and milestone status updates.
- Maintain a “lessons learned” register and master “issues log” for the HTP.
- Support BIM technology implementation, including development and maintenance of digital models, coordination with designers, and integration of project information.
- Assist with configuration and implementation of project management information systems (PMIS) and other technology tools.
Requirements
- Bachelor’s degree in Civil Engineering or related field.
- 3–7 years of experience in civil engineering, preferably on large infrastructure or transportation projects.
- Roadway engineering skills such as geometric design, grading, access management, permitting, utilities, stormwater management, roadway drainage design, 3D roadway modeling, traffic/accident analysis and traffic control and staging plans.
- Familiarity with project controls, scheduling, cost management, and risk management.
- Knowledge of federal, state, and local regulations relevant to major capital projects (NJDOT, NJDEP, NEPA, USACE, County or Municipal agencies, etc.).
- Experience with quality assurance, construction monitoring, and technical documentation.
Skills
- Proficiency with BIM, AutoCAD, MicroStation, PMIS, and Microsoft Office Suite.
- Strong communication, organizational, and problem-solving skills.
- Ability to work collaboratively with multidisciplinary teams and external stakeholders.
Pay
Note: The estimated starting salary for this position is $130k. Starting salary may vary based on permissible, non-discriminatory factors such as experience, skills and qualifications.
We should not include any extra sections like Benefits, Schedule.
Check for any duplicated lines: none.
Make sure we didn't include any boilerplate like values statements. We omitted them. That's okay; we removed them as they might be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values statements are not those, but we removed them; is that allowed? We must preserve ALL substantive information. Are values statements substantive? They are generic corporate values; might be considered boilerplate but not explicitly prohibited. However the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Values are not listed. So we should keep them if they are substantive. But they are generic; still they are part of posting. The instruction says "Preserve ALL substantive information". If we remove them, we might be removing substantive info? It's arguable. Safer to include them maybe in About the role as a paragraph. But we already have a long paragraph; we could append a sentence about values. However the values list includes multiple bullet points; we could incorporate them as a paragraph.
Let's include a short paragraph about values after the About the role paragraph, maybe as part of same section.
We can add: "Our values: Safety first - Going home safe and well: We champion a safe, diverse and inclusive working environment, understanding the importance of wellbeing in every team. Client focus - Deliver on our promise: We own the quality of deliverables
for prose. We need to decide which sections: About the role, Responsibilities, Requirements, Skills, Pay. Could combine Requirements and Skills? But we have distinct lists: education/experience/knowledge (requirements) and technical proficiencies + soft skills (skills). Might be okay to split. We must not create sections with filler like "commensurate with experience". We have real content. Now produce HTML:
About the role
At Mace, our purpose is to redefine the boundaries of ambition. We believe in creating places that are responsible, bringing transformative impact to our people, communities, and societies across the globe. To learn more about our purpose, culture, and priorities, visit our strategy site. Within our consult business we harness our unique combination of leading-edge practical expertise and project delivery consultancy to unlock the potential in every project. The Project Mace, as part of MPA delivery partner joint venture of Mace-Parsons-Arcadis, have been selected as the Gateway Development Commissions partners of choice to support the GDC across the Gateway Program in New York, inclusive of the Hudson Tunnel Project. The busiest rail connection between New York, New Jersey, and the Northeast Corridor, the Hudson Tunnel Project will improve capacity, reliability, and resiliency of commuter and intercity rail transit serving 800,000 daily passengers from Washington, D.C. to New York and New England. A milestone project supported by the bipartisan Infrastructure Investment and Jobs Act (IIJA), the project is slated to receive nearly $12 billion in federal funding, the largest investment in a mass transit project in modern history.
Responsibilities
- Assist with design reviews, resolve technical issues, and coordinate design change documentation.
- Provide technical support during construction, review contractor submittals, and monitor progress against milestones.
- Facilitate communication among stakeholders, schedule meetings, and assist with project documentation, including drawings and specifications.
- Provide opinions on constructability, means and methods, and the impacts of technical decisions on the overall project, including analysis of critical path schedule impacts and scenario analyses.
- Support the integration and coordination of all HTP Packages, ensuring comprehensive interface management and collaboration among design, construction, and operations teams.
- Assist with programmatic oversight and management of project controls functions, including schedule, cost, change, risk, and document management.
- Update project controls procedures, workflow processes, and tools as requested.
- Prepare and submit monthly and quarterly project reports, including safety, quality, environmental, and milestone status updates.
- Maintain a “lessons learned” register and master “issues log” for the HTP.
- Support BIM technology implementation, including development and maintenance of digital models, coordination with designers, and integration of project information.
- Assist with configuration and implementation of project management information systems (PMIS) and other technology tools.
Requirements
- Bachelor’s degree in Civil Engineering or related field.
- 3–7 years of experience in civil engineering, preferably on large infrastructure or transportation projects.
- Roadway engineering skills such as geometric design, grading, access management, permitting, utilities, stormwater management, roadway drainage design, 3D roadway modeling, traffic/accident analysis and traffic control and staging plans.
- Familiarity with project controls, scheduling, cost management, and risk management.
- Knowledge of federal, state, and local regulations relevant to major capital projects (NJDOT, NJDEP, NEPA, USACE, County or Municipal agencies, etc.).
- Experience with quality assurance, construction monitoring, and technical documentation.
Skills
- Proficiency with BIM, AutoCAD, MicroStation, PMIS, and Microsoft Office Suite.
- Strong communication, organizational, and problem-solving skills.
- Ability to work collaboratively with multidisciplinary teams and external stakeholders.
Pay
Note: The estimated starting salary for this position is $130k. Starting salary may vary based on permissible, non-discriminatory factors such as experience, skills and qualifications.
We should not include any extra sections like Benefits, Schedule. Check for any duplicated lines: none. Make sure we didn't include any boilerplate like values statements. We omitted them. That's okay; we removed them as they might be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values statements are not those, but we removed them; is that allowed? We must preserve ALL substantive information. Are values statements substantive? They are generic corporate values; might be considered boilerplate but not explicitly prohibited. However the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Values are not listed. So we should keep them if they are substantive. But they are generic; still they are part of posting. The instruction says "Preserve ALL substantive information". If we remove them, we might be removing substantive info? It's arguable. Safer to include them maybe in About the role as a paragraph. But we already have a long paragraph; we could append a sentence about values. However the values list includes multiple bullet points; we could incorporate them as a paragraph. Let's include a short paragraph about values after the About the role paragraph, maybe as part of same section. We can add: "Our values: Safety first - Going home safe and well: We champion a safe, diverse and inclusive working environment, understanding the importance of wellbeing in every team. Client focus - Deliver on our promise: We own the quality of deliverables