Hire DERMS engineers and OMS specialists for utility programs

What OMS and DERMS staffing is not

OMS is not a call-center CRM with a map widget. DERMS is not a generic IoT platform. We will not staff live dispatch, live switching authority, or a replacement outage system. FLISR, AMI, CIS extracts, and hosting capacity appear as context on requisitions, we use those words to screen, not to claim we own your grid applications.

We also keep OMS/DERMS screens separate from ADMS architecture screens. They share data. They are not one resume. If you need both, say so on the hire form and we return two shortlists rather than one confused hybrid.

OMS, DERMS, ADMS, and GIS adjacency

Related terms a serious candidate should survive: ADMS, SCADA, CIS extracts, AMI, crew mobile, predicted outages, switching, DER limits, hosting capacity, and GIS connectivity. Vendors we hear weekly: AutoGrid, OATI, EnergyHub, Schneider, GE, Oracle, OSI, and custom DERMS depending on the IOU. Pair this role with utility GIS engineers, ADMS engineers, and GIS/OMS/ADMS data validation when the defect is the model, not the Java service.

QA is often the faster commercial entry: outage and switching test packs, DER telemetry replay in the lab, exception queues before go-live. That is still OMS/DERMS work. It is not live storm desk coverage.

Who we place on OMS and DERMS programs

Typical fills: OMS application analysts, OMS solution-lead contractors, outage testers, DERMS data engineers, interconnection-adjacent specialists who can read a queue, and hybrid ADMS/OMS configuration people who already survived one vendor upgrade. Integrators in Raleigh, Charlotte, Atlanta, Overland Park, Renton, and Columbus hire surge capacity. IOUs hire contractors who will not treat storm season as a software demo. We do not staff a live storm desk or a grid-operations industry-expert advisory seat.

Anonymous profiles first. No identity documents on the public apply form. Dedicated teams get a U.S. domain lead. specialist matching still applies when names exist; DERMS architects can be thinner than OMS testers.

OMS and DERMS markets we cover

Link OMS/DERMS hiring to Raleigh and Charlotte for Duke, Richmond and Arlington for Dominion, Los Angeles and San Diego for California IOU programs, Sacramento for SMUD/DER, Atlanta for Southern Company applications, Dallas for Oncor-scale OMS beside ADMS, Miami and Fort Lauderdale for FPL storm programs, Seattle and Renton for Puget Sound consulting and municipal OMS, Portland for PGE, and Columbus for AEP. St. Louis Ameren work often wants ADMS/OMS testers rather than a net-new DERMS product owner.

Smaller cities still search: Chapel Hill and Durham overflow from the Triangle, Sandy Springs and Marietta from north Atlanta vendor campuses, Leesburg and Ashburn when data-center load collides with interconnection stories. Use those city pages. Do not clone this role onto a hundred URLs.

OMS and DERMS screening notes

A useful OMS shortlist can explain predicted versus actual outage, crew mobile constraints, and how CIS extracts join the electric model. A useful DERMS shortlist can explain interconnection queues, operating limits, and the telemetry contract back into ADMS or SCADA. If the candidate only knows Salesforce-style tickets or a generic IoT cloud, the interview is already over. PositiveGridWorks will not relabel that resume as grid modernization talent.

Tell us whether the seat is tester, application analyst, or vendor configuration. Duke, Dominion, Southern Company, SCE, SMUD, and Oncor-adjacent programs do not share one dialect. We identify suitable profiles when the brief names the utility and the vendor. Pair OMS/DERMS hiring with GIS/OMS/ADMS data validation when the defect is connectivity or customers, not the Java service bus.

Define outage and DER outcomes before hiring

OMS and DERMS buying starts with separate business outcomes. An OMS workstream may focus on outage prediction, customer association, crew workflows, estimated restoration times, switching coordination, storm testing, or integration with AMI and CIS. A DERMS workstream may focus on DER visibility, enrollment, telemetry normalization, forecasting, operating envelopes, dispatch coordination, hosting-capacity inputs, or interconnection workflows. Put the required outcome, platform, utility operating model, and milestone in the brief.

For OMS, describe the event lifecycle that must work: trouble calls, predicted device and customer outages, crew assignment, nested outages, restoration verification, and post-event reporting. For DERMS, identify resource types, aggregators, telemetry cadence, command and acknowledgment expectations, and the relationship to ADMS, SCADA, or distribution planning. Strong candidates can discuss IEEE 1547 context, inverter capabilities, operating limits, aggregation, and fail-safe behavior without claiming authority to dispatch assets outside an approved process.

Platform names improve matching only when responsibilities are clear. AutoGrid, OATI, EnergyHub, Schneider Electric, GE Vernova, Oracle, and AspenTech OSI can appear in adjacent programs. We distinguish product configuration, business analysis, interface engineering, data migration, test leadership, and utility-side ownership. Acceptance tests belong in authorized environments. PositiveGridWorks can staff the analysis and evidence work. Live dispatch, switching authority, and final production acceptance remain with the utility.

Choose staffing based on the bottleneck: functional analyst, integration engineer, data specialist, QA lead, or solution architect. Tell us the decisions the seat owns, expected artifacts, on-site needs, and target release.

Specialist matching for OMS and DERMS talent

Use the hire form, name OMS or DERMS in the role field, and list the vendor plus whether you need testers first. We identify suitable profiles. If you need a squad for a model-load season, use the project brief and ask for GIS/OMS/ADMS data validation next to this role.