Software Engineer, Lambda

• 3+ years of experience working with Go (Golang) or Python in production environments
• 3+ years of experience with bare metal & virtualization hardware management and configuration
• Are comfortable working in Linux environments and debugging issues at the OS, hardware, and networking layers
• Can independently troubleshoot complex systems and communicate effectively across software, infrastructure, and vendor teams

Desirable

• The Compute Software Engineering role plays a key part in the foundation of both the Public and Private Cloud offerings by enabling Bare-Metal and Virtual Machine provisioning
• In this role you will: Develop and integrate workflows for compute instance lifecycle, system health, host and cluster validation, and contribute to and evolve the internal platform tooling, and workflows
• As part of the Compute Engineering team, this position focuses on improving the bare-metal and VM developer and customer experiences, streamlining the software delivery lifecycle, building, testing, and shipping software efficiently and reliably
• The position works closely with various engineering teams across the company and contributes directly to Lambda’s ability to scale engineering productivity, maintain high delivery velocity, and support the company’s continued growth by making the right engineering workflows easier, faster, and more reliable
• We are seeking a Software Engineer with good experience in backbone infrastructure that build, scale and optimize GPU-first cloud infrastructure that enables High Performance Computing and demanding AI workloads
• Design, develop and maintain software for GPU/CPU compute infrastructure with focus on performance, scalability, and reliability
• Implement and develop services for baremetal and VM instancing
• Develop distributed systems for managing and orchestrating compute resources across various SKU’s
• Troubleshoot and debug complex issues in a production and development environment
• On-call and incident ownership
• Collaboration across multiple teams and drive ambiguity in requirements or solutions on RFC’s