Field Engineer (night shift) - Data Center Construction
Sundt Construction · Temple, TX · 4 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Notice to External Search Firms" etc. Also remove "Equal Opportunity Employer Statement" etc. Also remove "Benefit list:" maybe we can include Benefits section with the list. Pay: we have "Market Competitive Salary (paid weekly)" and maybe "Bonus Eligibility based on company, group, and individual performance". That's pay info. Schedule: not mentioned. So we should not include Schedule heading if no specific content. Benefits: we have list of benefits. Qualifications: maybe "Minimum Job Requirements" includes ability to assume responsibility, etc. Also "Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience." Also "Microsoft Office Suite proficiency." Also "Physical Requirements" maybe part of Requirements? Could be separate but we can include under Requirements. Qualifications maybe same as Requirements? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
About the role: Could be Job Summary? The job summary: "Assists the Project Engineer with being the technical source of information for the project..." That's about the role. So we can put that in About the role.
Responsibilities: The "Key Responsibilities" bullet list.
Requirements: Minimum Job Requirements (ability to assume responsibility, etc.) plus Physical Requirements? Could be separate but we can include under Requirements.
Qualifications: maybe the education requirement and experience? But that overlaps. Could treat Qualifications as education/experience, Skills as Microsoft Office proficiency, etc. But we need to avoid duplication. Let's parse:
- Minimum Job Requirements: Ability to assume responsibility, interface and communicate with others is essential. Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience. Microsoft Office Suite proficiency. Note: Job Description is subject to change...
- Physical Requirements: list of physical demands.
Thus we could have Requirements: Minimum Job Requirements + Physical Requirements.
Qualifications: maybe not needed separately; but we could include education/experience as Qualifications. However we already used that in Requirements. To avoid thin sections, we could combine. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including minimum job reqs and physical), Benefits, Pay. Possibly Skills: Microsoft Office proficiency could be under Requirements or Skills. But we already have Microsoft Office in Minimum Job Requirements. Could move to Skills. But we need to avoid duplication. Let's decide:
Sections:
- About the role: Job Summary paragraph.
- Responsibilities: Key Responsibilities (list).
- Requirements: Minimum Job Requirements (ability to assume responsibility, communication, etc.) plus Physical Requirements.
- Skills: Microsoft Office Suite proficiency.
- Benefits: list of benefits.
- Pay: Market Competitive Salary (paid weekly), Bonus Eligibility based on company, group, and individual performance.
We should not include Schedule.
We must not include headings with filler text. Ensure we preserve all substantive info. Let's extract details.
Job Summary paragraph: "Assists the Project Engineer with being the technical source of information for the project. Responds to questions about drawings, specifications, shop drawings, and change orders and have responsibility for assisting in writing change orders, RFl's, meeting minutes, and reviewing Submittals. Maintains an effective and professional working relationship with owners, architects, engineers, subcontractors, and suppliers. 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."
We need to keep that exactly? Preserve all substantive information; do not invent or summarize away detail. We can keep as is, maybe slight punctuation.
Responsibilities list: Let's extract bullet points from "Key Responsibilities". The text after that is a long sentence with many items separated by periods. We need to convert to
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Notice to External Search Firms" etc. Also remove "Equal Opportunity Employer Statement" etc. Also remove "Benefit list:" maybe we can include Benefits section with the list. Pay: we have "Market Competitive Salary (paid weekly)" and maybe "Bonus Eligibility based on company, group, and individual performance". That's pay info. Schedule: not mentioned. So we should not include Schedule heading if no specific content. Benefits: we have list of benefits. Qualifications: maybe "Minimum Job Requirements" includes ability to assume responsibility, etc. Also "Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience." Also "Microsoft Office Suite proficiency." Also "Physical Requirements" maybe part of Requirements? Could be separate but we can include under Requirements. Qualifications maybe same as Requirements? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
About the role: Could be Job Summary? The job summary: "Assists the Project Engineer with being the technical source of information for the project..." That's about the role. So we can put that in About the role.
Responsibilities: The "Key Responsibilities" bullet list.
Requirements: Minimum Job Requirements (ability to assume responsibility, etc.) plus Physical Requirements? Could be separate but we can include under Requirements.
Qualifications: maybe the education requirement and experience? But that overlaps. Could treat Qualifications as education/experience, Skills as Microsoft Office proficiency, etc. But we need to avoid duplication. Let's parse:
- Minimum Job Requirements: Ability to assume responsibility, interface and communicate with others is essential. Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience. Microsoft Office Suite proficiency. Note: Job Description is subject to change...
- Physical Requirements: list of physical demands.
Thus we could have Requirements: Minimum Job Requirements + Physical Requirements.
Qualifications: maybe not needed separately; but we could include education/experience as Qualifications. However we already used that in Requirements. To avoid thin sections, we could combine. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including minimum job reqs and physical), Benefits, Pay. Possibly Skills: Microsoft Office proficiency could be under Requirements or Skills. But we already have Microsoft Office in Minimum Job Requirements. Could move to Skills. But we need to avoid duplication. Let's decide:
Sections:
- About the role: Job Summary paragraph.
- Responsibilities: Key Responsibilities (list).
- Requirements: Minimum Job Requirements (ability to assume responsibility, communication, etc.) plus Physical Requirements.
- Skills: Microsoft Office Suite proficiency.
- Benefits: list of benefits.
- Pay: Market Competitive Salary (paid weekly), Bonus Eligibility based on company, group, and individual performance.
We should not include Schedule.
We must not include headings with filler text. Ensure we preserve all substantive info. Let's extract details.
Job Summary paragraph: "Assists the Project Engineer with being the technical source of information for the project. Responds to questions about drawings, specifications, shop drawings, and change orders and have responsibility for assisting in writing change orders, RFl's, meeting minutes, and reviewing Submittals. Maintains an effective and professional working relationship with owners, architects, engineers, subcontractors, and suppliers. 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."
We need to keep that exactly? Preserve all substantive information; do not invent or summarize away detail. We can keep as is, maybe slight punctuation.
Responsibilities list: Let's extract bullet points from "Key Responsibilities". The text after that is a long sentence with many items separated by periods. We need to convert to - items. We must preserve all substantive info; we can split by sentences.
Let's copy the responsibilities paragraph:
"Assists Project Engineer in developing and maintaining as-built drawings and other work tasks and assists with or reviews and processes submittals, change orders, RFl's, and budget forecasting. Ensures the timely and appropriate generation, collection, distribution, storage, retrieval and ultimate disposition of meeting agendas, RFl's and daily reports. Demonstrates an understanding of the project management plan (PMP) and is involved in support and execution of the plan. Demonstrates a thorough understanding of the change management process and performs project scope activities and supports the project team to ensure the work needed to complete the project successfully. Ensures the administration of the project quality management plan and demonstrates and reinforces a culture of safety throughout the project. May assist in the calculation of daily production rates and unit costs for self-performed work. Participates in risk management including identification, analysis, response planning and monitoring and control on a project and demonstrates competency in understanding the environmental control processes for the project and takes corrective actions when necessary. May be responsible for overseeing/managing the BIM (Building Information Modeling) Coordination between Subcontractors and Designers. May be responsible for the documentation and submittal for the LEED (Leadership in Energy and Environmental Design) Certification of a building and for creating and updating Digital Record Drawings (ORD). May provide lines, grades and layout as required for the project while maintaining an organized logbook. May provide the following weekly quantities: maintains accurate quantity logs and reports quantities in compliance with the cost control manual. Completed logs are to be filed with the project files. Perform elements of the processes involved in budgeting and controlling costs so that the project can be completed within the approved budget. Demonstrates business acumen within area of responsibility. (Not all Field Engineers track quantities) Provides support to superintendents required for the execution of the work and assists in the resolution of field problems as necessary."
We need to split into list items. Each sentence becomes an
- . Ensure we keep parentheses content.
Now Requirements: Minimum Job Requirements: "Ability to assume responsibility, interface and communicate with others is essential. Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience. Microsoft Office Suite (Outlook, Word, Excel, PowerPoint, etc.) proficiency. Note: Job Description is subject to change at any time and may include other duties as assigned."
Physical Requirements: list: "Ability to wear personal protective equipment is required (including but not limited to; steel toed shoes, gloves, safety glasses, hearing protection, hardhat, vest, etc.) May reach above shoulder heights and below the waist on a frequent basis May stoop, kneel, or bend, on an occasional basis May use telephone, computer system, email, or other electronic devices on a limited basis to communicate with internal and external customers or vendors Must be able to comply with all safety standards and procedures Occasionally will climb stairs, ladders, etc. Required to use hands to grasp, lift, handle, carry or feel objects on a frequent basis Will interact with people frequently during a shift/workday Will lift, push or pull objects on an occasional basis Will sit, stand or walk short distances for up to the entire duration of a shift/workday."
We need to split into list items as well. Also note there is a "Safety Level Note:" after that, but that's boilerplate? It's about Safety-Sensitive designation. Might be considered boilerplate? It's not EEO but it's a note about safety-sensitive jobs. Could be considered substantive? It describes safety level. Might be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Safety Level Note is not exactly those but could be considered legal? It's about safety-sensitive designation. Might be considered boilerplate but it's part of job description. I'd keep it as part of Requirements maybe. However it's a note about Safety-Sensitive designation. Might be considered boilerplate but it's specific to the job. I'd include it as a paragraph under Requirements.
But we must not include duplicated lines. There's no duplication.
Now Skills: Microsoft Office Suite proficiency (maybe we already included in Minimum Job Requirements). To avoid duplication, we could move Microsoft Office to Skills and remove from Minimum Job Requirements. But then we lose that info from Requirements. Better to keep Microsoft Office in Skills and remove from Minimum Job Requirements? But Minimum Job Requirements includes that; we could keep it there and not have Skills section. However we need to decide if we want a Skills section. The instruction: Prefer a few substantive sections over many thin ones. If we have Microsoft Office as only skill, that's thin. Could combine into Requirements. So we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements (including Minimum Job Requirements, Physical Requirements, Safety Level Note), Benefits, Pay.
Now Benefits: list from "Benefit list:" after Equal Opportunity Employer Statement. The list:
- 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 need to preserve all. We'll put each as
- .
Pay: we have Market Competitive Salary (paid weekly) and Bonus Eligibility based on company, group, and individual performance. However those are also in Benefits list. To avoid duplication, we should not duplicate. The Benefits list already includes those. So we could either not have a separate Pay section, or we could keep Pay section with those details and remove from Benefits. But the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we remove from Benefits, we lose that info unless we keep it elsewhere. We could keep Pay section with those two items, and Benefits section with the rest (excluding those two). That avoids duplication. Let's do that.
Thus Benefits list will exclude Market Competitive Salary and Bonus Eligibility.
Now Pay section:
Pay
with - Market Competitive Salary (paid weekly)
- Bonus Eligibility based on company, group, and individual performance
Now Benefits section: remaining items.
Now we need to ensure we don't include any boilerplate like "Equal Opportunity Employer Statement", "Notice to External Search Firms", etc. We'll omit those.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: About the role
...
Responsibilities: Responsibilities
- ...
...
Requirements: Requirements
- Ability to assume responsibility, interface and communicate with others is essential.
- Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience.
- Microsoft Office Suite (Outlook, Word, Excel, PowerPoint, etc.) proficiency.
- Note: Job Description is subject to change at any time and may include other duties as assigned.
- Ability to wear personal protective equipment is required (including but not limited to; steel toed shoes, gloves, safety glasses, hearing protection, hardhat, vest, etc.)
- May reach above shoulder heights and below the waist on a frequent basis
Pay
with- Market Competitive Salary (paid weekly)
- Bonus Eligibility based on company, group, and individual performance
About the role
...
Responsibilities:Responsibilities
- ... ...
Requirements
- Ability to assume responsibility, interface and communicate with others is essential.
- Entry-level position that normally requires a four-year construction-related degree or equivalent technical/field experience.
- Microsoft Office Suite (Outlook, Word, Excel, PowerPoint, etc.) proficiency.
- Note: Job Description is subject to change at any time and may include other duties as assigned.
- Ability to wear personal protective equipment is required (including but not limited to; steel toed shoes, gloves, safety glasses, hearing protection, hardhat, vest, etc.)
- May reach above shoulder heights and below the waist on a frequent basis
Similar jobs
Project Engineer (night shift) - Data Center Construction
Engineeringapply on eewl.fa.us6.oraclecloud.com
Field Superintendent (night shift) - Data Center Construction
Manufacturingapply on eewl.fa.us6.oraclecloud.com
Field Engineer - Data Center Construction
Engineeringapply on eewl.fa.us6.oraclecloud.com
Field Engineer - Data Center Construction
Engineeringapply on eewl.fa.us6.oraclecloud.com
Field Engineer - Data Center Construction
Engineeringapply on eewl.fa.us6.oraclecloud.com
Building Engineer, Data Centers (Night Shift)
Information Technologyapply on jll.wd1.myworkdayjobs.com