Software Engineer, Distributed Simulation

Job description

Job responsibilities

• Design and build the backend services that provision, orchestrate, and tear down distributed test and simulation environments on Kubernetes
• Own significant subsystems of the platform end-to-end — from design through rollout, operation, and iteration with users
• Scale the platform's compute layer as demand grows, including capacity management, performance, and efficient use of expensive resources
• Improve the interfaces and abstractions through which users describe their environments, so they can express complex test topologies without needing to be Kubernetes experts
• Build for the range of environments we deploy into, including cloud and on-premise, along with the release and configuration tooling that makes those deployments repeatable
• Improve reliability and performance of a system whose workloads are heavy and short-lived, including instrumentation, monitoring, and root cause analysis when something breaks
• Raise the engineering bar through design and code review, technical mentorship, and clear technical writing
• Work directly with internal engineering teams, business lines, and external customers to understand where the platform falls short, and turn that into shipped improvements

Job requirements

• 3-6 years of professional software engineering experience
• Computer Science degree or equivalent industry experience
• Strong production experience in a language such as Go, Rust, C++, Java, or Python
• Experience building and operating distributed systems or infrastructure platforms in production, including ownership of the operational side (deployment, monitoring, debugging, on-call)
• Hands-on Kubernetes experience with a deep understanding of its internals and components, such as as controllers, operators, and custom resources
• Experience with infrastructure as code and modern build and deployment tooling (e.g. Terraform, Helm, CI/CD systems)
• Demonstrated ability to own an ambiguous, cross-cutting project end-to-end and drive it to production
• Strong written and verbal communication — you can write a design document that a skeptical reader can evaluate