IT/OT Engineer II
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- About Stellix: description of company mission, portfolio. This is about the company, not necessarily a required section but we can include as "About the company" maybe. The instruction says use headings for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that list? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if they exist. The posting includes "About Stellix" (company overview). Could map to "About the role"? Not exactly. There's also "Here’s What You’ll Get" (benefits). There's "The Role" (description). There's "Education, Experience & Skills". There's "What You’ll Do" (responsibilities). There's "How You’ll Be Successful" (maybe skills/qualities). There's "Benefits" (list). There's "Compensation" (Pay). There's also "Must be currently authorized to work in the United States." etc. There's also policy statements (EEO) which we should remove as boilerplate.
We need to remove duplicated lines, cookie/navigation/legal/EEO etc. So we should drop the EEO paragraph and the third-party unsolicited resume submissions policy? That might be considered boilerplate/legal; we should remove it. Also "Policy on Third-Party Unsolicited Resume Submissions" maybe considered legal; remove. Also "Please Note: Stellix is an Equal Opportunity Employer..." remove.
We need to preserve all substantive information: company description, role description, responsibilities, qualifications, skills, benefits, compensation.
We need to decide sections.
Potential sections:
- About the company (maybe "About Stellix") but not in list. Could use "About the role"? Actually "About Stellix" is about the company, not role. The instruction says we can use those example headings, but not required to limit to them. However they say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings for sections that match. If we have a section about company overview, we could still use but maybe not one of those examples; but it's okay to use any heading as long as it's . Safer to use "About Stellix" as heading.
But they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have other headings.
We need to avoid sections with filler text. So we need to ensure each section has substantive content.
Let's extract content:
Company description:
"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."
That's substantive.
Here's What You’ll Get (benefits list):
"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 in Benefits section repeats similar but with slight variations: "Competitive Medical, Dental & Vison Insurance Flexible Spending or Health Savings Accounts Unlimited Vacation Time Policy10 Paid Holidays 12 Paid Weeks Birthing Parent Leave Retirement Savings: 401(k) and Employee Stock Ownership Plan Pet InsuranceEmployee Referral Bonus Tuition Reimbursement Company Paid STD, LTD, and Life Insurance"
We need to combine and deduplicate. Keep all unique benefits.
List:
- Highly competitive Medical, Dental, and Vision Insurance
- Flexible Spending or Health Savings Accounts
- Unlimited Vacation Time
- 10 Paid Holidays
- 12 Paid Weeks Maternity Leave (or Birthing Parent Leave)
- Pet Insurance
- Retirement Savings: 401(k) and Employee Stock Ownership Plan
- Employee Referral Bonus
- Professional Development Reimbursement (or Tuition Reimbursement)
- Company Paid STD, LTD, and Life Insurance
We also have "Professional Development Reimbursement" earlier, later "Tuition Reimbursement". Might be same concept; we can keep both or combine as "Professional Development / Tuition Reimbursement". To avoid duplication, we can list one: "Professional Development / Tuition Reimbursement". But we must preserve all substantive information; not invent or summarize away detail. If we combine, we might be summarizing. Better to keep both as separate items? They are similar but not identical; we could keep both but note they are similar. However duplication removal instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should remove duplicated lines. The two lines are similar but not exact duplicates; one says "Professional Development Reimbursement", the other "Tuition Reimbursement". They are not identical lines, but they are conceptually similar. The instruction says remove duplicated lines, not necessarily similar meaning. So we can keep both if they are not exact duplicates. However to avoid redundancy, we could keep both as they are distinct benefits. I'd keep both.
Now "The Role" description:
"We are currently seeking to fill an IT/OT Engineer III position within our IT/OT Managed Services team to provide post-project services (such as infrastructure, virtualization, networking, cybersecurity and other IT/OT services) and automation solutions for our installed customer base, using a portfolio of Emerson products and some select third-party platforms. IT/OT Solutions may include scheduled maintenance or managed services for system administration; cyber security solutions; performance and reliability services; help desk and emergency services, digital plant troubleshooting and integration; system installation and commissioning; system upgrades; operational solutions for alarm management, loop performance, process simulation; lifecycle consulting and business continuity services. The IT/OT Engineer III will be expected to perform services for customers including via annual service contracts, service bank, assigned projects and some subscription-based offers. It is expected for the IT/OT Engineer III to support and advise customers on a range of IT/OT and virtualization 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."
That's substantive.
"Education, Experience & Skills" section:
"BS Degree in Computer Science, Chemical Engineering, Electrical Engineering or equivalent.
3+ years delivering industrial control system/infrastructure solutions.
Must have either of: 2 years of DeltaV systems experience (hardware, troubleshooting/RCA, upgrading/patching, and/or virtualization). 3 years of other Manufacturing/Laboratory OT systems experience (troubleshooting/RCA, integration, networking and administration, lifecycle management, upgrading/patching). 3 years of IT experience as a service provider (virtualization, networking, cybersecurity, troubleshooting/RCA, upgrading/patching).
Must have 2 years of 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, virtualization, serial and ethernet communications and hardware, technical drawings including: P&IDs, electrical schematics, loop drawings, network architecture drawings.
Soft Skills: Infinite Leadership mentality and interest in coaching/mentoring 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.
Must be able to travel extensively within the New England region."
That's qualifications/requirements.
"What You’ll Do" responsibilities:
"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 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."
That's responsibilities.
"How You’ll Be Successful" maybe skills/attributes:
"Leverage your passion for technology and your customer-focused mindset to grow your customer relationships to a level of a trusted advisor, mapping automation solutions that will solve our customers' complex operational challenges and support their digital journey.
Flexibility - May be called upon for coordination of other Stellix Global Services personnel and cross-functional teams to ensure the delivery of the overall results expected by the customer.
Bring passionate team spirit and a commitment for excellence in all work products.
Proactively drive and deliver projects and services via the lifecycle solutions portfolio,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - About Stellix: description of company mission, portfolio. This is about the company, not necessarily a required section but we can include as "About the company" maybe. The instruction says use headings for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that list? It says "use