United States onlyWe’re looking for a Kubernetes engineer who understands the platform at its roots. Someone who understands how Kubernetes actually works, end to end, from API server → scheduler → kubelet → CRI/CNI/CSI.
Edera inserts an isolation layer under Kubernetes, so we need someone who knows where Kubernetes assumes a shared kernel, where those assumptions break, and how kubelet and CRI behave when the world underneath them isn’t the standard container runtime.
This requires real depth — the kind you only get from building or debugging Kubernetes internals.
Key Responsibilities
- Own the deep CRI/kubelet integration for our runtime.
- Debug pathological cluster behavior involving kubelet, scheduler, CRI, and CNI.
- Work with the Hypervisor team to align VM lifecycle with pod semantics.
- Build new orchestration primitives for secure multi-tenancy.
- Be the technical authority for how Kubernetes and Edera interact.
- Help define the right abstractions so Kubernetes “just works” on a VM-per-pod runtime.
Qualifications
- Core Kubernetes Depth:
- Strong understanding of API server storage/watches, informers, and controller reconciliation.
- Deep knowledge of scheduler filtering/scoring and admission chain behavior.
- Experience with GC, finalizers, and ownerReference mechanics under load.
- Expert in pod lifecycle and kubelet expectations.
- Strong understanding of kubelet cgroups, QoS, pressure/eviction signals, and CRI lifecycle.
- Clear mental model of probes, logs, exec/attach flows and node-level networking/storage behavior.
- Runtime Integration Basics:
- Knows where Kubernetes assumes shared PID/net/ipc namespaces.
- Understands how CRI relies on Linux container semantics.
- Familiar with device plugins, topology hints, and resource guarantees.
- Strong understanding of CNI IPAM, routing, and teardown behavior.
Why this matter at Edera
- We introduce a new isolation primitive under Kubernetes.
- Kubelet must trust resource guarantees across VM boundaries.
- Scheduler hints must align with virtualized resources.
- CRI must handle VM boot/teardown/logs/exec cleanly.
- Node behavior must remain fully Kubernetes-compliant.
Why Edera?
We strive to make secure computing simple. Many believe that securing computing is an impossible undertaking. We don't. The products and innovations we release on the way to that end will change everything. We're just getting started.
We operate as a team and exhibit these values and priorities when working together:
Embrace your whole self - We meet each other with humility, curiosity, and authenticity, embracing difficult challenges with courage and dedication to our mission, our humanity, and each other.
We don’t just talk the talk, we walk the walk, together - Diversity is critical to our survival. We value diversity in all its forms, understanding that different perspectives drive our success and those in our community should feel confident in sharing and showing up as their complete selves.
We’ve got your back, for real - We prioritize honest, sincere communication and foster a culture of active gratitude, dignity, and empowerment, where everyone feels safe to contribute and innovate. We believe psychological safety is instrumental in supporting an innovative and successful company and community.
Master your craft, honor your limits - We believe in continuous learning and growth, supporting each other to outfail the competition without fostering a hero culture, relying on teamwork and empathy. We recognize that work is just one part of our lives and celebrate striving toward growth in all areas of life.
We don’t just dream it, we do it - We are dedicated to our mission and are not afraid to tackle difficult challenges, whether in our work, products, or team dynamics.
