At go-e, we are shaping the future of e-mobility and the global energy transition with passion, speed, and technical excellence. Operating in an environment defined by rapid growth and breakthrough innovation, we combine regional strength with international reach to build intelligent, reliable energy solutions.

Our IoT infrastructure operates at massive scale:

100+ PB of raw telemetry data stored across our infrastructure
250k+ requests per second flat, not a peak; and growing
130+ TB of network traffic managed monthly

To drive our next phase of platform scale, we are seeking a Senior Backend Engineer (m/f/x). In this role, you will lead high-impact architectural initiatives: modernization of our API ecosystem, architecting privacy-first telemetry solutions for enterprise markets, and establishing a unified, Zero Trust security model across all our backend systems.

Your area of responsibility

Scale the backend and its data: Own the scaling strategy for Go and TypeScript services handling 250k+ requests per second, optimize ingestion pipelines into ClickHouse and PostgreSQL, and design partitioning, retention, and hot/cold tiering for the multi-year telemetry dataset.
Unify the API landscape: Lead the evolution of go-e’s APIs into one long-term platform for internal microservices and external B2B/B2C users, with contract-first design (OpenAPI, gRPC, GraphQL), clear governance, and backward-compatible versioning.
Build the API gateway: Design high-performance routing, rate-limiting, and transformation layers that securely expose core services under strict authorization policies.
Own backend security: Act as the architectural owner for identity, authentication, and authorization as a shared foundation across APIs, telemetry, CI/CD, and observability, including RBAC, fine-grained access policies, Zero Trust service-to-service communication, and tenant isolation.
Create a white-label telemetry platform: Architect a modular ingestion and processing engine that runs multi-region, single-tenant, or at the edge to meet data residency requirements, and can be rebranded and configured for OEM and partner solutions.
Lead technically: Drive key architectural decisions through RFCs and ADRs, build consensus across backend, mobile, and other teams, and mentor senior engineers through coaching, architectural code reviews, and delegated ownership of core sub-systems.)

What you bring

Proven Senior-Level Leadership: Track record as a Strong Senior Engineer driving cross-cutting architectural vision across multiple teams and complex domains.
Security & Identity Mastery: Extensive experience engineering distributed security models, including OAuth2/OIDC, PKI, JWT, fine-grained authorization, and RBAC within high-scale platforms.
Unified API Design Expertise: Strong experience designing, deploying, and maintaining unified, public-facing and internal API ecosystems with strict backward-compatibility and security requirements.
Multi-Tenant & Sovereign System Design: Hands-on experience architecting multi-tenant or white-label platforms, with direct knowledge of data sovereignty constraints, localized data storage, and regional data compliance (e.g., GDPR, local residency laws).
High-Throughput Backend Mastery: Expert-level mastery of Go and TypeScript/Node.js in high-concurrency, event-driven distributed environments.
Data Engineering at Scale: Deep experience with OLAP-optimized databases (e.g. ClickHouse) and high-scale relational datastores (PostgreSQL), emphasizing high-write ingestion, query tuning, and schema migration strategies.

It would be even better if you have

IoT & Fleet Management Protocols: Direct experience with EV/IoT standards such as OCPP, MQTT, or ISO 15118, paired with high-volume device telemetry processing.
Edge & Hybrid Deployments: Experience designing applications that deploy seamlessly across public cloud infrastructure (AWS/GCP), localized private clouds, and edge computing environments.
Applied Domain-Driven Design (DDD). Proven track record applying strategic and tactical DDD to untangle complex business and physical domains: establishing bounded contexts, codifying ubiquitous language across product and engineering, and defining clean interfaces that decouple services.