The role

The independent automotive aftermarket runs on data. But that data sits in silos, locked inside each company. The value of connecting it is obvious to everyone. What’s missing is the infrastructure that makes sharing it safe. Kyvera exists to build it. That infrastructure has to exist as running systems: secure, reliable, and simple to connect to. That is your job.

As Platform Lead, you ship, operate, and evolve the core platform of the Kyvera data space. You build the technical foundations for secure, rules-based data exchange between independent, often competing companies: APIs, connectors, data flows, identity and access patterns, security controls, monitoring, and reliable delivery.

This is not a pure design or architecture role. You make pragmatic technical decisions, write production-grade code, operate what you build, and improve the platform continuously based on real usage, partner feedback, and operational evidence. You build greenfield, and you keep it that way: clean foundations, deliberate interfaces, no inherited legacy.

This is a founding role. The engineering culture of Kyvera will largely be the one you establish.

What you’ll do

Ship and operate the core platform capabilities on AWS: identity and access management, encryption, logging, APIs, connectors, and data pipelines.
Establish production-grade engineering from day one: CI/CD, infrastructure as code, automated testing, observability, and operational runbooks.
Own the platform end-to-end: what it technically is, how it runs, and the security and reliability bar it never drops below. The Lead AI Engineer owns the intelligence layer, how data is understood, mapped, and quality-assured. Where the two meet, the boundary is explicit; where they collide, the CTO decides.
Work directly with shareholders and partners on real integration challenges: data formats, mapping, latency, quality, and the edge cases that only exist in the real world.
Make integration easy. Treat the partner and developer experience as a product: onboarding flows, documentation, examples, and reusable patterns that turn connecting to Kyvera from a project into a task.
Design the platform for AI and analytics extensibility without compromising sovereignty, security, or operational reliability.
Let the architecture grow from evidence: turn learnings from shipped increments into better structure over time, avoiding big upfront design while keeping the technical bar high.

Who you are

You have built, shipped, and operated scalable, reliable infrastructure systems in production, and you have stayed around long enough to live with your own decisions.
You are a strong hands-on senior engineer with a track record in backend, platform, or integration-heavy systems.
You have deep AWS expertise: IAM, networking, encryption and KMS, logging, monitoring, and cloud-native delivery.
You have built APIs, connectors, data pipelines, or integration platforms, and messy real-world data does not scare you.
Production engineering is your standard, not your aspiration: automated testing, CI/CD, infrastructure as code, observability, incident response, and operational ownership.
You make pragmatic decisions under uncertainty while holding a high bar for security, reliability, and maintainability, and you can explain your reasoning to teammates, shareholders, and partners alike.
Experience with data exchange standards, identity federation, policy enforcement, consent-based data sharing, or multi-party data ecosystems makes you stronger in this role.
You work fluently in English; German is a plus.

What this role offers

A founding seat in an institution the industry has talked about for years and never built. You shape the core platform of new market infrastructure from day one: not by producing architecture slides, but by shipping, operating, and evolving the systems that let an entire industry collaborate on data securely. What you build here becomes the rails the aftermarket runs on.

You work as part of a small founding team, report directly to the CTO, and operate with founder-level ownership, backed by TecAlliance’s three decades of automotive data expertise, trusted neutrality, and industry relationships.

#J-18808-Ljbffr