Ben Adam

Systems Engineer & Developer
LocationNew Zealand
Webbenandhayley.nz
Field13+ years

Profile

Systems engineer and developer with 13+ years across infrastructure, software development, and technical consulting. I design, build, and support systems end to end — from production networks and Windows infrastructure to the custom applications and integrations that run on top of them.

My focus is maintainability: systems that are reliable, well documented, and clear to operate long after they ship. I keep current through an active home lab, where new tools and services get tested before they reach anywhere that has to stay up.

Selected Projects

Custom-built CRM with accounting integration

PHP · MySQL · Xero & MYOB APIs

Designed and built a bespoke CRM from the ground up — covering customers, orders, quoting, and PDF invoicing — with two-way integration into MYOB and Xero to keep financial records synchronised automatically.

Fish-tracking platform & Android applications

Node.js · MySQL · Kotlin / Android

Delivered a full-stack freshwater survey platform: a mobile-first field application on Node/Express and MySQL for recording sites, catches, measurements, and photos, with automated weather and moon-phase data — complemented by native Android applications built in Kotlin and Jetpack Compose.

Web & application development

Blazor · .NET · PHP / WordPress

Ongoing web and application development across the stack — PHP and WordPress/WooCommerce builds through to modern Blazor applications — with .NET experience spanning legacy ASP.NET 4 to the latest .NET 10.

Technical Skills

Infrastructure
Active Directory, Exchange, Office 365, vSphere, Veeam, IIS, Citrix
Development
C#, .NET (4 through 10), Blazor, ASP.NET, PHP, WordPress / WooCommerce, SQL, C++
Networking
DNS, reverse proxies, firewalls, VLAN segmentation, VPN / remote access
Mobile
Android — Kotlin, Jetpack Compose
Platforms & practice
Virtualization, backup & recovery, self-hosting, automation, integration, documentation

How I Work

Understand first

Start with the environment and the people using it before choosing the tool.

Keep it operable

Prefer systems that are observable, recoverable, and documented. A backup isn’t proven until a restore is.

Make it useful

Build around the workflow and the real problem, not just the technology stack.

Open to new work and consulting. benandhayley.nz  ·