Infrastructure Engineer

Required

• The core requirement is ownership. We view the Infrastructure vertical as a product with a roadmap, and the person in this seat will be the one to drive it full-time. That expectation starts small and grows, but this is not a role with a well defined queue of tickets pre-scoped for execution.
• Your users are internal. They're technical but they aren't infrastructure experts, so they will need to understand the rationale for any changes and improvements we’re making to our infrastructure. The people who will succeed here treats other engineers as customers while advocating for improvements to our infrastructure. They automate recurring work, maintain a high bar for reliability and security, and prioritize projects based on the needs of the firm. They'd rather ship the simple solution a 50-person firm needs than build for scale we don't have. They surface tradeoffs in their work, rather than sharing a solution absent the context that resulted in that recommendation.
• Prior skills and experiences that matter for this role include designing, implementing, and maintaining the following services:
• Production Kubernetes (like EKS) and Terraform
• GitOps workflows (like Flux, Atlantis)
• Docker, deeply enough to debug a container problem down through the OS and network layers
• Cloud networking, secrets, certificates, and secure service-to-service connectivity
• Self-service tooling for other engineers