I’m a Lead Platform / Infrastructure Engineer. I design and operate the AWS systems behind a high-traffic e-commerce platform—covering infrastructure, deployment automation, edge traffic, and the operational practices that keep those systems reliable.
My work sits at the intersection of cloud architecture, software delivery, and production operations. Day to day that means Magento and modern storefront stacks, CI/CD, containerized workloads, Cloudflare edge configuration, and the trade-offs that show up when systems have to scale under real traffic.
Certifications#
AWS Certified Solutions Architect – Associate (SAA-C02) — earned July 2026.
I’m currently studying toward the AWS Professional certifications, with a focus on large-scale architecture, high availability, and operational excellence in production environments.
What I work on#
- AWS infrastructure design and operations
- E-commerce platform reliability (Magento + modern frontend systems)
- CI/CD pipelines and deployment automation
- Containerized application tiers and scaling patterns
- Cloudflare edge routing, caching, and traffic management
- High-availability and cross-region planning
- Developer experience, internal tooling, and technical leadership
A large part of the role is not just building systems—it’s keeping them operable, debuggable, and resilient as they grow.
How I approach systems#
Most infrastructure problems are complexity management problems. My defaults:
- Reduce moving parts
- Eliminate unnecessary state
- Automate anything repeated more than once
- Prefer predictable failure modes over clever ones
- Optimize for operability at 2 AM, not theoretical elegance
I prefer right-sized systems that evolve intentionally: start simple, add complexity when measurable pressure forces it, use managed services where they reduce operational burden, and avoid premature multi-region or distributed-database complexity unless the business actually needs it.
In practice, that has looked like hybrid Magento + Next.js storefronts, ECS/Fargate frontend scaling, EC2 application tiers where control matters, RDS with controlled replication instead of full active-active, and Cloudflare-first routing and caching.
Outside of work#
I apply the same systems thinking to how I operate day to day:
- Knowledge — Obsidian as a personal knowledge base, with notes refined into structured material and reinforced through active recall. Especially useful while studying AWS certifications.
- Training — a structured early-morning PPLUL schedule. Consistency under real-world constraints beats optimization for perfect conditions.
- Linux workstation — Arch Linux + Hyprland, managed with chezmoi as infrastructure-as-code: templated configs, machine-aware settings, automated bootstrap, and encrypted secrets.
Writing#
I write about infrastructure, architecture trade-offs, and workflows from real implementation—not theory. Topics usually include AWS and e-commerce architecture, CI/CD and developer infrastructure, Linux desktop automation, and personal systems built like engineering problems.
If a system is hard to reason about under pressure, it isn’t finished. That’s the standard I try to apply at work—and in everything else I build.
