> Markdown version of [/jobs/ext/4628279-platform-engineer](https://www.wearedevelopers.com/jobs/ext/4628279-platform-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Platform Engineer - **Company:** Volta Inc. - **Location:** Palo Alto, CA, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Clean Code Principles, Java (Programming Language), Application Programming Interfaces (APIs), Agile Methodology, Border Gateway Protocol, C Sharp (Programming Language), C++ (Programming Language), Software as a Service, Code Review, Continuous Integration, Software Debugging, Linux, Distributed Data Store, Distributed Systems, Infrastructure as a Service (IaaS), Python (Programming Language), Network Control, Networking Basics, Object-Oriented Software Development, Platform as a Service (PAAS), Performance Tuning, Scrum Methodology, Remote Direct Memory Access, Prometheus, Software Engineering, System Programming, Systems Integration, Management of Software Versions, Ceph (Software), Datadog, Data Logging, High Performance Computing, Grafana, Backend, Kubernetes, Bare Metal, Hardware Infrastructure, Software Version Control, Serverless Computing - **Published:** November 7, 2026 - **Apply:** https://www.juju.com/job/28_25303_433f98fa430828f266a326eab6b274b4 ## About the Role * 3+ years of software engineering experience, with a meaningful portion spent on infrastructure or platform systems. * Strong backend or systems programming experience in a production environment. Our working languages are Python, Go, and Rust; we welcome strong engineers from other compiled or object-oriented languages (for example C++, C#, or Java) who are ready to work across our stack as it evolves. * Solid understanding of Kubernetes internals: the control loop model, CRDs, controllers and operators, and reliable reconciliation logic. * Comfortable working close to the infrastructure layer: Linux, networking fundamentals, and distributed systems behavior. * Experience designing, building, and versioning production-grade APIs or service interfaces that other teams depend on, including disciplined handling of breaking changes and backward compatibility. * Experience operating what you build: debugging production systems, and taking part in on-call or incident response. * Strong engineering fundamentals: clean code, testing, version control, code review, and CI/CD practices. * Fluency with AI-assisted development: agentic CLI tools, IDE assistants, and orchestrating multiple coding agents through MCP, skills, or APIs to amplify delivery. Nice to Have (But Not Essential) None of these are required. Several map to specific teams, so strength in one or more helps us match you to the right one: * Depth in Go or Rust beyond working proficiency. * Familiarity with confidential computing technologies: TEEs, AMD SEV, Intel TDX, or Confidential Containers (CoCo). * Experience integrating security requirements into platform or infrastructure systems. * Familiarity with high-performance networking: overlay protocols, BGP, RDMA, or packet-processing frameworks. * Hands-on experience with distributed storage systems (Ceph or similar) at an engineering level. * Background building Kubernetes operators using frameworks such as Kopf, controller-runtime, or similar. * Experience with observability tooling: Prometheus, Grafana, OpenTelemetry, or structured logging in distributed systems. * Experience building SaaS or PaaS layers on top of an IaaS platform. * Exposure to serverless or inference serving infrastructure. * Exposure to GPU infrastructure or HPC environments. * Experience working distributed across time zones with counterparts in other regions. REQ-0 ## Description * Design and implement Kubernetes operators and controllers that manage the lifecycle of platform resources. * Work closely with the product team to turn roadmap requirements into the platform capabilities that support them. * Collaborate with the bring-up teams to identify operational pain points and turn them into scalable platform features. * Integrate security guidance from the security engineering team into platform-level controls, and remediate findings at the platform layer. * Treat observability as a platform concern: instrument services, define meaningful metrics, and build tooling that gives the team visibility into platform health. * Own the services you build in production, including participation in an on-call rotation, incident response, and the follow-up work that closes structural gaps rather than only the immediate issue. * Hold to clean interface and versioning practice on anything other teams or customers depend on, including disciplined handling of breaking changes. * Participate in code review, technical design discussions, and cross-team collaboration in an Agile (Kanban or Scrum) environment. Depending on your team and background, you will go deep in some of the following: * Control plane and APIs: improve and extend the API layer between user-facing services and the underlying platform, with disciplined versioning and backward compatibility. * Compute: build and operate the lifecycle of virtualized and bare metal compute resources. * Storage: provisioning workflows, attachment reliability, performance tuning, and failure handling. * Confidential computing: build and extend confidential computing capabilities across the stack, from secure bare metal and confidential VMs to Confidential Containers (CoCo). * Customer-facing services: the platform surfaces customers interact with directly, including the APIs and interfaces through which they consume capacity, working alongside product and UX.