Software Engineer, Infrastructure

Sixfold•New York, NY

4d•$155,000 - $185,000•Hybrid

About The Position

Sixfold is building AI agents that understand risk the way a 20-year veteran underwriter does. Not summaries or flags, but systems that make real decisions on billions in premium for some of the world's largest carriers. AI is the product and the workflow. In this role, you will build and run the cloud infrastructure, Kubernetes environments, deployment tooling, and observability systems that enable Sixfold's engineers to develop, release, and operate our products. You'll join Central Tech, the small team responsible for Sixfold's shared infrastructure and internal engineering tools. We are moving our products onto a modern Kubernetes and GitOps setup, simplifying older AWS and Terraform infrastructure, and improving how product teams deploy and operate their services. The core pieces are in place, but there is still plenty to build and improve. Product engineers own and operate their applications from prototype through production. Our job is to give them reliable infrastructure, deployment workflows, observability tooling, and guidance so they can self-service all their development needs. When the same problem comes up more than once, we look for a reusable solution. We do not expect you to know every part of the system on day one. You will begin with a defined area and take on more ownership as you learn. Our stack includes Terraform, Azure and AWS, Kubernetes, Helm, Argo CD, GitHub Actions, and Datadog.

Requirements

3+ years of professional software engineering experience, including 2+ years working on infrastructure, platform engineering, DevOps, or SRE problems.
Run production workloads on Kubernetes and can troubleshoot common problems with Pods, Deployments, Services, ConfigMaps, Secrets, Jobs, and Helm charts.
Used Terraform in production, or have strong experience with another Infrastructure as Code tool and can ramp up quickly.
Know your way around at least one major cloud provider and can reason about networking, IAM, secrets, scaling, security, and safe rollouts.
Built or maintained CI/CD or GitOps workflows.
Can read, debug, and write code in at least one general-purpose programming language.
Participated in an on-call rotation and used metrics, logs, traces, alerts, and dashboards to investigate production issues.
Take responsibility for follow-up work and use postmortems to improve the system rather than assign blame.
Use Codex or Claude Code in your day-to-day engineering work.
Proactive and comfortable working through ambiguous problems. Clarify the goal with the engineers involved, propose a practical solution, explain tradeoffs, and surface risks early.
Favor the simplest approach that meets the need, add complexity only when scale, security, reliability, or compliance requires it, and remain responsible for what you ship in production.

Nice To Haves

Go experience is a plus.

Responsibilities

Build and operate our infrastructure. Use Terraform to provision AWS and Azure resources. Manage Kubernetes workloads, Helm charts, Argo CD configuration, GitHub Actions workflows, and the shared services that support our applications. Your work may touch infrastructure, GitOps, and application repositories, and you will follow changes all the way through production.
Make it easier for product teams to ship. Work directly with engineers to understand where deployments and infrastructure changes are slow or confusing. Turn repeated work into reusable patterns, workflows, documentation, or tools that teams can self-service with.
Improve reliability and incident response. Use Datadog dashboards, alerts, logs, and traces to find problems and improve visibility. Plan changes with rollback in mind. Participate in a 24/7 on-call rotation one week at a time; when paged, investigate, communicate clearly, and follow through on fixes and postmortems when needed.
Help simplify our legacy infrastructure. Upgrade our older services to use modern best practices, consolidate Terraform repositories and AWS accounts where it makes sense, and remove duplicated or fragile systems without weakening security or isolation.