GEOSPATIAL PLATFORM ENGINEER · BRISBANE, AU

I build spatial systems that are calmer to run.

I work where architecture, delivery and operations overlap — making complex GIS platforms easier to change, safer to operate, and less likely to wake someone at 2am.

12+ years in geospatialex-EsriAWS · Azure · ArcGIS

RIGHT NOW

Working on the long game.

I am a technical SME for enterprise GIS operations in energy: planning upgrades, patching and modernisation across ArcGIS, FME, SQL Server and Oracle, while leading an offshore delivery team. The interesting challenge is not just keeping systems alive; it is making their next change safer than the last.

HOW I WORK

I care about the seams.

Most platform problems are not caused by one bad component. They appear in the gaps: when architecture cannot be operated, when delivery cannot be maintained, or when operations cannot adapt.

01

Build for the person on call.

A diagram is only useful if the people running the system can understand it when the pressure is on.

02

Automate the repeatable.

Put effort into guardrails, pipelines and self-healing so skilled people can focus on the unusual work.

03

Stay close to the code.

I draw the architecture, but I also write enough of the implementation to understand its real consequences.

SELECTED WORK

A few problems I have helped make less complicated.

Client details are intentionally de-identified. What remains is the work, the decisions, and the lessons.

Turning change into an operating rhythm.

A global GIS and data estate needed to remain secure while supporting a growing web of business integrations. I help plan and deliver evergreen upgrades and patching across dozens of servers — then turn the repeatable parts into automation, rather than another manual runbook.

  • ArcGIS Enterprise
  • FME
  • SQL Server / Oracle

Making releases less dramatic.

For a state electricity utility, I built release tooling to publish Portal items and align Utility Network data through an AWS CI/CD pipeline. The objective was simple: a change should be repeatable, reviewable and low-risk before it reaches production.

  • ArcGIS API for Python
  • PowerShell
  • AWS

Modernising without losing the domain knowledge.

A regional water authority was moving away from a legacy GIS interface. I led the architecture and HA deployment, while building a custom water-tracing algorithm that kept the operational knowledge useful in its new home.

  • ArcGIS Server
  • Geocortex Workflow
  • SQL Server

TOOLKIT

Platform first. Production code when it matters.

ArcGIS Enterprise · Utility Network · FME · AWS · Azure · Python · PowerShell · SQL Server · Oracle · React · REST APIs · CI/CD · monitoring and automation

NOTES FROM THE FIELD

Things I learn while making systems work.

I write about GIS tooling, cloud platforms, automation, and the occasional Linux rabbit hole. These are working notes, not polished thought-leadership.

Visit the notebook ↗

THE PERSON BEHIND THE PLATFORMS

From Esri's labs to the realities of keeping things running.

I started in geospatial at Esri China, implementing and tuning ArcGIS for Server, building custom solutions and training clients. In Australia I have worked across consulting, software and enterprise operations — at AAM, Esri Australia, NGIS, and now in the energy sector.

Being on both the vendor and client side changed how I think about engineering. A system is not finished at go-live. It needs to be understood, operated and evolved by real people over time.

MSc, Cartography & Geographic Information Science · Google Cloud Associate Cloud Engineer

SAY HELLO

Have a question, a platform problem, or want to compare notes?

I am always glad to exchange notes about GIS, resilient operations, automation, or an interesting map.