What you’ll own Fig’s platform runs inside the security stacks of enterprise customers, processing live detection and telemetry data from SIEM, EDR, and SOAR systems at real scale. Until now, infrastructure has been built and carried by the founding engineering team alongside everything else. You will be the first dedicated owner of it. That means designing Fig’s cloud foundation across GCP and AWS, building the deployment, scaling, and observability layers from the ground up, and setting the standards the rest of engineering builds on. It also means holding a bar that most startups can defer and Fig cannot: we sell to security teams who audit their vendors seriously, so how we run our own infrastructure is part of how we win. This is a hands-on senior role with real architectural authority, and as engineering grows you become the person others learn cloud and infrastructure from. What you’ll be doing Multi-cloud architecture: Own the design and implementation of Fig’s multi-cloud architecture across GCP and AWS, including the cross-cloud standards, boundaries, and tradeoffs that keep two providers from becoming twice the complexity. Infrastructure as code: Build and maintain the entire environment in Terraform, so infrastructure is reviewable, reproducible, and scales without a person in the loop. Deployment pipelines from scratch: Create the CI/CD foundation that lets a small team ship quickly and safely, with the testing, gating, and rollback paths that make fast releases boring rather than risky. Kubernetes at data scale: Run and scale the Kubernetes and containerized workloads behind Fig’s security data processing, where volume, latency, and cost pressure all show up at once. Security of our own stack: Own identity, access, secrets, network boundaries, and infrastructure hardening to a standard that holds up under customer security review. Reliability and visibility: Build the logging, monitoring, and alerting layer that tells us something is wrong before a customer does, and make on-call sustainable as the system grows. Technical direction: Partner directly with the founding engineering team on architectural decisions, and raise the infrastructure and cloud fluency of every engineer who joins after you. Requirements: What you’ll need Senior infrastructure depth: 7+ years as a DevOps or Site Reliability Engineer, with production systems you built and carried, not only inherited. Multi-cloud experience: Hands-on work with core services across both GCP (GCE, GKE, Cloud Storage, VPC) and AWS (EC2, EKS, S3, RDS), and clear judgment on when running in two clouds is worth the cost. Kubernetes and containers: Strong production experience with Docker and Kubernetes, including scaling, resource management, and debugging clusters under real load. Infrastructure as code: Proven Terraform experience (or Pulumi) in complex, multi-provider environments, with a preference for codified over manual. Pipelines and scripting: Built CI/CD from zero with GitHub Actions, GitLab CI, or Jenkins, backed by strong Python or Bash. Security instincts: A DevSecOps mindset and real exposure to security best practices. Background in a cybersecurity or otherwise security-sensitive environment is a strong advantage. 0-to-1 ownership: Comfortable being the first and only person in a domain, making decisions without an existing playbook, and staying close to the work while setting direction for others.
