Backend Engineer (Go / BMC Protocols) — Infrastructure Automation Platform

Backend Engineer (Go / BMC Protocols) — Infrastructure Automation Platform We are seeking a talented Backend Engineer with strong Go expertise to contribute to our core Server Management Platform. This platform is built for scalable infrastructure automation and device lifecycle management. You will be assigned to one of three key engineering tracks, with ample opportunity for cross-track contributions as the platform evolves: Track A — Discovery & Inventory: Multi-protocol device discovery (Redfish, IPMI, SNMP), hardware inventory APIs, and telemetry pipeline integration. Track B — Provisioning & Monitoring: iPXE / HTTP Boot implementation for Linux/Windows, multi-OS image catalogues, and custom alerting engines. Track C — Lifecycle / Cross-cutting: Console self-update workflows, feature gating/licensing, remote command execution (SSH, WinRM), and KVM (noVNC) integration. What You’ll Do: Contribute to a highly scalable server management platform. Work on multi-protocol integrations and high-performance backend services. Build systems supporting device discovery, provisioning, monitoring, and lifecycle management. Must-Have Technical Skills: Language: 4+ years of strong Go (Golang) experience. (We are also open to strong Python / Java / Rust engineers. APIs & Data: Proficiency with REST & gRPC API design, PostgreSQL 16, and Redis 7. Concurrency & Messaging: Experience with or exposure to NATS JetStream. Debugging & Testing: Expert-level debugging (pprof, dlv, structured logging) and testing expertise (Unit, integration, table-driven tests, and Testcontainers). Nice-to-Have (Bonus): Exposure to Redfish, IPMI, SNMP, or BMC / out-of-band management. Experience with iPXE, cloud-init, or kickstart (Track B). Experience with WebSockets, WinRM, or SSH-streaming (Track C). If you love low-level infrastructure, hardware automation, and building rock-solid backend services in Go, we’d love to hear from you! Please highlight your experience with Go and infrastructure/network protocols in your proposal. Best of Luck