Cloud Infrastructure & Systems Engineering
A selection of cloud engineering projects spanning infrastructure, automation, cost analytics, reporting, and reliability.
I built this portfolio for the Cloud Resume Challenge to treat my personal resume site like enterprise infrastructure.
Ready to see the deployment? View the cloud-hosted version of my Resume →
Want to review the code? Check out the public GitHub Repository →
Looking for a deep dive? For a complete look at the underlying architecture, cost-management decisions, and pipeline configurations, explore the full Technical Case Study →
I built a GCP billing analytics project that uses synthesized cloud expense data in BigQuery to power Data Studio (Looker Studio) dashboards for real-world cost reports.
This project mirrors a real cost-reporting scenario I solved at a previous employer. Executives, dev managers, and ops teams needed self-service visibility into monthly cloud spend without being granted direct access to the billing account portal.
I believe in making other people's jobs easier. I'm willing to do a little extra work up front if it gives others the tools and visibility they need to move faster.
Why this project matters: Cloud cost data is useful when it is organized and presented in a way that users can actually consume. This project shows how raw billing exports can be transformed into self-service dashboards that help teams understand spending, make better decisions, and reduce the reporting burden on finance and cloud administrators.
Looking for the full walkthrough? Explore the complete Reporting Case Study →
I completed an AI-Native Engineering Challenge by using Codex as an engineering agent to build a playable browser version of War. I used the AI tool to drive the entire project, moving systematically from the initial requirements through implementation, verification, documentation, and the final retrospective.
The purpose of the project was not just to make a card game. It was to practice an AI-native software development lifecycle. This involved translating rules into a specification, planning the architecture, and separating game logic from the UI, while also writing deterministic tests, iterating from browser feedback, and capturing lessons learned.
What I used Codex for: Repository inspection, rule interpretation, implementation, unit tests, UI iteration, documentation, browser verification, and retrospective notes.
Ready to play? Launch War: The Card Game →
War gameplay in progress, showing the table layout, autoplay controls, revealed cards, pile state, card counts, and round log.
Multi-month GCP spend report showing project costs over a selected time series, with filters for region, environment, project ID, and product.
Single-month cost summary showing project-level spend, service and SKU filters, and comparison against the previous month.