Work Arrangement: Onsite 4 Days per Week, Day 1 Onsite
Locals Required
Please use the following JD:
Software Engineer - Charging Vendor Integrations
Team: Charging Infrastructure / Fleet Platform Level: Mid Senior
About the role
Client operates its own charging network and relies on third-party charging providers (e.g., EVgo) spanning multiple hardware manufacturers and vendor platforms. We're building a single vendor gateway.
You'll own that gateway end to end: the protocol clients, the abstraction layer, the onboarding tooling, and the live service contract our fleet systems depend on. This is a backend engineering role at the intersection of messy external APIs, real-time systems, and EV-charging domain protocols. Our stack is Python on the backend and React on the frontend - you'll live primarily in Python, with React for the charger onboarding and operations tooling.
What we're looking for
Strong backend engineering experience building and operating production services and API integrations against unreliable or inconsistent external sources.
Experience designing canonical data models / abstraction layers over heterogeneous third-party systems.
Comfort with event-driven or streaming systems feeding real-time consumers, and the reliability mindset that comes with owning a live service (observability, retries, graceful degradation).
Ability to own a service across the stack - stand it up, deploy it, monitor it - without needing hand-holding on infra.
Skills
Python - primary language; production experience building backend services and API clients (async, typing, and a modern framework such as FastAPI/Django/Flask).
React - for building and maintaining the charger onboarding and operations UI (TypeScript a plus).
API integration - REST/webhooks, plus comfort querying vendor databases (SQL) where no clean API exists.
Data modeling - designing canonical schemas and reconciling inconsistent inputs across sources.
Real-time / event-driven systems - message queues or streaming (e.g., Kafka), and the observability tooling to run them.
Cloud & operations - deploying and monitoring services in a cloud environment (AWS/GCP), containers, CI/CD.
Strong signals (nice to have)
Hands-on experience with OCPP (Open Charge Point Protocol) - charger-to-central-system communication across manufacturers.
Hands-on experience with OCPI (Open Charge Point Interface) - the roaming/interoperator protocol for integrating third-party networks (locations, tariffs, session data, real-time status).
Prior work in EV charging, energy, telematics, IoT device fleets, or other domains that involve normalizing data from many hardware vendors.
DevOps/SRE fluency (IaC, CI/CD, cloud infra, monitoring) as a complement to strong application engineering.