Jobs · Engineering · Pennsylvania

Reliability Engineer

Emerson · Erie, PA · 4 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections for headings present in the posting: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes a job description with many details. It includes "About the role" maybe not explicitly but we can infer. The description starts with "Job Description Urick Ductile Solutions manufactures ...". There's no explicit headings but we can create sections based on content: About the role (intro paragraph), Responsibilities (list of duties), Requirements (education/experience), Qualifications (preferred qualifications), Skills (maybe combine with requirements?), Benefits (benefits described), Pay (not mentioned), Schedule (not mentioned). So we should not include Pay or Schedule sections because no specific content. Benefits: there is a paragraph about benefits: "Our Culture & Commitment to You: ... We provide a variety of medical insurance plans, with dental and vision coverage, Employee Assistance Program, 401(k), tuition reimbursement, employee resource groups, recognition, and much more. Our culture offers flexible time off plans, including paid parental leave (maternal and paternal), vacation and holiday leave." That's benefits. So include Benefits section. Also there is "About Us" etc but that's boilerplate; we should remove cookie/navigation/legal/EEO etc. The posting includes EEO statement etc; we must remove that. Also remove "Work Authorization" etc? That's legal; we should remove. Also remove "Equal Opportunity Employer" etc. Also remove "Accessibility Assistance". Also remove "About Emerson" etc? That's likely boilerplate; but some content about Emerson may be considered boilerplate but maybe not required to remove? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove sections that are clearly legal/EEO etc. The "About Emerson" paragraph describing the company might be considered boilerplate but it's not EEO; it's company overview. Might be okay to keep? However it's likely part of the job posting but not specific to role; but instruction says preserve ALL substantive information; do not invent or summarize away detail. The "About Emerson" is substantive about the company; but it's not role-specific. Might be okay to keep as part of "About the role"? But we have no explicit heading. We could include a short paragraph under About the role that includes company description. However the instruction says 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. So we can have a

