1

Nerc System Operator Jobs in Ohio (NOW HIRING)

Mulesoft Integration

Columbus, OH · On-site

$97K - $130K/yr

... critical integration workstream operating under NERC CIP and related utility regulatory ... Design, build, and maintain middleware integration layers connecting OT systems (SCADA, smart meter ...

Assists other operators and terminals to ensure standards are being met Preferred Qualifications ... Knowledge of access control systems and NERC CIP compliance regulations is a plus. Other Preferred ...

... systems studies ensuring compliance with NERC, PJM and FE planning criteria. * Proposing and ... If capital projects cannot be implemented in the needed timeframe, a detailed operating solution is ...

... systems studies ensuring compliance with NERC, PJM and FE planning criteria. * Proposing and ... If capital projects cannot be implemented in the needed timeframe, a detailed operating solution is ...

... systems studies ensuring compliance with NERC, PJM and FE planning criteria. * Proposing and ... If capital projects cannot be implemented in the needed timeframe, a detailed operating solution is ...

... systems, more than 24,500 miles of transmission lines that connect the Midwest and Mid-Atlantic ... NERC, Reliability First, PJM Transmission Operator requirements, and related Operations and ...

... systems, more than 24,500 miles of transmission lines that connect the Midwest and Mid-Atlantic ... NERC, Reliability First, PJM Transmission Operator requirements, and related Operations and ...

Showing results 21-40

Nerc System Operator information

See Ohio salary details

$10

$31

$79

How much do nerc system operator jobs pay per hour?

As of Sep 7, 2026, the average hourly pay for nerc system operator in Ohio is $31.07, according to ZipRecruiter salary data. Most workers in this role earn between $18.51 and $36.35 per hour, depending on experience, location, and employer.

What is a NERC System Operator?

A NERC System Operator is responsible for monitoring and controlling the electrical power grid to ensure a reliable and balanced flow of electricity. They follow North American Electric Reliability Corporation (NERC) standards to prevent outages and respond to system disturbances. Operators communicate with power plants, substations, and other entities to manage grid stability and emergency situations. They typically work in real-time control centers and must be NERC-certified to perform their duties.

What is a typical workday like for a NERC System Operator?

A typical day for a NERC System Operator involves monitoring real-time grid conditions, responding to alarms, coordinating planned and unplanned outages, and communicating with field personnel and neighboring utilities to maintain system reliability. Operators often work in a control room setting, using advanced software and monitoring equipment to oversee power flows and facilitate rapid responses to disturbances. The role requires vigilance, as operators must be ready to take swift, decisive action during emergency events or system anomalies. Shifts may cover nights, weekends, and holidays due to the 24/7 nature of grid operations, but this dynamic environment also offers opportunities to develop specialized expertise and advance into senior roles within grid management or operations planning.

What are the key skills and qualifications needed to thrive as a NERC System Operator?

To thrive as a NERC System Operator, you need a solid understanding of electric power systems, grid operations, and regulatory compliance, often supported by a degree in electrical engineering or a related field and the NERC certification. Familiarity with energy management systems (EMS), SCADA systems, and outage coordination tools is critical. Strong decision-making abilities, communication skills, and the capacity to perform under pressure help operators excel. These competencies ensure the safe, reliable, and efficient operation of the power grid in compliance with federal standards.

What are the most commonly searched types of Nerc System Operator jobs in Ohio?

The most popular types of Nerc System Operator jobs in Ohio are:

What are popular job titles related to Nerc System Operator jobs in Ohio?

For Nerc System Operator jobs in Ohio, the most frequently searched job titles are:

What cities in Ohio are hiring for Nerc System Operator jobs?

Cities in Ohio with the most Nerc System Operator job openings:

Infographic showing various Nerc System Operator job openings in Ohio as of August 2026, with employment types broken down into 1% As Needed, 82% Full Time, 12% Part Time, 1% Temporary, and 4% Contract. Highlights an 91% Physical, 2% Hybrid, and 7% Remote job distribution, with an average salary of $64,636 per year, or $31.1 per hour.

Mulesoft Integration

CogniSoft Technologies

Columbus, OH • On-site

$97K - $130K/yr

Other

Posted 5 days ago


Job description

Position :  Mulesoft Integration Architect / Engineer
Location : Columb OHIO (Hybrid)
Duration: 12+ months contract
Utility & Regulated Industry Integration Program
 
Engagement Overview
 
Need 5–6 senior middleware engineers to staff a large, regulated utility client's enterprise integration program, spanning grid operations technology (OT), smart meter/AMI data, outage management, billing, and enterprise IT (ERP/CRM). This is a mission-critical integration workstream operating under NERC CIP and related utility regulatory requirements. Engagement is structured 60% onsite (US) and 40% offshore (India), onshore-led with offshore-leveraged delivery. Client identity is confidential for external-facing postings; refer to it as "a Fortune 500 regulated utility client."
 
Key Responsibilities
* Design, build, and maintain middleware integration layers connecting OT systems (SCADA, smart meter/AMI, outage management) with enterprise IT (billing, CRM, SAP/ERP, data warehouse).
* Implement and operate enterprise integration platforms — MuleSoft, IBM webMethods/IIB, TIBCO, Dell Boomi, or Azure Integration Services (platform per candidate specialization).
* Build and maintain REST/SOAP APIs, event-driven architectures, and message queues (Kafka, IBM MQ, RabbitMQ) for real-time and batch data exchange.
* Ensure integration security, reliability, and compliance with NERC CIP and other utility regulatory standards.
* Modernize and troubleshoot legacy-to-modern integrations, including mainframe and SAP PI/PO connections.
* Partner with grid operations, billing, customer service, and data teams to translate business requirements into integration architecture.
* Produce architecture and data-flow documentation sufficient for audit and regulatory review.
Required Qualifications
* 12+ years of middleware/integration engineering experience, with demonstrable delivery in utilities or another regulated industry (financial services, healthcare, energy).
* Hands-on expertise in at least one major enterprise integration platform: MuleSoft, IBM webMethods, TIBCO, Boomi, or Azure Logic Apps/Integration Services.
* Direct experience integrating OT/SCADA or IoT/AMI systems with enterprise IT — non-negotiable for this utility environment.
* Strong API design (REST/SOAP) and event-streaming/message-queue experience (Kafka, RabbitMQ, IBM MQ).
* Working knowledge of regulatory/compliance frameworks relevant to utilities (NERC CIP) or equivalent regulated-industry standards.
* Bachelor’s degree in computer science, Engineering, or related field, or equivalent hands-on experience.
Preferred Qualifications
* SAP PI/PO or SAP Integration Suite experience.
* Cloud integration experience on Azure or AWS.
* Prior direct employment or delivery experience at a utility, energy, or critical-infrastructure company.
 
Interview Requirement — Use Case Presentation
Every candidate must present 3 real-world middleware integration use cases they personally designed or delivered, ideally in a utility or other regulated-industry setting. For each use case, candidates should address:
* Business problem and context — what systems needed to connect and why.
* Technical approach and platform used — architecture, tools, and integration pattern.
* Integration complexity — systems connected, data volume, latency/throughput requirements.