NOC Engineer

IONNA LLC•Raleigh-Durham, NC, NC

7h•$80,000 - $90,000•Onsite

About The Position

The NOC Engineer is the front line of quality intelligence for our DC fast-charging network. This role continuously reviews network performance, flags emerging trends, triages issues reported by Operations, Drivers, Automakers and other stakeholders, and validates assumptions with data before conclusions are drawn. Working across the full charging stack (charger hardware and firmware, CPMS backend, payment terminals, OCPP/OCPI/ISO 15118 protocol layers, and our internal data platform) the NOC Engineer performs evidence-based root cause analysis and delivers concise, prioritized feedback into the engineering group for all things quality-related: software bugs, feature gaps, and implementation gaps. The role partners daily with the Charging Quality team, Operations, Data/Technology teams, and our hardware, CPMS, and payment vendors. Mission: Detect and triage the true root cause of issues impacting the customer charging experience, and convert network data into prioritized, actionable engineering feedback. KPIs: 1st Attempt Success Network MTBF / MTTR Time to Detect & Triage (detection lag from first occurrence to validated triage) RCA Quality (validated root causes; vendor/engineering escalations accepted on first submission)

Requirements

Bachelor's degree in engineering, computer science, data science, or related field, or equivalent hands-on experience.
3+ years in a NOC, network operations, reliability, data, or technical support engineering role within relevant industries (EV charging, energy, telecommunications, automotive, SaaS operations, or similar).
Strong SQL and data analysis skills on large telemetry datasets; comfortable in BI/query tools (e.g., Superset) and log analysis platforms (e.g., Kibana/Elastic).
Working knowledge of EV charging protocols and standards (OCPP 1.6J, OCPI, ISO 15118, DIN 70121, IEC 61851) or demonstrated ability to ramp quickly on protocol-level debugging.
Disciplined, evidence-first root cause analysis: every assumption validated with data, alternatives ruled out, and conclusions reproducible.
Excellent written communication: able to compress complex technical findings into short, prioritized, actionable summaries.
Comfort building and using AI-assisted analysis workflows and automation as a daily force multiplier.

Responsibilities

Review daily network performance against baseline (plug success, 1st attempt success, charge success, uptime, error-code frequency) and flag deviations before drivers or partners report them.
Spot patterns across sites, charger models, firmware versions, vehicle OEMs, and failure modes; distinguish systemic regressions from site-local, vehicle-specific, or one-off events.
Track customer-facing trends (repeat-visit failures, new vehicle behavior, Google/Plugshare commentary) and translate them into measurable, ticketed issues.
Monitor the health of automated failure-mode classifiers; flag stale ingestion or classifier regressions that would distort KPIs before trends are misread.
Triage incoming tickets from Operations: validate, complete, or correct initial assumptions with proof from raw data rather than accepting them at face value.
Drive analysis to the true technical root cause using raw telemetry: OCPP message logs, application/server logs, payment terminal data, charger diagnostics, and session logs. Do not stop at surface-level dashboards.
Correlate evidence across independent sources (telemetry, logs, vendor portals, customer reports) and reference the relevant standards (OCPP 1.6J, OCPI, ISO 15118, DIN 70121, IEC 61851).
Document findings concisely on tickets with supporting queries, charts, and log excerpts, plus a short "how-to" so any teammate can retrace and verify the analysis.
Provide concise, prioritized, evidence-backed input to the engineering group: software bugs, feature gaps, and implementation gaps, each with quantified customer impact (sessions affected, KPI impact).
Recommend concrete next steps: lab replication steps, NOC runbook actions, config/firmware review, or field service dispatch.
Validate fixes after release and watch for regressions when vendors ship new software.
File well-evidenced tickets to hardware, CPMS, payment, and OEM partners; follow escalations through to closure.
Surface recurring cross-ticket patterns to the Director of Charging Quality to feed the systemic-issue program and quality strategy.
Propose monitoring, alerting, and classification improvements that shorten detection lag and reduce repeat analysis.