Engineer / Platform / Services
Where the software runs
Servers sized for what you actually use, moved into the cloud or back out of it, with the monthly bill worked out first.
Ran 20 Docker apps on Google Cloud and AWS
Deployed and maintained 20 Docker containerized applications, troubleshooting with Podman and Kubernetes, and managing R‑based apps on Google Cloud and AWS.
Deployed and maintained 20 Docker containerized apps across Google Cloud and AWS, troubleshooting with Podman and Kubernetes for stable releases.
Infrastructure simplified beyond AWS
Reworked an international client’s infrastructure by removing unused services, adjusting capacity and moving workloads away from AWS. The founder reports a 10x reduction in cloud costs with no loss of productivity.
Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.
Provisioned Azure infrastructure as code
Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL Flexible Server, Front Door/WAF and networking — across the development, staging and production environments.
Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL, Front Door/WAF — reproducible across dev, staging and prod.
Owned end‑ platform deployments to Azure
Owned end‑to‑end deployments of the platform to Azure, managing releases across development, staging and production environments.
Owned end-to-end Azure deployments, moving releases through dev, staging and production along a defined, repeatable path.
Built the entire core infrastructure from scratch
As one of the first hires, designed and built the entire core infrastructure and supporting processes from scratch for a green‑energy SaaS startup, laying the foundation for rapid growth.
As one of the first hires, designed and built a green-energy SaaS startup's entire core infrastructure from scratch, enabling rapid growth.
Infrastructure defined in a repository
Built the company's own infrastructure as 19 Ansible playbooks and 34 roles across 12,065 lines of YAML, converging a live host to a declared state with every play idempotent.
The repository supplies the configuration for rebuilding the declared environment, and the parts of it that were only ever true because somebody remembered…
Public services on a small server
Hosted the company’s public services on a single‑core 512 MB host — a git forge, a web server for seven domains, Tor, two alternative‑protocol servers and intrusion banning — treating 464 MB of usable memory as the design constraint; backup automation is a separate implementation.
The recorded public-service setup ran on a machine that cost less per month than a lunch, and the design is better for the discipline rather than merely…
Ran containers on Podman and Quadlet
Deployed a container plane on Podman and Quadlet under systemd rather than Docker, because Docker's default bridge‑port publishing can bypass UFW rules — and gave deploys an unprivileged user with one fixed command instead of root.
Containers run under the supervisor that was already trusted, behind the firewall that was already declared, and a routine release uses one scoped command…
Provisioned a second server from code
Automated the provisioning of a second server on a second cloud provider, creating the firewall before the machine so it is born behind one, with both providers' firewalls written directly against their REST APIs to avoid a third‑party collection.
A second host can be created, or re-adopted, from the repository, behind a firewall that already exists, at a cost the file states.