Skip to main content

Staff Software Engineer, Infrastructure

Posted today

secure identityBrooklyn (NY)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: In this role you shape CLEAR’s cloud platform, spanning AWS, Kubernetes, networking, and IaC to enable fast, secure, and scalable software across the company. You’ll drive long-term architecture and standards, building self-service capabilities that reduce toil for engineers. You’ll lead cross-functional initiatives, including production-like staging and AI infrastructure, and mentor teams through design reviews and incident post-mortems. This is a hands-on leadership role focused on reliability, developer velocity, and cost-aware engineering within a mission-driven identity platform. Compensation / Benefits meals and snacks well-being and learning stipend healthcare plans fertility and adoption/surrogacy support flexible time off OneMedical memberships for dependents
Responsibilities: Define and drive the cloud platform architecture across AWS, Kubernetes (EKS), networking, and IaC Lead end-to-end initiatives including staging environments and AI infrastructure from RFC/design to rollout Establish and evolve infrastructure engineering standards (IaC patterns, safe rollout/rollback, observability, security baselines) Act as platform product owner: collect engineer feedback, identify pain points, build self-service tooling Mentor engineers, lead design and incident reviews, translate lessons into system improvements
Key requirements: Deep AWS expertise and multi-account, multi-environment platform design Production-grade software engineering in Python, Java, or similar Experience with Kubernetes/EKS and cluster lifecycle management Proficiency with IaC tools (Pulumi, Terraform, CloudFormation) Observability and incident response capabilities (Datadog) Security tooling exposure (edge/network security, IAM, routing) Strong communication and cross-team collaboration skills Technical leadership beyond own team with RFCs and design reviews mentoring cross-functional collaboration clear communication AWS (VPC design, routing, SGs, load balancing, Route53, IAM) Kubernetes/EKS Istio or service mesh

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.

More like this