Technical leadership · Architecture · Delivery recovery

I make messy technical environments stable, predictable, and boring.

I work across architecture, delivery, product, and ownership to find what is actually making systems hard to change, hard to trust, and hard to ship.

Book a diagnostic call See selected work

For teams dealing with stalled delivery, repeated rework, fragile systems, or complexity that keeps compounding.

A dense knot of tangled lines on the left untangling into a calm, evenly spaced parallel grid on the right — chaos resolving into stable, predictable systems. — Messy systems untangled into stable, predictable patterns.

Selected experience

Production systems where reliability, delivery, and trust matter.

Experience across enterprise, aviation, insurance, fintech, and product environments.

Southern Cross
Air New Zealand
GCD
Inspected
Afterpay

Recent LinkedIn posts

Short notes on delivery confidence, technical systems, and stability work.

LinkedIn post on AI-generated code, upstream failures in assumptions and workflow, and uncertainty cost

Open on LinkedIn

LinkedIn post on vibe coding, speed, and operational trust in live systems

Open on LinkedIn

LinkedIn post on speed versus trust in software, surface area for failure, and uncertainty cost

Open on LinkedIn

Selected work

Selected stabilisation and scale work

Stabilisation where messy technical environments had to become predictable again, plus disciplined work inside high-scale commercial and fintech product systems.

Featured stabilisation case study

Southern Cross

Technical Lead / Enterprise rebuild stabilisation

Outcome

From stalled delivery to daily shipping.

Environment: A large-scale rebuild of staff-facing legacy systems into a micro-frontend and micro-backend architecture.
Instability: The team did not understand the architecture, delivery pressure was hiding the real risk, and nothing was shipping.
Intervention: Rebuilt the technical direction, trained developers, supported squad delivery, and gave leadership a clear view of the risk and recovery path.
Stabilised: Daily shipping, effective QA, clearer ownership, and junior developers contributing confidently.

Inspected

Founder and CEO / Product and systems architecture

Outcome

Inspection workflows made traceable, repeatable, and harder to fake.

Environment: Field inspection software for teams working across compliance, property, food safety, offline workflows, evidence capture, and audit-ready records.
Instability: Inspection work becomes unreliable when photos, notes, signatures, site context, follow-up actions, and compliance evidence live in disconnected places.
Intervention: Designed the product around structured evidence capture, offline-first workflows, clearer inspection flows, and records that can survive review.
Stabilised: Turned loose field activity into a more consistent, traceable, and operationally reliable system.

Air New Zealand

Senior Engineer / Enterprise operational systems

Outcome

AI-supported customer service work that reduced phone wait times by 97%.

Environment: Enterprise airline systems supporting customer service, flight operations, ground staff, crew, and passengers.
Instability: Operational information was time-sensitive, distributed across different users and systems, and delays created pressure for both customers and internal teams.
Intervention: Contributed to AI-supported customer service improvements and infrastructure that gave staff, crew, and passengers faster access to real-time flight events, delays, and incident information.
Stabilised: Made operational information faster to access, easier to act on, and more visible across the people affected by flight disruption.

GCD

Principal Engineer / Mobile architecture and delivery strategy

Outcome

Mobile delivery path created without forcing a full rebuild of the existing platform.

Environment: A client needed a mobile app without rebuilding their website, backend, and operational infrastructure from scratch.
Instability: A duplicated mobile product would have increased maintenance, fragmented logic, and forced the business to support disconnected systems.
Intervention: Helped shape a mobile strategy that reused existing infrastructure, preserved the value of the current platform, and created a cleaner path for mobile delivery.
Stabilised: Reduced rebuild risk, protected existing investment, and gave the client a more practical route into mobile.

Scale and commercial product

Afterpay

Dovetail

Senior Software Engineer / Consumer fintech product delivery

Environment: High-scale consumer fintech and payments environment.
Constraint: Product changes had to protect customer trust, merchant expectations, and payment-flow clarity.
Contribution: Contributed to mobile app redesign and feature delivery inside established engineering standards and high-traffic commercial systems.
Signal: Experience operating inside a fast-moving fintech product environment where reliability and consistency mattered.

Additional work

Additional leadership, delivery, and discovery work

Other principal, technical lead, discovery, and product delivery roles. Framed at the right weight so the strongest stabilisation proof stays clear.

ClearPoint

Principal Engineer / Customer and operator systems

Work: Frontend reliability, structure, performance, and maintainability across customer and operational systems.
Contribution: Provided principal-level guidance on practical improvements where customer impact, system complexity, and long-term maintainability had to be balanced.

Infosys

Technical Lead / Enterprise client delivery

Work: Frontend and mobile delivery initiatives across enterprise client engagements.
Contribution: Improved engineering standards, technical direction, delivery sequencing, and predictability across implementation teams.

Māori Television

Technical discovery / React Native SDK feasibility

Question: Could a video SDK that was not directly compatible with React Native be safely used inside the product?
Work: Mapped native integration constraints, React Native bridging considerations, SDK limitations, and implementation risk.
Contribution: Gave the team a clearer basis for deciding whether to proceed before committing delivery effort.

NZ Funds

Product delivery / Financial services

Work: Customer-facing mobile interface work for financial product flows.
Contribution: Built and refined screens where clarity, consistency, and trust mattered in a regulated financial context.

Osynlig

Senior Frontend Developer / Client web products

Work: Scalable frontend delivery across client-facing React web products.
Contribution: Focused on maintainability, implementation quality, and delivery planning across product surfaces.

Flossie

Contract Senior Software Engineer / Booking workflows

Work: Booking software and campaign landing pages for appointment and customer acquisition workflows.
Contribution: Delivered product surfaces that supported service workflows, customer conversion, and campaign delivery.

Social Dog

Product delivery / Mobile

Work: Mobile stability and releases under growth and support pressure.
Contribution: Root-cause work in my surfaces plus tighter release rhythm around repeat failure patterns.

EatChoice

Product delivery / Commerce

Work: Checkout and orders under commercial and chargeback pressure.
Contribution: Held checkout integrity as the gate when sequencing fixes versus new scope.

Den Automation

Product delivery / IoT mobile

Work: Smart home mobile apps from prototype to production across IoT and connected device workflows.
Contribution: Supported CI, store release, lifecycle behaviour, and user-facing mobile experiences for real-world homes.

Engagement signal

When teams bring me in

01Delivery keeps slipping
02The same problems keep returning
03Ownership is unclear
04Complexity is compounding

Approach

What I do

01Find the real constraint
02Trace it through architecture, flow, ownership, and delivery habits
03Identify the smallest structural changes with the highest leverage
04Make the next move obvious

Engagement model

How the diagnostic works

01
Diagnose
Name the real constraint behind the symptoms.
02
Stabilise
Fix the structure that drives rework, risk, and stalled delivery.
03
Make it repeatable
Clear ownership and delivery habits that hold under pressure.

Writing