Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
DynaChrg Inc. in Calabasas, CA is seeking a senior EV charging engineer to own the charger-facing integration layer of the EVES platform. You will evaluate, onboard, and test charger interoperability, troubleshoot complex OCPP flows, and support production integration with CSMS teams.
Ideal candidates have 5+ years in EV charging product or systems integration and hands-on OCPP 1.6J experience, plus the ability to work on-site in Calabasas.
DynaChrg Inc.
Location: Calabasas, California — On-site
Employment Type: Full-Time
DynaChrg develops intelligent EV charging and energy-management technology. Our EVES™ platform enables multi-vendor charger management, real-time monitoring, charging transactions, energy optimization, dynamic charging control, and grid-aware services.
DynaChrg is seeking a senior-level EV charging engineer with deep, hands‑on experience integrating commercial EV charging equipment with Charging Station Management Systems (CSMS) using OCPP.
This role owns the charger‑facing technical integration layer of EVES™, including EVSE evaluation, onboarding, interoperability testing, qualification, validation, troubleshooting, and production support.
This is a systems integration and interoperability role—not an EV charging construction, installation, or electrical‑infrastructure design role.
Experience primarily in charger installation, site deployment, construction, electrical design, utility coordination, power systems, or general commissioning does NOT substitute for direct EVSE-to-CSMS/OCPP integration experience.
Experience with multiple EVSE manufacturers, both AC Level 2 and DC fast charging, OCPP 2.0.1, Wireshark, charger firmware qualification, automated protocol testing, hardware‑in‑the‑loop testing, TLS/mTLS, smart charging, ISO 15118, Plug & Charge, PKI, OCPI, or V2G.
Candidates must be prepared to discuss specific work they personally performed, including EVSE manufacturers/models, CSMS platforms, OCPP versions used in production, a charger‑to‑CSMS integration they owned, OCPP messages analyzed, and a real interoperability or firmware/networking issue they diagnosed and resolved.