Senior Software Engineer
Outcomes (formerly Fuse by Cardinal Health)
Columbus, OH
2021 – Present
Senior Software Engineer (2024–Present) · Software Engineer II (2023–2024) · Sr. Analyst (2021–2023) · Intern (Summer 2020)
Specialty Medication Platform: Azure-to-AWS Migration Q2 2026
- Migrated a production specialty-medication platform from Azure to AWS with zero data loss. First ECS workload in the new environment, so its deployment and ingress patterns had to be built alongside the migration, coordinated across developers, contractors, and leadership.
- Cut over production DNS for five domains inside an 8.5-hour maintenance window, diagnosing and resolving issues live.
- Isolated the new platform in its own AWS environment for security, then built the cross-platform API path back with API Gateway, PrivateLink, and VPC endpoints, including a Java Lambda authorizer bridging Cognito and Keycloak so services could authenticate across both.
- Kept source and target databases in sync with AWS DMS over a VPN for the duration of the migration.
- Traced cross-AZ routing failures and missing routes through a multi-layer path (Transit Gateway to Palo Alto firewall to VPN) to deliver state vaccine-registry connectivity.
Developer Platform for a New Pharmacy Management System Q1 2026
- Stood up a complete developer platform in weeks (Concourse CI/CD, HashiCorp Vault, ArgoCD, ECR, Nexus, EKS compute) in an environment with no DevOps tooling, unblocking the launch of a new pharmacy management system. It became the standard platform other teams there now use.
- Cut new-team onboarding from weeks to a few days with repeatable standards: repository conventions, ArgoCD RBAC, Vault secret patterns, and documentation. Onboarded multiple teams, including a large offshore contractor group.
- Extended the company's internal CI/CD pipeline framework (Java) to support new repository structures, keeping every existing pipeline working unchanged.
Cloud Consolidation 2025
- Migrated roughly 40 microservices from GKE to EKS with no downtime, using a repeatable migration pattern that aligned each service to the platform's deployment and secrets-management standards.
- Led the infrastructure work consolidating several product lines from GCP and legacy AWS into one AWS environment, with no downtime during the moves.
- Designed a centralized inspection network (hub-and-spoke over Transit Gateway) routing cross-environment traffic through a dedicated inspection VPC with AWS Network Firewall (Suricata, strict-order, default-drop) and Palo Alto integration, built as an extensible pattern so new accounts and connections plug in the same way.
- Built custom VPC architectures for workloads with unusual networking needs, including an internet-facing telephony/SIP platform (dual-firewall) and a pharmacy-partner integration reached over VPN.
- Automated Security Hub findings into Jira tickets so they get tracked and resolved, and review Security Hub and Ox findings each week, including issues raised on pull requests.
Cloud Platform Buildout: Cardinal Health Separation 2023–2024
- Built the cloud platform Outcomes moved onto when it separated from Cardinal Health, delivered under a fixed contractual deadline with no production downtime. It remains the foundational environment the company runs on today.
- Provisioned and bootstrapped 100+ AWS accounts with Control Tower and SCPs, standardizing the baseline each account starts with: Terraform state, networking, and IAM roles for developer and Atlantis access.
- Stood up the eight production EKS clusters running the Outcomes microservices platform (Karpenter for node provisioning, ArgoCD on Fargate for GitOps) and translated the teams' existing Pivotal Cloud Foundry applications into Kubernetes patterns. Primary maintainer of those clusters since, holding costs down through right-sizing, snapshot cleanup, and Karpenter tuning.
- Built the internal developer platform product teams ship on (Concourse CI/CD, HashiCorp Vault, and Nexus over the account and EKS baseline), so teams deploy, manage secrets, and run workloads through standard paths instead of standing up their own infrastructure. Used by 100+ developers across the company today.
Side Projects Ongoing
- Built an org-wide report on AI-tooling usage and cost, aggregating Kiro and GitHub Copilot spend into daily Teams summaries with per-user breakdowns, projections, and overage alerts (Python Lambda, EventBridge, cross-account S3, Terraform).
- Built an internal bot that watches the AWS "What's New" feeds, summarizes announcements relevant to our stack with Bedrock, and posts them to Teams (TypeScript, DynamoDB, Bedrock, CodeBuild).
- Run a personal multi-account AWS organization on the same patterns used at work. Terraform-managed S3 and CloudFront with ACM, deployed by GitHub Actions over OIDC with no long-lived credentials.