Amazon Web Services
Apr 2025 — PresentSoftware Development Engineer II
Bellevue, WA
Moved to AWS to take on larger, multi-team programs with visible customer impact — region launches, public-API architecture, and the kind of operational work that unlocks whole orgs. The through-line is stepping into ambiguous problems and shipping them cleanly.
- Tech lead on an eight-service sovereign-cloud region launch, inherited at month two of three. Built a team of five engineers from scratch, drove cross-org alignment through the principal-engineer and senior-manager layers, and unblocked dependencies across five platform teams. Personally launched the most architecturally complex service in the set. All eight shipped on deadline with validated readiness reviews — available from day one of the region’s public launch.
- End-to-end owner on a multi-year authorization redesign for a public AWS API. Evaluated three architectural approaches, implemented a Lambda-authorizer strategy with partial authorization for overlapping API surface, and drove a Priority-1 product-security engagement through penetration testing to full sign-off. Rolled out in 20% increments with zero customer regression; unblocked three dependent programs.
- Self-selected and closed out a stack of operational risk nobody had owned — migrated long-lived credentials off the legacy auth scheme across 16+ accounts and 7 partitions (all risks resolved before escalation), modernized two CDK pipelines to the latest region-build patterns (one-click multi-partition deploys), and fixed an alarm-replication gap silently hiding on-call signal for months. On-call incident response dropped from hours to minutes.
- Currently building agentic-AI utilities on Bedrock and SageMaker to automate repetitive operational-review and readiness work for the team.
