Civil Foreman
Optimized Process Designs LLC · Baytown, TX · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, responsibilities, qualifications, etc. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to preserve all substantive info, no boilerplate.
We need to decide which sections to include.
Content:
- Intro: "Your Job The jobsite located in Mont Belvieu, TX has an opening for a Civil Foreman." That's location and title. Not a heading.
- "Our Team Optimized Process Designs, LLC (OPD) is an engineering/construction company..." This is about the company. Could be "About the role"? Actually "About the role" maybe not; but we could use "About the company" but not in list. The allowed headings are limited to those given. We could use "About the role" to include description of role and company? The instruction: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to preserve all substantive info, no boilerplate.
We need to decide which sections to include.
Content:
- Intro: "Your Job The jobsite located in Mont Belvieu, TX has an opening for a Civil Foreman." That's location and title. Not a heading.
- "Our Team Optimized Process Designs, LLC (OPD) is an engineering/construction company..." This is about the company. Could be "About the role"? Actually "About the role" maybe not; but we could use "About the company" but not in list. The allowed headings are limited to those given. We could use "About the role" to include description of role and company? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings. We need to map content accordingly.
We have:
- Responsibilities: list under "What You Will Do" and "We Expect All Field Employees To". Also some physical demands.
- Requirements/Qualifications: "Who You Are (Basic Qualifications)" and "What Will Put You Ahead" (preferred qualifications). Also some physical demands maybe part of requirements.
- Skills: maybe list of skills like carpentry, tools, etc.
- Benefits: described under "Our Benefits". That's specific content.
- Pay: not provided explicitly; only mention compensation range estimate but not actual numbers. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is not stated (no range). So we should NOT include Pay section.
- Schedule: not explicitly stated; mentions shifts up to 12 hours per day and 7 days per week, travel, etc. That's schedule info. It says "Must be able to work shifts up to 12 hours per day and 7 days per week". That's schedule detail. So we can include Schedule section.
- Skills: we can include a Skills section for technical skills like carpentry, tools, reading drawings, sight level, transit, etc.
- Requirements: maybe combine basic qualifications and physical demands.
We need to avoid duplication.
We must not include boilerplate like EEO, E-Verify, etc.
We must not include application instructions.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We need to preserve all substantive info.
Let's extract substantive info:
Location: Mont Belvieu, TX.
Company description: Optimized Process Designs, LLC (OPD) engineering/construction, headquartered Katy, TX, expertise in natural gas, NGL, petrochemical; part of Koch Engineered Solutions (KES); incorporated 1980; reputation for honesty, integrity; able to supply construction services and engineering/procurement; one-stop shop; industry experience, flexibility, personal attention; tight knit, highly productive team.
Responsibilities (What You Will Do):
- Strong knowledge of carpentry, tools, procedures, and best practices
- Ability to lead crews
- Must be willing and able to conduct morning production meeting with crews to discuss daily plans and concerns
- Assign job tasks to each crew member and ensure that each member is properly trained
- Must be able to coordinate work according to priorities and plans
- Being a safety role model for the team
- Enforcing OPD and client specific safety policies and procedures on the jobsite
- Anticipate and recognize potential safety and environmental concerns and report them to the OPD Superintendent
- Communicate and coordinate with OPD Superintendent, Logistics Manager, Construction Manager as required for material requirements and to schedule concrete pours and order rebar for delivery
- Verify forms and concrete are set within client specifications
- Must be competent with excavations, trenching, and soil
- Must be able to plan equipment, soil treatment, and safety considerations for all planned civil work
- Must be able to lead by example and with respect
- Must contribute and maintain a clean job site
- Must be able to use a computer to write daily reports, employee discipline, JSAs, and use e-mail
We Expect All Field Employees To:
- Actively participate in a strong safety culture
- Recognize safety hazards and risks
- Participate in onsite safety meetings
- Follow OPD and client safety policies and procedures
- Be aware of changing conditions on an active jobsite
- Be on time to the jobsite each day ready for work
- Display a positive attitude and be able to work in a team environment
Physical Demands:
- Capable of working in outdoor weather and environmental conditions including extreme heat and humidity, extreme cold, and high elevations.
- Lifting and carrying awkward objects up to 60 lbs
- Standing for extended periods of time up to 11 hours per day.
- Breaks are given in 2.5 hour intervals
- Moving the entire body.
- Considerable use of arms, legs, climbing, lifting, balancing, walking, stooping, crawling, twisting, reaching, and bending on a regular basis.
- Use hands to handle, control, and feel objects and/or tools.
Who You Are (Basic Qualifications):
- At least 2 years of experience as a civil foreman
- Must be able to read and understand civil, structural, and pipe drawings
- Must be able to use a sight level and transit to determine coordinates and elevations
- Previous experience in a gas plant construction environment
- Previous experience leading teams of 10-30 people
- Must be willing to advance safety culture
- Previous experience communicating effectively across crafts: civil, pipe, and structural
- Travel is a must with extended periods away from home in remote areas at times.
- Must be able to perform a pre-employment drug screen and background check
- Must be willing and able to attend and/or lead employee safety meetings
- Must be able to work shifts up to 12 hours per day and 7 days per week
- Must be able to meet all physical demands of the job
What Will Put You Ahead (Preferred):
- Three or more years of previous experience as a foreman
- Fully competent with excavation, trenching, soil jobs and safety considerations
- Consistent progression into field leadership
- Past experience working in multiple crafts: pipe, civil, structural
Koch philosophy statements (entrepreneur, hiring philosophy, diversity, military ready, second chance) - maybe not needed as they are boilerplate? They are substantive about company culture but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Koch philosophy statements might be considered boilerplate? They are not legal but maybe still generic. However they are part of "Who We Are" and "Our Benefits". The "Our Benefits" section is substantive: medical, dental, vision, flexible spending and health savings accounts, life insurance, ADD, disability, retirement, paid vacation/time off, educational assistance, may also include infertility assistance, paid parental leave and adoption assistance. Specific eligibility criteria set by SPD, policy or guideline and benefits may vary by geographic region.
We should include Benefits section.
We should not include "Hiring Philosophy" etc unless they are specific; they are somewhat generic but could be considered part of "About the role"? Probably not needed.
We need to decide sections:
- About the role: could include company description and location? Or we could skip About the role and go straight to Responsibilities, Requirements, Skills, Benefits, Schedule.
But we need to use headings only when we have real specific content. We have content for Responsibilities, Requirements (basic qualifications), Skills (maybe separate), Benefits, Schedule. Also maybe "Qualifications" heading for basic and preferred? The instruction list includes Qualifications as a possible heading. We could put basic qualifications under Qualifications, and preferred under Skills? Or we could combine.
Better: Use headings: Responsibilities, Requirements, Skills, Benefits, Schedule.
We need to include location maybe in a paragraph before headings.
Let's craft:
Location: Mont Belvieu, TX.
Then