Staff Infrastructure Engineer

Responsibilities

• Deployment architecture and blast-radius containment. Redesign deployment so that a mistake in one part of our service cannot block or take down others. Continue to drive our shift toward per-service deploy isolation and functional-area slices that contain failures rather than propagating them across the platform.
• Container footprint and networking.
• Own the ECS and EKS footprint, evaluate broader EKS adoption for AI workloads, and design the next iteration of inter-service network connectivity.
• Capacity and scaling.
• Own capacity for a spiky workload: floors computed ahead of demand rather than chased by reactive scaling, self-deriving from data, with drift caught early.
• Self-serve infrastructure platform.
• Build the Terraform self-serve platform with guardrails so engineering teams own their standard infrastructure changes and Reliability Engineering reviews only the non-standard ones.
• Cloud cost attribution and controls. Stand up per-team cost attribution across AWS, Datadog, and LLM spend. Make infrastructure costs visible and attributable so teams can make informed tradeoffs.
• Python runtime and dependency health.
• Own how the monolith behaves under load: garbage collection, event loop contention, and the runtime limits that bite first.

Languages