I build and automate cloud infrastructure — Terraform, AWS, and CI/CD pipelines that ship securely with no stored credentials. I come from 8+ years of production software engineering (5 at Intuit building authentication systems that served millions), so I bring the parts many cloud engineers lack: real production experience — deploys, on-call, observability — and deep security & identity depth.
- ☁️ Building Infrastructure as Code (Terraform) on AWS — containerized (ECS/Fargate) and serverless (Lambda)
- 🔐 Keyless CI/CD (GitHub Actions + OIDC), least-privilege IAM, zero-trust thinking
- 🤖 Exploring AI/MLOps infrastructure with FinOps cost discipline
- 🎓 Completing an M.S. in IT (Dec 2026) · earning AWS Solutions Architect + Terraform certifications
- 📍 San Diego — open to Cloud Engineer / Architect / Platform Engineer roles (onsite or remote)
Also experienced with React, Next.js & modern frontend — full-stack range from years of product engineering.
const jason = {
role: "Cloud / Platform Engineer",
background: "8+ yrs software engineering · 5 at Intuit (auth at scale)",
building: {
iac: ["Terraform", "CloudFormation"],
aws: ["ECS/Fargate", "Lambda", "VPC", "IAM", "CloudWatch"],
cicd: ["GitHub Actions (OIDC)", "Jenkins"],
ai: ["MLOps", "model serving as code"],
},
edge: ["IAM / zero-trust", "least-privilege", "FinOps cost discipline"],
learning: ["Kubernetes (CKA)", "AWS Solutions Architect"],
askMeAbout: ["secure cloud infra", "IaC", "AI/MLOps platforms"],
};- ☁️ cloud-foundation — A containerized app deployed to AWS entirely via Terraform, delivered by a keyless OIDC GitHub Actions pipeline. ECS/Fargate + ALB, least-privilege IAM, remote state, policy-as-code in CI.
- 🔗 url-shortener-serverless — Serverless AWS: Lambda + DynamoDB (single-table) + API Gateway + CloudFormation IaC; pay-per-request cost model.
- 🤖 agent-smith — An LLM function-calling coding agent (Python) with sandboxed file ops and path-traversal protection.
- 🏀 nba-draft-tracker — Full-stack app (React + edge functions) with GitHub Actions CI/CD.
Open to Cloud Engineer / Architect / Platform roles — and always up for a good infrastructure conversation.


