Staff Software Engineer, Ironclad

• 8+ years in SRE, DevOps, or infrastructure engineering, including experience as a technical lead for business-critical systems
• 5+ years developing and maintaining production software in TypeScript or Python, including tools and services
• Deep experience operating Kubernetes in production, including troubleshooting scheduling, networking, and resource issues at scale
• Deep hands-on experience with GCP, AWS, or Azure; GCP experience is preferred
• Production experience with both relational and NoSQL databases, such as PostgreSQL, MongoDB, or Redis, including query and index tuning, replication, monitoring, and scaling under load
• Hands-on experience with infrastructure as code, CI/CD, and GitOps tooling, such as Terraform or Pulumi, CircleCI, and Argo CD
• A strong understanding of distributed systems, cloud storage architecture, and backup and recovery
• Experience using AI coding tools to improve engineering workflows, with sound judgment about when to use them and how to validate their output
• Strong troubleshooting skills, including the ability to move from a vague symptom to a root cause under pressure
• Clear written and verbal communication, with design documents and incident writeups that help teams make decisions and take action
• A track record of leading through influence and helping teams you don’t manage adopt better practices
• A collaborative approach: you deliver meaningful improvements, share credit, and help others succeed

Desirable

• We’re looking for a Staff Site Reliability Engineer to help shape the cloud platform that powers Ironclad
• You’ll join an experienced SRE team, work across engineering to identify reliability and scaling challenges, and lead solutions from design through production
• Shape our direction. Help set the technical direction for SRE and the cloud platform. Partner with teams across Ironclad to identify needs, prioritize improvements, and build a roadmap for reliability, capacity, and platform capabilities
• Solve the whole problem. Identify reliability risks before they become incidents. Design and deliver changes that reduce risk and prevent recurring failures, carrying the work through to production
• Lead architectural decisions. Make informed tradeoffs across security, scalability, and performance. Document decisions so teams can understand the reasoning and build on it
• Keep our data layer fast and reliable. Contracts live in our databases, so database reliability is business reliability. Monitor, tune, and scale our relational and NoSQL systems, addressing capacity and performance issues before they affect customers
• Reduce toil through automation. Improve how we build, test, deploy, monitor, and recover. Prioritize automation that prevents errors and makes operations repeatable
• Strengthen our SRE practices. Bring fresh perspective to SLOs, incident response, postmortems, and capacity planning. Build on what works and close the gaps
• Own resilience end to end. Design and test backup, recovery, and disaster recovery capabilities, and strengthen data durability across storage and distributed systems
• Share ownership of production reliability. Participate in the SRE on-call rotation, including coverage outside business hours. Respond to production incidents, lead complex investigations, and improve alerting, runbooks, and automation to reduce recurring incidents and on-call toil
• Help the team grow. Mentor engineers, review designs and code, and share knowledge that makes the whole team more effective
• Work across teams. Partner with product engineering, security, support, and customer-facing teams. Join customer escalations when needed and investigate issues across unfamiliar parts of the product