Open to cloud / infra roles
I eliminate downtime and manual work. Built on the factory floor, now built on AWS.
Manufacturing engineer turned cloud infrastructure builder. CS&E student at University of Toledo | AWS Certified Cloud Practitioner
Two manufacturing internships taught me that the job cloud infrastructure and SRE roles actually reward finding the real root cause, fixing the system behind it, and proving the fix with a number, not a guess. At JAC Products, I traced a 9% defect rate to overprocessing and cut it to 2.5%. At Campbell Soup, I led 35+ employees across two shifts and cut micro-stoppages by 90%. That's floor experience and leadership already proven, not theory. I'm now pointing that same problem-solving at AWS, one certification and one real project at a time.
root-cause analysis
work orders
(uptime recovered)
two shifts
Where the numbers come from.
- Cut the 311D paint rejection rate from 9% to 2.5% by designing five structured trials across 400 rails and auditing the full paint and inspection process on-site at the supplier. Proved the root cause was overprocessing, not equipment failure, and removed one operator per cell.
- Rebuilt the preventive maintenance program in Asset Essentials, cutting active work orders 67% (679 to 227) and daily tasks 87% (189 to 24).
- Found 187 maintenance tasks running under a single shared account with no accountable owner, and reassigned each one to a named individual.
- Wrote the company's first controlled tooling standard for the BLM ELECT63 tube bender, consolidating scattered supplier manuals into one approved document through weekly review with engineering and leadership up to VP level.
- Standardized AutoCAD layouts across two plants, Saline (223 to 76 layers) and Napoleon (120 to 72), then modeled an incoming machine transfer in CAD from on-site measurements, planning the floor space before it arrived.
- Authored the company-wide layer standard guide and trained engineers and managers across five plants in the US and Mexico.
- Led seasonal production, supervising 35+ employees across 1st and 3rd shifts, ensuring safe start-ups and workflow continuity.
- Reduced micro-stoppages on the 8oz can line 90%, from 120 to 12 per day. The equivalent of a major uptime recovery on a line that runs around the clock.
- Built an automated employee call-off workflow in Power Automate, replacing manual spreadsheets with one centralized, real-time system for 20+ departments.
- Worked across Engineering, Maintenance, Quality, Warehouse, and Sanitation to troubleshoot equipment and keep the line stable in 24/7 operations.
- Designed and launched a WooCommerce/WordPress store for a vintage car emblem business, taking it from an empty catalog to 300+ products, with full payment and delivery systems configured, concept to launch in three months.
- Resolved 20+ tickets a day across Outlook, permissions, and hardware faults, earning the team's top service-quality rating.
- Trained five new interns on ticketing systems and troubleshooting methodology.
- Dean's List, Fall 2024
- International Rocket Award Scholarship
- Member, AI/ML Club
- Student Worker, American Language Institute
Three projects on AWS. One of them is this page.
My take on the Cloud Resume Challenge. The page you are reading is the project: a static site on AWS with a serverless backend, automated deploys, and the whole stack described in Terraform.
Your visit was just counted: this page called API Gateway, which ran a Lambda that added one to a DynamoDB table.
A private S3 bucket behind CloudFront with Origin Access Control, HTTPS only. Root account locked with MFA, daily work through a scoped IAM user, and a budget alert set before launch.
API Gateway HTTP API, a Python Lambda, and a DynamoDB table. One atomic increment per page load, no server to manage.
Every push to main deploys through GitHub Actions. It signs in to AWS with OIDC, so no AWS keys are stored in GitHub.
S3, CloudFront, DynamoDB, Lambda, API Gateway and IAM are all written as Terraform. The Lambda has unit tests that mock DynamoDB, so they run without AWS credentials.
The particle globe, galaxy and flowchart are Three.js shaders built with Claude Code, guided by Claude skills for Three.js and UI animation. I set the direction, reviewed each version, and kept it light enough to hold 60 fps on integrated graphics.
I misspelled "portfolio" when creating the DynamoDB table, then "fixed" the IAM policy to match my code, which only produced a new error. Tables can't be renamed, so the real fix was pointing the code and policy at the table that actually existed.
GitHub Actions kept getting AccessDenied even though every name matched the docs. CloudTrail showed that GitHub's OIDC token now carries numeric owner and repo IDs, and the trust policy needed those, not just the names.
Factory-floor CSVs land in S3 and trigger a Lambda that calculates OEE (Overall Equipment Effectiveness), writes the results to DynamoDB, and exposes them through API Gateway.
A public ALB, auto-scaling EC2 instances, and a Multi-AZ RDS database in private subnets, rebuilt from a manual setup into Terraform.
Let's talk about a role.
Based in Toledo, Ohio. Open to contractor and entry-level roles in cloud infrastructure, DevOps, and SRE.