MES Analyst
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID/requisition numbers as headings; we can fold minor metadata into a short
or drop it. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove statements like "We prohibit discrimination..." etc. Also remove "To request an accommodation..." etc. Also remove "This position does not support immigration sponsorship." Might be considered minor metadata; we can fold into a short
maybe. But we need to keep substantive info: role purpose, responsibilities, experiences/education required and desired, working conditions, pay range, benefits description. We need sections only when posting has real specific content. So we will have sections: About the role (maybe from role purpose paragraph), Responsibilities, Requirements (maybe combine required education/experience), Qualifications (maybe desired?), Skills (maybe technical skills), Benefits, Pay. Schedule maybe not present except working conditions mention occasional off-hours, weekends, production outages, time on manufacturing floor. That could be Schedule? The instruction says use
for Schedule if present. We have working conditions that mention occasional support during off-hours, weekends, or production outages; may involve time on manufacturing floor. That's schedule info. So we can include a Schedule section.
We must not create sections with filler like "commensurate with experience". We have actual pay range: $78,062.00 - $107,335.00. So we can include Pay section.
Benefits: we have description of compensation and benefits package: company-paid pension, 401(k) matching, health benefits, parental leave, etc. So we can include Benefits.
We need to avoid duplication. Also need to remove EEO statement etc.
Let's extract substantive paragraphs:
- Intro about Corning (maybe not needed? It's about company but could be considered "About the role"? Actually role purpose is separate. The intro about company could be considered "About the role"? Might be considered background but not required. The instruction: "Prefer a few substantive sections over many thin ones." We could include an "About the role" section that includes the role purpose paragraph: "We are hiring an MES Analyst to support and improve Manufacturing Execution System (MES) solutions that keep manufacturing operations running effectively. In this role, you will work closely with manufacturing, engineering, quality, and IT teams to understand business needs, configure MES functionality, troubleshoot issues, and support system enhancements. The ideal candidate brings hands-on MES experience, strong problem-solving skills, and the ability to work in a regulated environment, including ITAR-controlled data handling."
That's good.
Responsibilities: list from "Key Responsibilities" bullet points.
We need to convert bullet list into - . The responsibilities are sentences each starting with a verb. We'll put each as
- .
Requirements/Education: The "Experiences/Education - Required" block. We'll put as
- maybe.
Desired experiences: "Experiences/Education – Desired". Could be under "Qualifications" or "Skills". We'll decide: maybe "Qualifications" for desired, "Skills" for technical skills like SQL, C#, etc. But we have overlapping. Let's think: The required includes degree, experience, understanding, hands-on software development experience using SQL, C#, Java, Python, etc., experience with databases, SQL queries, stored procedures, data analysis, APIs, web services, middleware, strong troubleshooting, familiarity with regulated environments, communication skills.
Desired includes experience with MES platforms, ERP, integrating with SCADA, PLCs, OPC-UA, historians, IIoT, knowledge of software development best practices, source control, testing, deployment, validated systems, access controls, audit-ready documentation.
We could have a "Requirements" section for required, and a "Preferred Qualifications" section for desired. But the instruction only lists specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: Requirements = required education/experience. Qualifications = desired experience. Skills = technical skills (SQL, C#, etc.) maybe overlapping with required. But we can still include.
Better: Use Requirements for required education/experience. Use Qualifications for desired experience (MES platforms, ERP, etc.). Use Skills for technical skills (SQL, C#, Java, Python, databases, APIs, troubleshooting, etc.). However required already includes those technical skills; but we can still list them under Skills. Might cause duplication but okay as long as we preserve info. Could also combine required and skills into one section but we need to follow headings. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine required education/experience and skills into one "Requirements" section, and desired into "Qualifications". Let's do that.
Thus:
- About the role: role purpose paragraph.
- Responsibilities: list of responsibilities.
- Requirements: combine required education/experience + technical skills (SQL, etc.) + understanding of manufacturing processes + troubleshooting + communication skills + regulated environment.
- Qualifications: desired experience (MES platforms, ERP, integration, best practices).
- Benefits: description of benefits package.
- Pay: pay range.
- Schedule: working conditions (off-hours, weekends, production outages, time on manufacturing floor). Also note "This position does not support immigration sponsorship." Could be minor metadata; we could include in a short p under Schedule or maybe drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include that sentence as a short p maybe under Schedule or at end. But we might drop it as not substantive? It's about immigration sponsorship; maybe minor but could be kept as short p. We'll include as a short p after Schedule section maybe.
We must not include boilerplate like EEO statement, accommodation request, etc. Also remove "A job that shapes a life." etc? That's fluff but maybe part of benefits? Actually that's a marketing line; could be considered boilerplate. We'll remove.
We'll also remove "Company-wide bonuses and long-term incentives align with key business results..." that's part of benefits; we can keep as part of benefits description.
We'll also remove "As part of our commitment to your financial well-being, we provide a 100% company-paid pension benefit..." that's benefits.
We'll also remove "Getting paid for our work is important..." that's fluff; maybe remove.
We'll also remove "We prohibit discrimination..." etc.
Now produce HTML fragment.
Structure:
About the role
We are hiring an MES Analyst to support and improve Manufacturing Execution System (MES) solutions that keep manufacturing operations running effectively. In this role, you will work closely with manufacturing, engineering, quality, and IT teams to understand business needs, configure MES functionality, troubleshoot issues, and support system enhancements. The ideal candidate brings hands-on MES experience, strong problem-solving skills, and the ability to work in a regulated environment, including ITAR-controlled data handling.
Responsibilities
- Support, maintain, and enhance MES applications to meet manufacturing and business needs.
- Gather and document requirements from production, quality, engineering, and IT stakeholders.
- Configure MES workflows, production data collection, traceability, electronic records, and reporting capabilities.
- Support MES extensions, scripts, interfaces, and integrations with ERP, SCADA, PLC, historian, and other enterprise systems.
- Troubleshoot MES incidents, defects, performance issues, and related manufacturing system problems.
- Perform root cause analysis and help implement corrective actions.
- Partner with developers, automation engineers, business analysts, and operations teams on enhancements and deployments.
- Participate in design, coding, testing, validation, deployment, and change management activities.
- Ensure MES systems, integrations, and documentation follow internal policies, cybersecurity standards, and applicable regulatory requirements, including ITAR.
- Maintain system documentation, technical specifications, SOPs, and configuration records.
- Support MES upgrades, patches, new functionality, user training, and ongoing support.
Requirements
- Bachelor’s degree in Computer Science, Information Systems, Engineering, Manufacturing Technology, or a related field.
- 12 months’ experience supporting or administering MES systems in a manufacturing environment.
- Strong understanding of manufacturing processes, quality systems, production workflows, and shop floor operations.
- Hands-on software development experience using SQL, C#, Java, Python, or similar languages.
- Experience with databases, SQL queries, stored procedures, data analysis, APIs, web services, or middleware.
- Strong troubleshooting and problem-solving skills across applications, databases, and integrated manufacturing systems.
- Familiarity with regulated or controlled environments, plus strong written and verbal communication skills.
Qualifications
- Experience with MES platforms such as Siemens Opcenter, Rockwell FactoryTalk, or similar systems.
- Familiarity with ERP systems such as SAP or Oracle.
- Experience integrating MES with SCADA, PLCs, OPC-UA, historians, IIoT platforms, or enterprise systems.
- Knowledge of software development best practices, source control, testing, deployment, validated systems, access controls, and audit-ready documentation.
Benefits
Corning offers a comprehensive compensation and benefits package that supports health and wellness, financial aspirations, and career growth from day one. This includes company-wide bonuses and long‑term incentives tied to business results, a 100% company‑paid pension benefit with fixed contributions that grow throughout your career, and matching contributions to a 401(k) savings plan (total retirement contributions can reach between 7% and 12% of pay depending on age and years of service). Health and well‑being benefits comprise medical, dental, vision, paid parental leave, family building support, fitness programs, company‑paid life insurance, disability coverage, disease management programs, paid time off, and an Employee Assistance Program (EAP). Additionally, Corning provides a recognition program to celebrate successes and reward colleagues who make exceptional contributions.
Pay
The range for this position is $78,062.00 - $107,335.00 assuming full‑time status. Starting pay for the successful applicant is dependent on a variety of job‑related factors, including geographic location, market demands, experience, training, and education.
Schedule
May require occasional support during off‑hours, weekends, or production outages. May involve time on the manufacturing floor in plant or production environments. This position does not support immigration sponsorship.
We need to ensure no extra markdown fences. Just raw HTML.
Check for any duplicated content: we didn't repeat the job title. We didn't include requisition number. We removed boilerplate. All substantive info preserved: role purpose, responsibilities, required education/experience, desired qualifications, benefits, pay, schedule, immigration note.
Check if any content missing: The intro about Corning (the first paragraph about company) we omitted; is that substantive? It's more marketing but could be considered "About the role"? The instruction says prefer few substantive sections over many thin ones. The company description may be considered not essential to the role; but it's part of the posting. However we might include it in About the role section as a brief paragraph before role purpose. But we already
- maybe.
Desired experiences: "Experiences/Education – Desired". Could be under "Qualifications" or "Skills". We'll decide: maybe "Qualifications" for desired, "Skills" for technical skills like SQL, C#, etc. But we have overlapping. Let's think: The required includes degree, experience, understanding, hands-on software development experience using SQL, C#, Java, Python, etc., experience with databases, SQL queries, stored procedures, data analysis, APIs, web services, middleware, strong troubleshooting, familiarity with regulated environments, communication skills.
Desired includes experience with MES platforms, ERP, integrating with SCADA, PLCs, OPC-UA, historians, IIoT, knowledge of software development best practices, source control, testing, deployment, validated systems, access controls, audit-ready documentation.
We could have a "Requirements" section for required, and a "Preferred Qualifications" section for desired. But the instruction only lists specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: Requirements = required education/experience. Qualifications = desired experience. Skills = technical skills (SQL, C#, etc.) maybe overlapping with required. But we can still include.
Better: Use Requirements for required education/experience. Use Qualifications for desired experience (MES platforms, ERP, etc.). Use Skills for technical skills (SQL, C#, Java, Python, databases, APIs, troubleshooting, etc.). However required already includes those technical skills; but we can still list them under Skills. Might cause duplication but okay as long as we preserve info. Could also combine required and skills into one section but we need to follow headings. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine required education/experience and skills into one "Requirements" section, and desired into "Qualifications". Let's do that.
Thus:
- About the role: role purpose paragraph.
- Responsibilities: list of responsibilities.
- Requirements: combine required education/experience + technical skills (SQL, etc.) + understanding of manufacturing processes + troubleshooting + communication skills + regulated environment.
- Qualifications: desired experience (MES platforms, ERP, integration, best practices).
- Benefits: description of benefits package.
- Pay: pay range.
- Schedule: working conditions (off-hours, weekends, production outages, time on manufacturing floor). Also note "This position does not support immigration sponsorship." Could be minor metadata; we could include in a short p under Schedule or maybe drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include that sentence as a short p maybe under Schedule or at end. But we might drop it as not substantive? It's about immigration sponsorship; maybe minor but could be kept as short p. We'll include as a short p after Schedule section maybe. We must not include boilerplate like EEO statement, accommodation request, etc. Also remove "A job that shapes a life." etc? That's fluff but maybe part of benefits? Actually that's a marketing line; could be considered boilerplate. We'll remove. We'll also remove "Company-wide bonuses and long-term incentives align with key business results..." that's part of benefits; we can keep as part of benefits description. We'll also remove "As part of our commitment to your financial well-being, we provide a 100% company-paid pension benefit..." that's benefits. We'll also remove "Getting paid for our work is important..." that's fluff; maybe remove. We'll also remove "We prohibit discrimination..." etc. Now produce HTML fragment. Structure:
About the role
We are hiring an MES Analyst to support and improve Manufacturing Execution System (MES) solutions that keep manufacturing operations running effectively. In this role, you will work closely with manufacturing, engineering, quality, and IT teams to understand business needs, configure MES functionality, troubleshoot issues, and support system enhancements. The ideal candidate brings hands-on MES experience, strong problem-solving skills, and the ability to work in a regulated environment, including ITAR-controlled data handling.
Responsibilities
- Support, maintain, and enhance MES applications to meet manufacturing and business needs.
- Gather and document requirements from production, quality, engineering, and IT stakeholders.
- Configure MES workflows, production data collection, traceability, electronic records, and reporting capabilities.
- Support MES extensions, scripts, interfaces, and integrations with ERP, SCADA, PLC, historian, and other enterprise systems.
- Troubleshoot MES incidents, defects, performance issues, and related manufacturing system problems.
- Perform root cause analysis and help implement corrective actions.
- Partner with developers, automation engineers, business analysts, and operations teams on enhancements and deployments.
- Participate in design, coding, testing, validation, deployment, and change management activities.
- Ensure MES systems, integrations, and documentation follow internal policies, cybersecurity standards, and applicable regulatory requirements, including ITAR.
- Maintain system documentation, technical specifications, SOPs, and configuration records.
- Support MES upgrades, patches, new functionality, user training, and ongoing support.
Requirements
- Bachelor’s degree in Computer Science, Information Systems, Engineering, Manufacturing Technology, or a related field.
- 12 months’ experience supporting or administering MES systems in a manufacturing environment.
- Strong understanding of manufacturing processes, quality systems, production workflows, and shop floor operations.
- Hands-on software development experience using SQL, C#, Java, Python, or similar languages.
- Experience with databases, SQL queries, stored procedures, data analysis, APIs, web services, or middleware.
- Strong troubleshooting and problem-solving skills across applications, databases, and integrated manufacturing systems.
- Familiarity with regulated or controlled environments, plus strong written and verbal communication skills.
Qualifications
- Experience with MES platforms such as Siemens Opcenter, Rockwell FactoryTalk, or similar systems.
- Familiarity with ERP systems such as SAP or Oracle.
- Experience integrating MES with SCADA, PLCs, OPC-UA, historians, IIoT platforms, or enterprise systems.
- Knowledge of software development best practices, source control, testing, deployment, validated systems, access controls, and audit-ready documentation.
Benefits
Corning offers a comprehensive compensation and benefits package that supports health and wellness, financial aspirations, and career growth from day one. This includes company-wide bonuses and long‑term incentives tied to business results, a 100% company‑paid pension benefit with fixed contributions that grow throughout your career, and matching contributions to a 401(k) savings plan (total retirement contributions can reach between 7% and 12% of pay depending on age and years of service). Health and well‑being benefits comprise medical, dental, vision, paid parental leave, family building support, fitness programs, company‑paid life insurance, disability coverage, disease management programs, paid time off, and an Employee Assistance Program (EAP). Additionally, Corning provides a recognition program to celebrate successes and reward colleagues who make exceptional contributions.
Pay
The range for this position is $78,062.00 - $107,335.00 assuming full‑time status. Starting pay for the successful applicant is dependent on a variety of job‑related factors, including geographic location, market demands, experience, training, and education.
Schedule
May require occasional support during off‑hours, weekends, or production outages. May involve time on the manufacturing floor in plant or production environments. This position does not support immigration sponsorship.
We need to ensure no extra markdown fences. Just raw HTML. Check for any duplicated content: we didn't repeat the job title. We didn't include requisition number. We removed boilerplate. All substantive info preserved: role purpose, responsibilities, required education/experience, desired qualifications, benefits, pay, schedule, immigration note. Check if any content missing: The intro about Corning (the first paragraph about company) we omitted; is that substantive? It's more marketing but could be considered "About the role"? The instruction says prefer few substantive sections over many thin ones. The company description may be considered not essential to the role; but it's part of the posting. However we might include it in About the role section as a brief paragraph before role purpose. But we already