Staff Software Engineer (Developer Productivity)

Join Ironclad as a Staff or Senior Staff Software Engineer on the Developer Productivity team. You will lead improvements in how Ironclad engineers build, test, and ship software. Your responsibilities will include shaping the team's technical direction, mentoring engineers, and supporting the tools we own. You will work closely with SRE and other engineering teams to identify problems and prioritize improvements. The ideal candidate will have deep experience with JavaScript/TypeScript build and test tools, strong programming skills, and production experience with Kubernetes and containers.

• Lead improvements to how Ironclad engineers build, test, and ship software, focusing on local development tooling, build and test systems, release automation, and the Backstage developer portal.
• Shape the team’s technical direction and roadmap by identifying problems, defining solutions, and leading delivery and adoption of practical tools and features.
• Mentor engineers, share responsibility for supporting the tools owned by the team, and participate in technical discussions to guide the team’s direction.

• We’re looking for a hands-on technical leader with deep JavaScript/Typescript build and test experience, a background in SRE or infrastructure, and a track record of delivering projects that other teams adopt
• Alignment with Ironclad’s values: drive, intent, integrity, and empathy
• Deep experience with JavaScript and TypeScript build and test tools, such as webpack, Jest, or Vitest, including diagnosing slow builds and flaky tests at scale
• Staff: 8+ years of software engineering experience. Senior Staff: 12+ years. For either level, at least 3 years in SRE, infrastructure, build systems, CI/CD, or developer tooling
• Strong programming skills in TypeScript, Go or Python, and comfort with shell scripting
• Experience leading technical projects that required adoption across teams, as a tech lead or engineering manager while staying hands-on
• Clear written communication, including design documents, technical proposals, and migration guides engineers can follow
• Production experience with Kubernetes and containers on GCP, AWS, or Azure, and CI systems such as CircleCI or GitHub Actions
• Bazel or Nx, particularly migrations of JavaScript or TypeScript monorepos
• Kargo, Argo CD, or other GitOps tooling
• Infrastructure as code, such as Terraform or Pulumi
• Building Backstage plugins