for About the role that includes company description and role summary. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to capture all duties etc. That's a lot. We need to output an HTML fragment with sections: About the role (maybe a

    summarizing), Responsibilities (maybe a

      of duties), Requirements (education/experience), Qualifications (preferred qualifications), Skills (maybe combine with requirements? but we can have Skills section for specific skills like CMMS, predictive maintenance, etc), Benefits (benefits). We must not include Pay or Schedule. We need to ensure we don't create sections with filler text. So only include sections where we have real content. Let's extract content: About the role: The first paragraph: "Urick Ductile Solutions manufactures ductile iron castings for a variety of industrial markets. We are seeking a hands-on Reliability Engineer to improve equipment availability, reduce unplanned downtime, and strengthen maintenance systems across our foundry operations. The Reliability Engineer develops and sustains the processes, tools, and technical strategies required to maximize equipment reliability and support safe, stable, and efficient production. This position serves as the technical leader for asset reliability, preventive and predictive maintenance, CMMS administration, root cause failure analysis, and maintenance-related capital projects. The successful candidate will work closely with Operations, Maintenance, Engineering, MRO, EHS, Quality, suppliers, and plant leadership to eliminate recurring equipment failures and help transition the organization from reactive maintenance to a planned, disciplined, and reliability-focused culture." That's substantive. Responsibilities: The bullet-like sections after that: "Reliability and Asset Management", "CMMS Ownership and Maintenance Systems", "Preventive, Predictive, and Operator Maintenance", "Root Cause Analysis and Reliability Improvement", "Spare Parts and MRO Support", "Maintenance Projects, Shutdowns, and Capital Improvements", "Reliability Performance Management". Each contains many sentences. We can turn each bullet into
    • items, maybe grouping. We need to preserve all substantive information; we can break into multiple
    • items each covering a responsibility. Could be many items; that's okay. Requirements: "For This Role, You Will Need: Bachelor's degree in Mechanical, Electrical, Industrial, Manufacturing, or a related engineering discipline; or an associate or technical degree combined with substantial relevant industrial maintenance and reliability experience. Three or more years of engineering, maintenance, or reliability experience in manufacturing or industrial operations. Demonstrated experience troubleshooting mechanical, electrical, hydraulic, pneumatic, controls, and utility equipment. Experience using a CMMS to manage asset records, PMs, job plans, failure history, backlog, and maintenance performance. Demonstrated use of structured problem-solving or root-cause methods. Ability to lead cross-functional improvement projects and communicate effectively with skilled trades, operators, supervisors, engineers, suppliers, and plant leadership. Strong organization, project management, and data-analysis skills, including proficiency with Microsoft Excel, Word and CAD. Legal authorization to work in the United States – sponsorship will not be provided." We should keep the legal authorization line? It's a requirement; it's not boilerplate? It's a requirement; we can keep. Preferred Qualifications: "Preferred Qualifications That Set You Apart: Foundry, metals, machining, heavy-industrial, or process-manufacturing experience. Experience with DISA molding, sand systems, furnaces, dust collection, cranes, conveyors, core-making, machining, compressed air, cooling-water, or comparable industrial systems. Experience with Maintenance Connection or a comparable CMMS or EAM platform. Predictive-maintenance experience in vibration, thermography, ultrasound, oil analysis, or motor and electrical testing. Knowledge of FMEA, Reliability Centered Maintenance, TPM, autonomous maintenance, and equipment failure analysis. PLC and industrial controls troubleshooting experience. Experience with capital projects, shutdowns, equipment installation, and commissioning. CMRP, CRL, vibration-analysis, thermography, or other relevant reliability certification. AutoCAD, Inventor, or other CAD software experience." Skills: Could be derived from requirements and preferred qualifications; but we might combine into Skills section: maybe list specific skills like CMMS, predictive maintenance, root cause analysis, etc. However we already have Requirements and Qualifications sections; Skills could be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one "Requirements" section that includes both required and preferred? But they ask to use headings like Requirements, Qualifications, Skills. We could have Requirements (mandatory), Qualifications (preferred), Skills (maybe technical skills). But to avoid thin sections, we could have Requirements (includes education/experience), Qualifications (preferred experience/certifications), Skills (technical skills like CMMS, predictive maintenance, CAD, etc). However many of those overlap. Given the instruction to prefer few substantive sections, maybe we just have About the role, Responsibilities, Requirements (including education/experience), Qualifications (preferred), Benefits. That's five sections. Skills could be omitted as its content covered in Requirements/Qualifications. We must not include Pay or Schedule. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce something like:

      About the role

      ...

      Responsibilities

      • ...
      • ...

      Requirements

      • ...
      • ...

      Qualifications

      • ...
      • ...

      Benefits

      • ...
      • ...
      We need to ensure we don't include any boilerplate like EEO etc. We'll cut out those paragraphs. Now we need to copy the content exactly, preserving all substantive information, not inventing or summarizing away detail. That means we need to include all details from the posting. That's a lot; we must be careful not to omit any detail. We'll need to parse the posting and include each sentence as part of
    • or

      . However we can combine sentences into

    • items as long as we don't lose detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot omit any detail; we can rephrase? Probably we should keep the original wording as much as possible, but we can split into list items. We need to be careful not to miss any piece. Let's extract the full text from the posting (excluding boilerplate). I'll copy the relevant sections: Job Description Urick Ductile Solutions manufactures ductile iron castings for a variety of industrial markets. We are seeking a hands-on Reliability Engineer to improve equipment availability, reduce unplanned downtime, and strengthen maintenance systems across our foundry operations. The Reliability Engineer develops and sustains the processes, tools, and technical strategies required to maximize equipment reliability and support safe, stable, and efficient production. This position serves as the technical leader for asset reliability, preventive and predictive maintenance, CMMS administration, root cause failure analysis, and maintenance-related capital projects. The successful candidate will work closely with Operations, Maintenance, Engineering, MRO, EHS, Quality, suppliers, and plant leadership to eliminate recurring equipment failures and help transition the organization from reactive maintenance to a planned, disciplined, and reliability-focused culture. Reliability and Asset Management Improve equipment reliability, availability, and maintainability across all foundry processes including melt, mold, core, finish, material-handling, utility, and facility systems. Establish and maintain asset criticality rankings to prioritize reliability resources and improvement activity. Identify chronic and high-impact equipment issues and develop plans to eliminate recurring failures. Develop reliability strategies for critical and constraint equipment. Support equipment lifecycle planning, modernization, and obsolescence-risk mitigation. CMMS (Computerized Maintenance Management System) Ownership and Maintenance Systems Own and administer the plant CMMS, including asset hierarchy, equipment records, preventive maintenance programs, job plans, failure codes, equipment history, parts relationships, and reporting. Establish data standards and audit CMMS accuracy and consistent use across Maintenance and Operations. Train employees on work-request, work-order, failure-coding, and maintenance-history requirements. Use CMMS data to identify failure trends, maintenance demand, backlog risk, and improvement priorities. Improve maintenance planning, prioritization, scheduling, execution, and closeout processes. Preventive, Predictive, and Operator Maintenance Develop and optimize preventive maintenance based on asset criticality, failure history, OEM guidance, and operating experience. Evaluate and implement condition-based and predictive maintenance practices where economically justified, including vibration, thermography, ultrasound, oil analysis, and electrical testing. Improve maintenance job plans to include labor, parts, tools, safety requirements, acceptance criteria, and estimated duration. Track PM and scheduled-work compliance and lead corrective actions when performance is below expectation. Partner with Operations and Maintenance to develop operator care, inspection, cleaning, lubrication, and basic-condition standards. Root Cause Analysis and Reliability Improvement Lead or facilitate structured root cause failure analysis for significant, repeat, and high-cost equipment failures. Apply methods such as 5 Why, cause-and-effect analysis, and Failure Mode and Effects Analysis (FMEA). Develop corrective actions with clear owners and completion dates, and verify that completed actions prevent recurrence. Update

Similar jobs

Reliability Engineer

ReckittEvansville, IN· 1 mo ago
Supply Chain$73k–$109k/yrapply on careers.reckitt.com

Reliability Engineer

LiquidPower Specialty Products Inc. (a Berkshire Hathaway Company)Grady County, OK· 2 mo ago
Engineeringapply on recruiting2.ultipro.com

Reliability Engineer

I-care Reliability Inc.Valdosta, GA· 3 mo ago
Engineeringapply on icare-usa.cvw.io