Senior I&C Engineer II

We need to output HTML fragment with sections: About Stellix? Actually "About Stellix" is a section heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading. They want sections only when posting has real specific content. So we need to parse the posting. The posting includes: - About Stellix (mission description) - Here’s What You’ll Get (benefits list) - The Role (description) - Key Responsibilities (list) - What You'll Bring (requirements/qualifications) - Preferred (maybe part of qualifications) - Compensation (Pay) - Must be currently authorized to work in the United States (maybe a note) - Policy on Third-Party Unsolicited Resume Submissions (boilerplate, remove) - Please Note: Stellix is an Equal Opportunity Employer (EEO boilerplate, remove) We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we keep: - About Stellix (mission) - Here’s What You’ll Get (benefits) - The Role (description) - Key Responsibilities (list) - What You'll Bring (qualifications) - Preferred (maybe part of qualifications) - Compensation (Pay) - Authorization to work in US (maybe a note, could be a short p) We should not duplicate benefits: there are two identical benefit lists (first and later). We should include only once. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide sections: About Stellix (maybe as About the company? but they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About company but we can still use About Stellix as heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use About Stellix as heading. But they also said do NOT repeat the job title as a heading (the page already shows it). So we shouldn't put "The Stellix Senior I&C Engineer II role" as heading. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Thus we will produce sections:

  About Stellix

  with paragraph(s) describing mission.

  Benefits

  with ul list of benefits.

  About the Role

  maybe? They gave example About the role. The posting has "The Role". We'll use

  About the Role

  with paragraph(s) describing role.

  Responsibilities

  with ul list of responsibilities (Key Responsibilities).

  Qualifications

  with ul list of requirements (What You'll Bring). Possibly separate Preferred as part of qualifications but we can include as part of same list or separate? Could have

  Preferred Qualifications

  but they didn't list that as example but we could. However they said prefer a few substantive sections over many thin ones. So maybe combine Requirements and Preferred into one Qualifications section. We also need Pay section:

  Pay

  with paragraph about salary range. We may also include a short paragraph about work authorization: maybe under a

  but not a heading. We must not include duplicated benefit list. Let's extract content. About Stellix: "About Stellix The Stellix Group of companies share a common mission of providing transformative solutions at the intersection of science and technology that enable our customers to deliver a healthier and more sustainable future. Our unique portfolio of companies is focused on helping life sciences and industry manufacturers build, connect, and transform operations and IT to make real progress in breakthrough therapeutics, food, energy, and more." We'll put that in

  . Benefits list (first occurrence): "Highly competitive Medical, Dental, and Vision Insurance Flexible Spending or Health Savings Accounts Unlimited Vacation Time 10 Paid Holidays 12 Paid Weeks Maternity Leave Pet Insurance Retirement Savings: 401(k) and Employee Stock Ownership Plan Employee Referral Bonus Professional Development Reimbursement Company Paid STD, LTD, and Life Insurance" Later they repeated similar but with "12 Paid Weeks Birthing Parent Leave" instead of Maternity Leave. Actually second list: "12 Paid Weeks Birthing Parent Leave". We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include both? The second list says "12 Paid Weeks Birthing Parent Leave". The first says "12 Paid Weeks Maternity Leave". They are slightly different. We should include both? But they are duplicated lines? Not exactly duplicate; one says Maternity Leave, the other Birthing Parent Leave. Both are substantive. We should include both as separate list items? However they are under same heading "Here’s What You’ll Get" repeated. The instruction: remove duplicated lines. These are not exact duplicates but similar. We could combine? But we must preserve ALL substantive information; we cannot invent or summarize away detail. If we combine into one item "12 Paid Weeks of parental leave (maternity/birthing parent)" that would be summarizing. Better to keep both as separate items? But that would be duplicative conceptually but not exact text. The instruction: "remove duplicated lines". Since they are not identical lines, we might keep both. However they appear under same heading repeated; maybe we should treat as one benefits section and include both items. That seems okay. Thus benefits list items: - Highly competitive Medical, Dental, and Vision Insurance - Flexible Spending or Health Savings Accounts - Unlimited Vacation Time - 10 Paid Holidays - 12 Paid Weeks Maternity Leave - 12 Paid Weeks Birthing Parent Leave - Pet Insurance - Retirement Savings: 401(k) and Employee Stock Ownership Plan - Employee Referral Bonus - Professional Development Reimbursement - Company Paid STD, LTD, and Life Insurance Now About the Role paragraph(s): "The Stellix Senior I&C Engineer II role owns the largest and most complex I&C scopes in the portfolio with limited oversight. This role reports to the Manager, I&C Engineering and is expected to be a technical subject matter expert inside the team and in front of customers. You will lead control system hardware design and field execution scopes and act as the escalation point for difficult technical problems. You will direct the technical work of other engineering staff assigned to your projects, even though this role does not have direct reports. This is not a task execution role. You are responsible for technical outcomes, design quality, customer confidence, and the accuracy of the engineering basis used for proposals, estimates, bills of material, and project execution." We'll put that in

  . Responsibilities list (Key Responsibilities): We need to extract bullet points. The text includes paragraphs with bold headings? Let's parse: "Technical Authority and Leadership Serve as an internal and external technical authority for one or more core I&C technology areas. Lead the most complex control system hardware, panel, instrumentation, and industrial network scopes assigned to the team. Support definition of engineering standards, design approaches, calculation methods, and review expectations that are adopted by the broader I&C Engineering group. Act as the escalation point for difficult design issues, field problems, vendor questions, and commissioning defects. Review work prepared by my junior roles and provide clear technical direction. Mentor engineers in hardware design, field troubleshooting, customer communication, and technical decision making. Design and Specification Own design packages for DCS and PLC control system hardware, including controllers, redundant remote I/O, communication interfaces, gateways, redundancy schemes, and power distribution. Produce and review UL 508A panel designs, including enclosure layouts, SCCR calculations, component selection, grounding, labeling, wiring, and compliance requirements. Design and troubleshoot industrial communication networks, including PROFIBUS DP/PA, PROFINET, Modbus TCP/RTU, Ethernet/IP, HART, Foundation Fieldbus, DeviceNet, and AS-i. Develop industrial network architectures, switch selections, ring topologies, and physical-layer diagnostic approaches. Specify field instrumentation, including thermocouples, RTDs, pressure, flow, level, and analytical devices. Use and review electrical CAD deliverables in AutoCAD Electrical, SolidWorks Electrical, EPLAN, or similar tools. Apply NFPA 70, UL 508A, UL 698A, IEC, ISA, and IEEE standards to real project designs. Project Execution Lead engineering execution from design basis through turnover. Coordinate with panel fabrication subcontractors while retaining Stellix ownership of the design, HFAT, commissioning support, and turnover package. Own technical decisions during design reviews, fabrication questions, hardware testing, commissioning, and closeout. Identify technical risk early and drive it to closure before it affects schedule, cost, or field execution. Customer and Commercial Support Support sales and project development for complex opportunities through FEED studies, site walkdowns, scope definition, hours estimates, BOM generation, compliance tables, and proposal write-ups. Develop proposal content for major I&C opportunities with enough detail that the scope, assumptions, exclusions, and technical basis are clear. Communicate directly with customers, vendors, subcontractors, project managers, and internal leadership on assigned work. Maintain billable utilization consistent with a senior engineering services role." We need to turn each line into

• . Should we keep the headings (Technical Authority and Leadership etc.) as separate list items? They are headings within responsibilities; we could treat them as
• but they are not duties. Better to maybe keep them as
• but they are section headings. However instruction: use
  • for any list of duties/requirements/benefits. So we can treat each bullet as a duty. The headings are not duties but could be considered as grouping; we could either omit them or keep as
  • but they'd be weird. Perhaps we can keep them as
  • but they'd be less meaningful. Better to omit the headings and just list the duties. However we risk losing some structural info but not substantive duty. The headings themselves are not duties; they are categories. The instruction says preserve ALL substantive information; headings are substantive? They are part of the responsibilities section. Might be considered substantive. But we could incorporate them as
  • but they'd be odd. Another approach: we could keep them as
  • but they'd be like "Technical Authority and Leadership" as a duty, which is not accurate. I'd rather omit them and just list the duty sentences. The headings are not essential for understanding duties; the sentences under them convey the duties. So we can drop the headings. Thus responsibilities list items: - Serve as an internal and external technical authority for one or more core I&C technology areas. - Lead the most complex control system hardware, panel, instrumentation, and industrial network scopes assigned to the team. - Support definition of engineering standards, design approaches, calculation methods, and review expectations that are adopted by the broader I&C Engineering group. - Act as the escalation point for difficult design issues, field problems, vendor questions, and commissioning defects. - Review work prepared by my junior roles and provide clear technical direction. - Mentor engineers in hardware design, field troubleshooting, customer communication, and technical decision making. - Own design packages for DCS and PLC control system hardware, including controllers, redundant remote I/O, communication interfaces, gateways, redundancy schemes, and power distribution. - Produce and review UL 508A panel designs, including