Software Engineer, Cloud Infrastructure
benchlingMillbrae (CA)
Software Engineer, Cloud Infrastructure
Posted today
benchlingMillbrae (CA)
SENIORITY
Lead
About the role
Overview:
As a Software Engineer on Benchling’s Infrastructure team, you design, build, and operate the platforms and tooling that enable all engineering teams to ship reliably, securely, and cost-effectively. You own AWS foundations (Kubernetes/EKS, networking, security, observability) and advance infrastructure-as-code and cost governance at scale. You’ll deliver end-to-end platform pieces, from design to production rollout and handoff, shaping the default secure and efficient path for engineers. This role offers impact across a high-scale cloud platform and opportunities to work with AI-powered tooling. Compensation / Benefits equity health dental vision 401(k) + employer match wellness
Responsibilities:
Own projects end-to-end from design to production rollout and handoff Build internal applications, APIs, automation, and tooling (CLIs, Slack apps, serverless, AI-powered assistants) to support cloud platform workflows Own AWS foundation components (Kubernetes/EKS, networking, secrets, PKI) with SLOs, runbooks, and telemetry Advance infrastructure-as-code with Terraform Cloud releases, modules, and policy-as-code guardrails Drive cloud cost governance including cost visibility, anomaly alerts, and cost allocation Contribute to observability tooling, vendor relationships, and monitoring tradeoffs Make architectural decisions and set technical direction across teams Operate production systems with on-call, blameless postmortems, and root-cause analysis to reduce toil Mentor engineers through design reviews and tech plan feedback, maturing tooling and processes Refer to our engineering blog for past work and innovations
Key requirements:
8+ years of software engineering, site reliability, platform, or infrastructure experience Proficiency in Python, Go, or TypeScript Hands-on AWS experience (EC2, EKS, RDS, VPC, IAM, S3) Production experience with infrastructure-as-code (Terraform at scale) Working knowledge of Kubernetes and container platforms Track record of independently delivering complex multi-month projects with technical design docs Architectural decision-making and cross-team alignment Comfort with development/operations collaboration, on-call, and incident response clear written communication collaboration across teams problem-solving under pressure Terraform Cloud and modules AWS services (EC2, EKS, RDS, VPC, IAM, S3) Kubernetes/EKS
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.