I&E Senior Designer

We need to output HTML fragment with sections only if real content. No markdown fences. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Let's parse the posting. First paragraph: "Your Job Optimized Process Designs (OPD), a Koch Engineered Solutions company, is looking for Senior I&E Designer who thrives on ownership, collaboration, and delivering high-impact projects. This is an opportunity to play a critical role in shaping I&E design solutions from concept through construction while leading and developing a talented design team. This role will sit at our headquarters in Katy, TX, Monday - Friday. This role is not eligible for visa sponsorship." That's about the role. So we can have

About the role

with a paragraph containing that info. Next: "Our Team Optimized Process Designs is an engineering, procurement, and construction (EPC) firm executing on complex energy and infrastructure projects across North America. Their focus and expertise is in the natural gas, natural gas liquids, and petrochemical industries. OPD is part of the larger Koch organization which provides a variety of capabilities across many industries. OPD is known for technical excellence, disciplined project execution, and a culture that empowers engineers to take ownership and create long-term value." That could also be about the role or company description. Could be part of About the role or maybe a separate "About the company". But we only have allowed headings; we could put this under About the role as well, or maybe we could create a separate section like "About the company" but not in list. Since only allowed headings are given, we should stick to them. Could incorporate into About the role. Then "What You Will Do" list: bullet points. That's Responsibilities. Then "Who You Are (Basic Qualifications)" list: that's Requirements or Qualifications. We have both Requirements and Qualifications headings allowed. We need to decide which to use. The posting has "Who You Are (Basic Qualifications)" which is basic qualifications. Then "What Will Put You Ahead" which is preferred qualifications. Then later "At Koch companies, we are entrepreneurs..." that's more about culture, maybe not needed. Then "Hiring Philosophy" etc. Then "Who We Are" etc. Then "Our Benefits". Then "Equal Opportunities" etc (boilerplate to remove). Also compensation note: "Any compensation range provided for a role is an estimate..." That's about Pay but no actual range given. Since no specific pay info, we should NOT create Pay section because we only create if posting actually states them. It mentions compensation philosophy but no range. So we should not include Pay. Schedule: The posting says "This role will sit at our headquarters in Katy, TX, Monday - Friday." That's schedule info (Monday-Friday). So we can create a Schedule section with that. Benefits: There's a section "Our Benefits" with description. So we can create Benefits section. Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Skills maybe from "Experience using AutoCAD or similar design software" etc. Could put skills under Skills. But we could also combine Requirements and Qualifications. However we need to avoid thin sections. Let's see what we have: - About the role: paragraph(s) describing role, location, schedule? Actually schedule we will separate. - Responsibilities: list of duties under "What You Will Do". - Requirements (basic qualifications): list under "Who You Are (Basic Qualifications)". - Qualifications (preferred): list under "What Will Put You Ahead". - Skills: maybe we can extract specific skills like AutoCAD, coordination, etc. But those are already in requirements/qualifications. Could create Skills section for technical skills: AutoCAD, instrumentation, electrical, controls, etc. But we might be duplicating. Better to not create Skills if content is thin; we can incorporate into Requirements/Qualifications. However we have both Requirements and Qualifications headings allowed; we can use both. - Benefits: we have description. - Schedule: Monday-Friday. - Pay: none specific, so omit. Now we need to ensure we don't include boilerplate like EEO, visa sponsorship note? The visa sponsorship note is part of About the role maybe; we can keep it as it's substantive (not eligible for visa sponsorship). That's okay. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. Also remove "If you have questions, please speak to your recruiter..." etc. Also remove "Hiring Philosophy", "Who We Are", etc unless they contain substantive info not already covered. The "Who We Are" describes OPD capabilities; could be part of About the role but maybe redundant. We'll keep only essential. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are not boilerplate. Let's extract substantive content: From first paragraph: - "Your Job Optimized Process Designs (OPD), a Koch Engineered Solutions company, is looking for Senior I&E Designer who thrives on ownership, collaboration, and delivering high-impact projects." - "This is an opportunity to play a critical role in shaping I&E design solutions from concept through construction while leading and developing a talented design team." - "This role will sit at our headquarters in Katy, TX, Monday - Friday." - "This role is not eligible for visa sponsorship." Second paragraph about team: - "Our Team Optimized Process Designs is an engineering, procurement, and construction (EPC) firm executing on complex energy and infrastructure projects across North America." - "Their focus and expertise is in the natural gas, natural gas liquids, and petrochemical industries." - "OPD is part of the larger Koch organization which provides a variety of capabilities across many industries." - "OPD is known for technical excellence, disciplined project execution, and a culture that empowers engineers to take ownership and create long-term value." That's substantive. Now "What You Will Do" bullet list: - Support the development of the overall I&E design scope, schedule, and deliverable quality for assigned projects - Develop and review key I&E deliverables, including: - One-lines, schematics, and wiring diagrams - Interconnects, loop drawings, and instrument details - Cable schedules, panel schedules, and layout drawings - Grounding, duct bank, lighting, and power distribution designs - Coordinate I&E scope with piping, civil / structural , process and construction teams to resolve issues early and reduce work. - Perform and lead QA/QC reviews - Review vendor documentation and integrate equipment pack age requirements into design deliverables (note typo "pack age" but keep as is) - Proactively identify risks, scope gaps, and inefficiencies and drive timely resolution - Support project by providing clear updates on progress, risks, and priorities - Promote and reinforce a safety-first culture in all design activities Now "Who You Are (Basic Qualifications)" list: - Experience developing I&E design deliverables for industrial, EPC, energy, petrochemical, chemical, manufacturing, or related projects - Experience creating and reviewing design documents including schematics, wiring diagrams, loop drawings, interconnects, layouts, or similar deliverables - Experience using AutoCAD or similar design software - Experience coordinating with multiple engineering disciplines and stakeholders Now "What Will Put You Ahead" list: - Associate's degree or higher in Electrical, Instrumentation, Design, or equivalent technical discipline - Broad experience across instrumentation, electrical, and controls systems - Familiarity with midstream gas processing facilities - Practical field or construction experience supporting EPC projects Now "At Koch companies, we are entrepreneurs..." paragraph: This is more about culture; could be considered substantive but maybe not needed for a section. However it's not boilerplate; it's about company values. Could be included in About the role or maybe a separate section but we don't have a heading for culture. Could incorporate into About the role. Then compensation note: "Any compensation range provided for a role is an estimate determined by available market data. The actual amount may be higher or lower than the range provided considering each candidate's knowledge, skills, abilities, and geographic location. If you have questions, please speak to your recruiter about the flexibility and detail of our compensation philosophy." This is generic; no specific range. We should not create Pay section because no actual range. However we could note that compensation is market-based but not specific. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation philosophy but not a range. So we should not create Pay section. Then "Hiring Philosophy" etc: boilerplate about diversity, military ready, second chance. That's likely boilerplate EEO-ish; we should remove. Then "Who We Are" paragraph: Already somewhat covered; could be considered substantive but maybe redundant. We'll see if we need to keep. It says: "As a Koch Engineered Solutions company, Optimized Process Designs (OPD) provides clients with detailed engineering packages in all disciplines, single-point procurement for all equipment and materials, fabrication, and direct-hired construction services throughout the United States. We leverage in-house capabilities and provide services with faster speed to market to help deliver increased cost savings while minimizing risk. At Koch, employees are empowered to do what they do best to make life better. Learn how our business philosophy helps employees unleash their potential while creating value for themselves and the company." That's somewhat generic but still substantive about services. Could be included in About the role. Then "Our Benefits" section: list of benefits. - medical, dental, vision, flexible spending and health savings accounts, life insurance, ADD, disability, retirement, paid vacation/time off, educational assistance, and may also include infertility assistance, paid parental leave and adoption assistance. - Specific eligibility criteria is set by the applicable Summary Plan Description, policy or guideline and benefits may vary by geographic region. - If you have questions on what benefits apply to you, please speak to your recruiter. - Additionally, everyone has individual work and personal needs. We seek to enable the best work environment that helps you and the business work together to produce superior results. We should keep the substantive benefit list; remove the boilerplate sentences about eligibility criteria and speaking to recruiter? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sentences about eligibility criteria and speaking to recruiter are not exactly boilerplate but are generic; however they are part of benefits description. Might be considered boilerplate? The instruction says to remove boilerplate, but not to remove all generic sentences. However "If you have questions on what benefits apply to you, please speak to your recruiter." is similar to application instruction; we should remove. Also "Specific eligibility criteria is set by the applicable Summary Plan Description, policy or guideline and benefits may vary by geographic region." is generic but still substantive about variability. Might keep? It's not boilerplate per se but could be considered generic. I'd keep the benefit list and maybe note that eligibility varies by region. But to be safe, keep the benefit list and maybe a short sentence about eligibility varying. Now "Equal Opportunities" etc: remove. Now we need to output HTML fragment with headings and content. We'll decide sections: - About the role: combine first two paragraphs and maybe "Who We Are" and entrepreneurship paragraph. - Responsibilities: the "What You Will Do" list. - Requirements: basic qualifications list. - Qualifications: preferred qualifications list. - Benefits: benefits list. - Schedule: Monday-Friday. We might also include Skills? Not needed. Now ensure we don't repeat job title as heading. We won't. Now produce HTML. We'll need to wrap content in appropriate tags:

About the role

then

... maybe multiple paragraphs. For lists, use

• . We must not include or .