Software Engineer (Infrastructure, Go)

Join our team as a Software Engineer specializing in Infrastructure and Go. You will design and implement the Infrastructure Services for our GPU-as-a-Service platform, building the control plane that translates high-level API calls into real infrastructure actions. You will own the full lifecycle of infrastructure-level services, develop asynchronous workflows, implement and maintain consoles and interfaces, and ensure system reliability. Strong experience in API development, Kubernetes knowledge, and proficiency in Go are required. Familiarity with infrastructure-as-code and GPU server hardware is a plus.

• Design and implement the Infrastructure Services that power the GPU-as-a-Service platform, including the control plane for high-level API calls.
• Own the full lifecycle of the infrastructure-level services, from the Server and MachineType APIs down to the provisioning workflows and reconciliation loops.
• Develop the asynchronous workflows that drive server enrollment, inspection, OS provisioning, and cluster bring-up, exposing durable status to callers.
• Bare-Metal Provisioning: Hands-on experience with bare-metal provisioning flows — BMC/Redfish, PXE/iPXE, image management, and hardware inspection
• API Development: Strong experience designing RESTful APIs or gRPC services. You understand API versioning and gateway patterns
• Kubernetes Knowledge: Deep understanding of Kubernetes primitives and controller/reconciler patterns. You will be interacting with systems like k0rdent, Metal3, and Cluster API to translate high-level API calls into infrastructure actions
• Proficiency in Go (preferred for backend/Kubernetes ecosystem)
• Multi-Tenancy: Experience building platforms where strict data and network isolation between tenants is required
• Asynchronous Systems: Experience building workflow-driven or event-driven systems (e.g., Temporal) where operations are long-running and state must remain consistent across retries and failures
• State Reconciliation: Experience building informers or reconciliation bridges that keep an external datastore consistent with Kubernetes resource state
• Infrastructure-as-Code: Familiarity with Terraform/OpenTofu and GitOps-driven configuration (ArgoCD or Flux)
• Hardware Domain: Familiarity with GPU server hardware, DPUs/NICs, and high-performance datacenter fabrics