IT/OT Engineer

We need to output HTML fragment with sections: About Stellix? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to include sections only when posting has real specific content. We have content: About Stellix (mission, portfolio). That's like "About the company". Could map to "About the role"? Actually "About Stellix" is about company. Could be "About the role"? But we have separate "The Role". The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if content matches. We have sections: - About Stellix (company overview) -> maybe "About the role"? Not exactly. Could use "About Stellix" as heading? Not in list but we can still use

for any section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It implies we should use those standard headings, but we can also use other headings if needed? Safer to stick to those headings. We have content that fits: - About the role: we have "The Role" paragraph describing position. So we can put that under

About the role

. - Responsibilities: we have "Responsibilities of this role may range to include ..." plus later "What You’ll Do" day-to-day tasks. Combine into responsibilities. - Requirements: we have Education, Experience & Skills section. Could be Requirements or Qualifications. We'll use

Requirements

(or Qualifications). The instruction includes both Requirements and Qualifications. We'll choose Requirements. - Skills: we have soft skills and technical skills; could be Skills section. - Benefits: we have "Here’s What You’ll Get" list of benefits (medical, dental, vision, etc.) repeated later. So Benefits section. - Pay: we have compensation base salary range $85k-$120k. So Pay section. - Schedule: we have On-Site Requirements describing schedule (full on-site 5 days first 4-6 months then 4 days per week). So Schedule section. We must not include boilerplate like EEO, policy, etc. We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". We have specific details. We need to use

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

  for prose. We need to avoid repeating content. Let's extract content. About Stellix: paragraph: "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 could put that under About the role? Actually About Stellix is company overview. Could be part of About the role? Might be better to have a separate "About Stellix" heading but not in list. However instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use

  for section headings (e.g. ...). I'd interpret that we should use those headings when applicable; if we have company overview, we could still use About the role? Not accurate. Maybe we can treat About Stellix as part of About the role? But the role description is separate. Could we omit About Stellix? It's substantive info about company; we should preserve. Could we put it under a heading like "About Stellix" using

  ? The instruction didn't forbid other headings, just gave examples. So we can use

  About Stellix

  . That seems fine. Now Responsibilities: combine the responsibilities paragraph and "What You’ll Do" day-to-day tasks. Let's list responsibilities: From "Responsibilities of this role may range to include scheduled maintenance activities or managed services for customers’ DCS system administration; cyber security solutions; automation performance and reliability services; customer help desk and emergency services, digital plant troubleshooting and integration; system installation and commissioning; DCS system upgrades; operational solutions for alarm management, loop performance, process simulation; lifecycle consulting and business continuity services." Also: "The IT/OT Engineer in the managed services team will be expected to perform consultative services for customers via annual service contracts, service bank, assigned projects and some subscription-based offers. Building “trusted advisor” relationships, it is expected for the IT/OT Engineer to support and advise customers on a range of IT/OT and virtualization life cycle platform recommendations that will solve customer pain, optimize business value, and enhance customer satisfaction with their IT/OT investments to support meeting their business goals." Then "What You’ll Do" list: - Day-to-day technical support and help desk for customer contracts to support their IT/OT systems. - Following triage, demonstrate situational awareness for escalation to more senior engineering members or the software vendor’s factory support. - Liaison with Emerson, Rockwell, Dell, VMWare, Cisco, and other third-party partners. - Complete assigned service agreement deliverables in a timely manner with high quality and quantifiable business results. - Manage the completion of these contract obligations with some oversight from the contracts coordinator or department manager, demonstrating organization skills and self-starting capabilities. - Support lifecycle solutions IT/OT Team Leads with infrastructure network design, installation, commissioning and maintenance activities in a Microsoft OS environment, often utilizing either VMWare or HyperV virtualization platforms. - Be able to provide technical leadership and mentoring to less senior engineers. - Support design and build activities for Life Science customers and others in a Quality controlled methodology. Involve extensive documentation, internal testing, Factory Acceptance Testing, Site Acceptance Testing and site commissioning services as assigned. - Troubleshoot IT/OT and automation control systems at the virtual, physical network, controller, and I/O level, in order to resolve customer problems in an efficient manner and keep their system running or the project on schedule. - Provide lifecycle engineering solutions in the areas of server, workstation, networking, software configuration, digital bus, DeltaV hardware, virtualization, alarm management or other areas of expertise. - Provide timely and thorough communication to customers in both written and oral format. - Demonstrate an organized and methodical approach to troubleshooting and problem solving. - Execute contract or project deliverables following direction, and/or by following established procedures or guidelines. - Work towards completion of the DeltaV Field Service Associate certification, as well as other certifications as assigned. - Actively involve/inform Account Managers of potential opportunities identified through customer engagements to help drive service expansion and increased customer satisfaction. - Support to improve the long-term growth of Stellix Global Services’ IT/OT business through supporting business development, maintaining and improving customer relations, and supporting internal programs for continuous improvement and efficiency. - Under supervision, execute installed-base lifecycle projects within budget and schedule, and take ownership for project quality and customer value outcome. - 24x7 support for customer emergencies under a monthly rotating assignment roster. - Comply with all Stellix Global Services requirements for business processes including time entry, site visit reports and all other documentation according to internal procedures. We need to put these as
  • items. Now Requirements/Education: "Education, Experience & Skills BS Degree in Computer Science, Chemical Engineering, Electrical Engineering or equivalent.Must have either of:3-5 years of DeltaV or similar DCS systems experience (hardware and platform, troubleshooting/RCA, DCS upgrades/administration, integration and/or virtualization).5-7 years of other Manufacturing/Laboratory OT systems experience (troubleshooting/RCA, integration, networking and administration, lifecycle management, upgrading/patching).5-7 years of IT experience as a service provider (virtualization, networking, cybersecurity, troubleshooting/RCA, upgrading/patching).Preferred: 2-4 years of direct experience in Life Sciences Industry.Familiar with cGMP, GDP, quality/regulatory requirements, FAT/SAT/CQV.Demonstrated increasing level of responsibility supporting OT systems.Familiar with analog and discrete signaling, serial and Ethernet communications and hardware, technical drawings including: P&IDs, electrical schematics, loop drawings, network architecture drawings. Virtualization experience and networking knowledge preferred.Soft Skills:Embodies an “Infinite Leadership” mentality and interest in coaching/mentoring with long game in mind.Collaboration and team workTime management and reportingDetail oriented, good documentation skillsCritical thinking and problem solvingAbility to assess risk through review of documentation and KBAs.Applicants should either reside locally or express a willingness to relocate to the Foxborough, MA area.Must be able to travel extensively within the New England region." We need to split into Requirements (education/experience) and Skills (soft skills). Let's parse. Education/Experience: - BS Degree in Computer Science, Chemical Engineering, Electrical Engineering or equivalent. - Must have either of: - 3-5 years of DeltaV or similar DCS systems experience (hardware and platform, troubleshooting/RCA, DCS upgrades/administration, integration and/or virtualization). - 5-7 years of other Manufacturing/Laboratory OT systems experience (troubleshooting/RCA, integration, networking and administration, lifecycle management, upgrading/patching). - 5-7 years of IT experience as a service provider (virtualization, networking, cybersecurity, troubleshooting/RCA, upgrading/patching). - Preferred: 2-4 years of direct experience in Life Sciences Industry. - Familiar with cGMP, GDP, quality/regulatory requirements, FAT/SAT/CQV. - Demonstrated increasing level of responsibility supporting OT systems. - Familiar with analog and discrete signaling, serial and Ethernet communications and hardware, technical drawings including: P&IDs, electrical schematics, loop drawings, network architecture drawings. - Virtualization experience and networking knowledge preferred. Soft Skills: - Embodies an “Infinite Leadership” mentality and interest in coaching/mentoring with long game in mind. - Collaboration and team work - Time management and reporting - Detail oriented, good documentation skills - Critical thinking and problem solving - Ability to assess risk through review of documentation and KBAs. - Applicants should either reside locally or express a willingness to relocate to the Foxborough, MA area. - Must be able to travel extensively within the New England region. Note: The relocation and travel could be considered requirements but they are more like location requirements; we could keep them under Requirements or Skills. Since they are not soft skills exactly, but we can put them under Requirements as additional criteria. But we already have a Requirements section; we can include those there. Skills section: soft skills list. Now Benefits: list from "Here’s What You’ll Get" (first occurrence) and repeated later. 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 (later: 12 Paid Weeks Birthing Parent Leave) – we need to preserve both? The second occurrence says "12 Paid Weeks Birthing Parent Leave". We should keep that as benefit. The first says maternity leave; second says birthing parent leave. Both are similar; we can combine? But we must preserve all substantive information; we could list both as separate items? Might be redundant but we can keep both. However we should avoid duplication? The instruction says remove duplicated lines. So we should deduplicate. The benefit is essentially 12 weeks paid parental leave. We'll keep one item: "12 Paid Weeks Parental Leave" (or Birthing Parent Leave). We'll choose "12 Paid We