DevOps Engineer
•
Energy Industry
Dylan
Summerville
I build the systems the company runs on: its Azure estate, the automation platform behind the back office, and the tools its people use in the field.
DevOps Engineer at a solar installer, self-taught in 2025. I own the Azure estate as code, built the Job Adding System that runs the back office, and build the tools the sales team and its customers use. The work has since grown well beyond DevOps.
Automations in production, each catalogued and flowchartedJob Adding System
Platforms integrated, from the CRM to the regulatorJob Adding System
Hours of manual work replaced every year, estimated from production volumesJob Adding System
Automated tests guarding 250k lines of PythonAll systems
Rust battery-schedule optimiserRenewCompare
AEMO price data modelledRenewCompare
Featured
Three systems, built end to end
Designed, built, tested, deployed, documented and operated by me.
In production
A signed solar proposal goes in; a fully provisioned job comes out across every core company platform. 76 automations across 20 platforms, 5,000+ staff hours reclaimed, the equivalent workload of 3–4 full-time roles eliminated.
In production
The energy-analysis tool a solar installation company runs in-house: it reads a power bill, prices the customer's real usage against the Australian energy market and forecasts wholesale prices. Its Amber Electric VPP estimate lands within $42 per year of real-world costs.
Showreel
Everything above, told properly in 3 min 26 s: how a signed proposal becomes a provisioned job, what RenewCompare does with a power bill, and what I'm building now.
Delivered
An assistant for the people who run the company, typed or spoken. It asks the Job Adding System about any job over MCP, builds reports in code across the company’s platforms, and makes changes in Slack, the CRM and the work boards once they approve them, inside budgets that leave the automations their share.
More
The rest of the site