Project Engineer (MEP) - Data Center Construction
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; not invent or summarize away detail. So we need to keep details like "Four-year construction-related degree or equivalent technical training and related experience, plus a minimum of three to four years of similar construction engineering experience." etc.
We need to format lists appropriately.
Let's extract content.
Intro/about the role: "As a 100% employee-owned contractor, when you work at Sundt, you’re not just hiring on at a company, you’re joining a culture. Because everyone at Sundt is part owner, you’ll join a team of people who are deeply invested in their work. From apprentices to managers, we’re passionate about the details and deliberate in everything we do. At Sundt we focus on building long-term prosperity for our clients, communities, and employee-owners. We offer competitive pay, industry-leading benefits including a 401k and employee stock ownership plan, incentive programs for craft and administrative employees as well as training that focuses on your personal and professional growth. We’re driven by skill, grit and purpose. Join us as we strive to be the most skilled builder in America."
That's substantive.
Job Summary: "Project Engineer is the technical source of information for the project and should have a thorough knowledge of the construction documents, subcontracts, and purchase orders. Responds to questions about drawings, specifications, shop drawings, and change orders. Maintains an effective and professional working relationship with owners, architects, engineers, subcontractors, and suppliers. May assist with the supervision and/or training of Field Engineers. This position includes three 'steps' (I, II, and Senior), which provide for a progression of skill and experience. Step I is the entry level for individuals with a minimum of experience in this position."
Key Responsibilities: list items (each sentence). We'll need to put each as
- .
Minimum Job Requirements: list items (maybe each sentence). We'll put as
- .
Physical Requirements: list items (each sentence). We'll put as
- .
Benefits: list items from "Benefit list:" etc. We'll extract each benefit line.
Pay: "Market Competitive Salary (paid weekly)" and "Bonus Eligibility based on company, group, and individual performance". Could be two items.
We must not include duplicated content like About Us duplicate, EEO statements, NOTICE TO EXTERNAL SEARCH FIRMS.
Let's craft HTML.
Structure:
About the role
...intro...
Job Summary
...summary...
Responsibilities
- ...
...
Requirements
- ...
...
Physical Requirements
- ...
...
Benefits
- ...
...
Pay
- Market Competitive Salary (paid weekly)
- Bonus Eligibility based on company, group, and individual performance
We need to ensure we don't include any heading with empty content.
Check that we haven't missed any substantive info like "incentive programs for craft and administrative employees as well as training that focuses on your personal and professional growth." That's in intro; we kept.
Also "employee stock ownership plan" appears in intro and benefits; we keep both.
Now ensure we removed duplicated lines: The About Us duplicate is same as intro; we only include once.
Now check for any other substantive content: "Note: Job Description is subject to change at any time and may include other duties as assigned." That's a note; maybe we should keep? It's substantive but maybe considered boilerplate? It's a note about job description changes. Could be considered meta. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not exactly those categories; it's about job description being subject to change. Might be considered boilerplate but it's not explicitly listed. Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This note is substantive (though generic). I'd keep it maybe as a paragraph under Responsibilities or at end. But we have no section for "Notes". Could add a after Responsibilities? But we must not create a heading without real content. Could add a
under Responsibilities after list? Might be okay. However, the note is about the job description; maybe it's considered boilerplate. Many job posts have that line; but it's not explicitly listed to remove. I'd keep it as a
after Responsibilities, maybe under a heading "Additional Information"? Not in allowed headings. Could just add a
after Responsibilities without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add a
without heading. However, to be safe, we could incorporate it into Responsibilities as a final
- ? But it's not a responsibility. Could add a
after Responsibilities list without a heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose." It doesn't say we cannot have
without heading. So we can add a
after Responsibilities for the note.
Similarly, there may be other notes like "May assist with the supervision and/or training of Field Engineers." already in summary.
Let's include note as a
after Responsibilities.
Now check for any other substantive content: "From apprentices to managers, we’re passionate about the details and deliberate in everything we do." Already in intro.
Now ensure we didn't include any boilerplate like "Equal Opportunity Employer Statement:" etc. We removed those.
Now check for duplicate benefit list: we have benefits extracted from the Benefit list lines. Let's list them:
- Market Competitive Salary (paid weekly)
- Bonus Eligibility based on company, group, and individual performance
- Employee Stock Ownership Plan & 401K
- Industry Leading Health Coverage
- Starting Your First Day
- Flexible Time Off (FTO)
- Medical, Health Savings, and Wellness credits
- Flexible Spending Accounts
- Employee Assistance Program
- Workplace Wellness Programs
- Mental Health Program
- Life and Disability Insurance
- Employee-Owner Perks
- Educational Assistance
- Sundt Foundation - Charitable Employee-Owner's program
We should keep each as separate
- . Ensure we don't duplicate "Market Competitive Salary (paid weekly)" also in Pay section; we have it also in Benefits list. Actually the benefit list includes "Market Competitive Salary (paid weekly)" and "Bonus Eligibility based on company, group, and individual performance". So we could either put them under Benefits only, and not have separate Pay section. But the instruction says to create Pay section only if posting actually states them. It does state them, but they are also in Benefits list. However, we could still have a Pay section; but that would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is not inventing but repeating. Might be okay but could be considered redundant. Better to avoid duplication: we could keep Pay section and not repeat in Benefits, or keep Benefits and not repeat in Pay. Since the benefit list includes them, we could keep them in Benefits and omit Pay section. However, the instruction says "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits may be thin. So better to combine: keep Benefits section with all benefit items, and not have separate Pay section. But we need to ensure we don't lose the nuance that salary is paid weekly etc. It's already in the benefit item.
Thus we will not create a Pay section.
Now check for Schedule: none.
Now check for Skills: none.
Now check for Qualifications: we have Requirements; we could rename Requirements to Qualifications? But we have both Requirements and Qualifications headings allowed. We could use Requirements for the minimum job requirements, and Qualifications for maybe something else? There's no separate qualifications. So we will just have Requirements.
Now check for "About the role" heading: we used that for intro.
Now check for "Job Summary": we used that.
Now check for "Responsibilities": we used that.
Now check for "Requirements": we used that.
Now check for "Physical Requirements": we used that.
Now check for "Benefits": we used that.
Now we need to ensure we didn't include any heading with empty content.
Now let's draft the HTML.
We need to be careful to escape any HTML special characters? Not needed.
Now produce final answer.
Let's write:
About the role
As a 100% employee-owned contractor, when you work at Sundt, you’re not just hiring on at a company, you’re joining a culture. Because everyone at Sundt is part owner, you’ll join a team of people who are deeply invested in their work. From apprentices to managers, we’re passionate about the details and deliberate in everything we do. At Sundt we focus on building long-term prosperity for our clients, communities, and employee-owners. We offer competitive pay, industry-leading benefits including a 401k and employee stock ownership plan, incentive programs for craft and administrative employees as well as training that focuses on your personal and professional growth. We’re driven by skill, grit and purpose. Join us as we strive to be the most skilled builder in America.
Job Summary
Project Engineer is the technical source of information for the project and should
for prose. We must preserve all substantive information; not invent or summarize away detail. So we need to keep details like "Four-year construction-related degree or equivalent technical training and related experience, plus a minimum of three to four years of similar construction engineering experience." etc. We need to format lists appropriately. Let's extract content. Intro/about the role: "As a 100% employee-owned contractor, when you work at Sundt, you’re not just hiring on at a company, you’re joining a culture. Because everyone at Sundt is part owner, you’ll join a team of people who are deeply invested in their work. From apprentices to managers, we’re passionate about the details and deliberate in everything we do. At Sundt we focus on building long-term prosperity for our clients, communities, and employee-owners. We offer competitive pay, industry-leading benefits including a 401k and employee stock ownership plan, incentive programs for craft and administrative employees as well as training that focuses on your personal and professional growth. We’re driven by skill, grit and purpose. Join us as we strive to be the most skilled builder in America." That's substantive. Job Summary: "Project Engineer is the technical source of information for the project and should have a thorough knowledge of the construction documents, subcontracts, and purchase orders. Responds to questions about drawings, specifications, shop drawings, and change orders. Maintains an effective and professional working relationship with owners, architects, engineers, subcontractors, and suppliers. May assist with the supervision and/or training of Field Engineers. This position includes three 'steps' (I, II, and Senior), which provide for a progression of skill and experience. Step I is the entry level for individuals with a minimum of experience in this position." Key Responsibilities: list items (each sentence). We'll need to put each as
About the role
...intro...
Job Summary
...summary...
Responsibilities
- ... ...
Requirements
- ... ...
Physical Requirements
- ... ...
Benefits
- ... ...
Pay
- Market Competitive Salary (paid weekly)
- Bonus Eligibility based on company, group, and individual performance
after Responsibilities? But we must not create a heading without real content. Could add a
under Responsibilities after list? Might be okay. However, the note is about the job description; maybe it's considered boilerplate. Many job posts have that line; but it's not explicitly listed to remove. I'd keep it as a
after Responsibilities, maybe under a heading "Additional Information"? Not in allowed headings. Could just add a
after Responsibilities without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add a
without heading. However, to be safe, we could incorporate it into Responsibilities as a final
after Responsibilities list without a heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose." It doesn't say we cannot have
without heading. So we can add a
after Responsibilities for the note.
Similarly, there may be other notes like "May assist with the supervision and/or training of Field Engineers." already in summary.
Let's include note as a
after Responsibilities.
Now check for any other substantive content: "From apprentices to managers, we’re passionate about the details and deliberate in everything we do." Already in intro.
Now ensure we didn't include any boilerplate like "Equal Opportunity Employer Statement:" etc. We removed those.
Now check for duplicate benefit list: we have benefits extracted from the Benefit list lines. Let's list them:
- Market Competitive Salary (paid weekly)
- Bonus Eligibility based on company, group, and individual performance
- Employee Stock Ownership Plan & 401K
- Industry Leading Health Coverage
- Starting Your First Day
- Flexible Time Off (FTO)
- Medical, Health Savings, and Wellness credits
- Flexible Spending Accounts
- Employee Assistance Program
- Workplace Wellness Programs
- Mental Health Program
- Life and Disability Insurance
- Employee-Owner Perks
- Educational Assistance
- Sundt Foundation - Charitable Employee-Owner's program
We should keep each as separate
- . Ensure we don't duplicate "Market Competitive Salary (paid weekly)" also in Pay section; we have it also in Benefits list. Actually the benefit list includes "Market Competitive Salary (paid weekly)" and "Bonus Eligibility based on company, group, and individual performance". So we could either put them under Benefits only, and not have separate Pay section. But the instruction says to create Pay section only if posting actually states them. It does state them, but they are also in Benefits list. However, we could still have a Pay section; but that would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is not inventing but repeating. Might be okay but could be considered redundant. Better to avoid duplication: we could keep Pay section and not repeat in Benefits, or keep Benefits and not repeat in Pay. Since the benefit list includes them, we could keep them in Benefits and omit Pay section. However, the instruction says "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits may be thin. So better to combine: keep Benefits section with all benefit items, and not have separate Pay section. But we need to ensure we don't lose the nuance that salary is paid weekly etc. It's already in the benefit item.
Thus we will not create a Pay section.
Now check for Schedule: none.
Now check for Skills: none.
Now check for Qualifications: we have Requirements; we could rename Requirements to Qualifications? But we have both Requirements and Qualifications headings allowed. We could use Requirements for the minimum job requirements, and Qualifications for maybe something else? There's no separate qualifications. So we will just have Requirements.
Now check for "About the role" heading: we used that for intro.
Now check for "Job Summary": we used that.
Now check for "Responsibilities": we used that.
Now check for "Requirements": we used that.
Now check for "Physical Requirements": we used that.
Now check for "Benefits": we used that.
Now we need to ensure we didn't include any heading with empty content.
Now let's draft the HTML.
We need to be careful to escape any HTML special characters? Not needed.
Now produce final answer.
Let's write:
About the role
As a 100% employee-owned contractor, when you work at Sundt, you’re not just hiring on at a company, you’re joining a culture. Because everyone at Sundt is part owner, you’ll join a team of people who are deeply invested in their work. From apprentices to managers, we’re passionate about the details and deliberate in everything we do. At Sundt we focus on building long-term prosperity for our clients, communities, and employee-owners. We offer competitive pay, industry-leading benefits including a 401k and employee stock ownership plan, incentive programs for craft and administrative employees as well as training that focuses on your personal and professional growth. We’re driven by skill, grit and purpose. Join us as we strive to be the most skilled builder in America.
Job Summary
Project Engineer is the technical source of information for the project and should
for prose." It doesn't say we cannot have
without heading. So we can add a
after Responsibilities for the note. Similarly, there may be other notes like "May assist with the supervision and/or training of Field Engineers." already in summary. Let's include note as a
after Responsibilities. Now check for any other substantive content: "From apprentices to managers, we’re passionate about the details and deliberate in everything we do." Already in intro. Now ensure we didn't include any boilerplate like "Equal Opportunity Employer Statement:" etc. We removed those. Now check for duplicate benefit list: we have benefits extracted from the Benefit list lines. Let's list them: - Market Competitive Salary (paid weekly) - Bonus Eligibility based on company, group, and individual performance - Employee Stock Ownership Plan & 401K - Industry Leading Health Coverage - Starting Your First Day - Flexible Time Off (FTO) - Medical, Health Savings, and Wellness credits - Flexible Spending Accounts - Employee Assistance Program - Workplace Wellness Programs - Mental Health Program - Life and Disability Insurance - Employee-Owner Perks - Educational Assistance - Sundt Foundation - Charitable Employee-Owner's program We should keep each as separate
About the role
As a 100% employee-owned contractor, when you work at Sundt, you’re not just hiring on at a company, you’re joining a culture. Because everyone at Sundt is part owner, you’ll join a team of people who are deeply invested in their work. From apprentices to managers, we’re passionate about the details and deliberate in everything we do. At Sundt we focus on building long-term prosperity for our clients, communities, and employee-owners. We offer competitive pay, industry-leading benefits including a 401k and employee stock ownership plan, incentive programs for craft and administrative employees as well as training that focuses on your personal and professional growth. We’re driven by skill, grit and purpose. Join us as we strive to be the most skilled builder in America.
Job Summary
Project Engineer is the technical source of information for the project and should