Senior Developer Infrastructure Platform

THE ROLE

We're building the platform that other engineers build on top of. You'll design and ship production services, internal SDKs, and Kubernetes operators that abstract away the complexity of our hybrid infrastructure; spanning Cloud Stack, bare-metal GPU clusters. You write code that other teams depend on, which means you care deeply about API contracts, backward compatibility, and not breaking things quietly.

This is a software engineering role. You'll be expected to own services end-to-end; design, implementation, testing, and the occasional 3am page when something in the critical path breaks.

• Java; not just familiarity. You understand concurrency, JVM internals, and have worked in large codebases with real engineering process.
• Go; production services, not just tooling scripts. You've written Go that other engineers depend on.
• Python; clean, testable, packaged. Not ad-hoc scripts.
• Kubernetes; deep. You've written an operator or custom controller from scratch, not just applied Helm charts.
• Open Stack or Cloud Stack; you can explain how a compute scheduler works, not just 'we used it'.
• gRPC / protobuf; service design, streaming, schema evolution.
• API design discipline; versioning, backward compatibility, contracts. You've had to think about what happens when you break something downstream.
• Hardware awareness; you've debugged at the hypervisor, driver, or bare-metal level at least once.

• GPU compute; CUDA, MIG, vGPU, device plugins, PCIe passthrough, SR-IOV.
• Agentic AI / ML (practitioner level); LLM API integration, agent frameworks (Lang Chain / Llama Index), RAG pipeline design, vector DBs, MLOps fundamentals. You've shipped a system where a model is in the critical path and debugged it when it misbehaved.
• Inference basics; vLLM, Triton, or similar. Enough to understand what the platform needs to support.
• Open Source development experience, on a large project

• A Dev Ops engineer who primarily operates infrastructure and writes pipelines. This role ships software.
• Someone whose Java experience stops at Spring Boot CRUD applications.
• Someone who can t discuss software design trade-offs under interview pressure; not just 'what we did' but 'what we considered and why'.