DevOps and cloud engineer in melbourne

cloud and linux infrastructure, containers and ci/cd pipelines, so shipping is routine and production stays up.

Deployment is where a lot of projects stall: the app works on a laptop and nobody owns getting it onto a server safely and repeatably. I set up the infrastructure, the pipeline that tests and ships every change, and the server configuration underneath, then document it so your team can run it.

I delivered automated CI/CD pipelines across AWS and GCP for Biofield Power inside a one-month contract, deployed and configured the production stack for Atlas Counsel on a Linux VM, and provisioned and operated a six-node Kubernetes cluster on the Melbourne Research Cloud. I hold the AWS Certified Cloud Practitioner and Microsoft Azure Fundamentals certifications.

what i build

  • CI/CD pipelinesAutomated test, build and deploy on every merge, with staging and production environments and rollbacks.
  • Cloud infrastructure on AWS and GCPCompute, storage, databases and networking set up sensibly, with costs you can predict.
  • Linux servers and web serversUbuntu servers set up securely, with Nginx reverse proxies, TLS certificates, systemd services, DNS and backups.
  • Containers and KubernetesDockerised applications and Kubernetes deployments when the workload justifies them, and simpler setups when it does not.
  • Load testing and reliabilityLoad and system testing before launch, monitoring and alerts after it.

work i have shipped

Biofield Power, one-month contract

CI/CD across AWS and GCP

Automated CI/CD pipelines delivered across both clouds, cutting release friction for the engineering team.

University of Melbourne

Distributed social sentiment analysis

Six-node Kubernetes cluster on Melbourne Research Cloud running serverless functions, Elasticsearch and live Kibana dashboards.

all projects →

tools

AWSGCPLinuxUbuntuBashDockerKubernetesFissionCI/CDNginxUvicornGunicornLet’s EncryptElasticsearchKibana

how it works

  1. A short callWe talk through the problem, who it is for and what done looks like. No preparation needed.
  2. A written scopeA short document with milestones, what is in and out of scope, and a quote or an hours-per-week arrangement.
  3. Build in the openYou see working software early and regularly, with tests and deployment set up from the first commit.
  4. HandoverDocumentation, access to every account and a walkthrough, so your team can run it without me.

how i think about it

questions

Do we need Kubernetes?

Usually not at first. A single well-configured server or a managed platform covers most small and medium products. Kubernetes earns its complexity when you run many services or need to scale them independently.

Can you take over an existing setup?

Yes. I start by documenting what is there, fixing anything risky such as missing backups or exposed secrets, then automate the deployment.

AWS, GCP or Azure?

Whichever you already use, or the one that fits your team and budget. I have shipped on AWS and GCP and hold an Azure fundamentals certification.

also hired as

DevOps Engineer · Cloud Engineer · AWS Engineer · AWS Cloud Developer · GCP Cloud Engineer · Platform Engineer · Infrastructure Engineer · Site Reliability Engineer · Linux Engineer · Linux System Administrator · Systems Administrator · Kubernetes Engineer · CI/CD Engineer · Deployment Engineer · Release Engineer

other services

have a project in mind?

send a few lines about what you need and when. the first call is free and there is no obligation after it.