Sr Tech Infra Program Manager, OMHS Software, Controls, and Science

This isn't a program management role where you inherit a platform and keep it running. You will build the technical infrastructure that six software products don't have yet: the cloud footprint, environments, deployment pipelines, and guardrails that decide whether Amazon's next buildings launch on a platform they can trust, on commissioning dates that cannot move. We're building the software, controls, and intelligence layer that powers Amazon's automation infrastructure, deployed across hundreds of buildings processing millions of packages daily. Our products span industrial controls, unified SCADA, computer vision, AI-powered design automation, standardized operational metrics, and predictive operations intelligence. Every one of them runs on shared infrastructure: AWS accounts and cost that scale with every site we launch, build and release pipelines, non-production and production environments, telemetry, and the security guardrails that let us launch safely at the edge of the network. Today each product reinvents that plumbing for itself. You will make it a platform. You will get ahead of the launches before they arrive. When a new sortation architecture takes first access in November and cannot slip, you'll have stood up its environments, its build-and-deploy path, and its readiness gates months ahead. You'll size and govern the AWS spend before a new building generation multiplies it, standardize how products build, deploy, and roll back so the next product inherits a platform instead of building one, and run the security and compliance programs that keep us safe while we move fast. You'll partner directly with engineering managers, product managers, security, and finance to keep the infrastructure ahead of the products it serves. Impact at scale: The infrastructure programs you run will decide whether Amazon's next buildings launch on a platform that is secure, observable, and affordable from day one, and will become the standard this organization uses to ship every product that follows. Key job responsibilities Footprint & Cost • Own the SCS AWS footprint as a program: account structure, environments, and a per-site cost model that scales linearly as each new building comes online • Build and defend the infrastructure cost forecast (IMR / CAPEX and discretionary AWS spend) before a new building generation multiplies it • Hold products to a per-site unit-economics baseline, and drive the compute-siting decisions (for example, AWS Outpost versus on-prem for real-time control) where cost and capability trade off • Reconcile forecast against actual spend and surface variance to leadership before it becomes a budget event Environments, Build & Release • Own the standard path from code to production: build pipelines, release cadence, and non-production, beta, and production environments across the portfolio • Stand up the environments and deployment infrastructure a new launch needs ahead of its commissioning date, including pre-production and hardware-in-the-loop validation labs where cybersecurity patches, OS updates, and infrastructure changes are proven before field rollout • Standardize how products build, deploy, and roll back (config-managed, version-controlled, and scoped from a single device up to an entire region) so a shared-library change does not mean a hand-managed redeploy across every box at every site • Drive the deployment tooling and offline-commissioning capability that lets a product go live without waiting on the site's IT-network timeline Observability, Security & Compliance • Define the telemetry, logging, and monitoring baseline so every product and environment is observable from launch • Partner with security and AppSec to run compliance and risk-remediation programs (SAS, policy-engine, dependency and version-set health) to closure • Own the guardrails for internally built tools and services (authentication, access, secrets, and data governance) so nothing ships to