Hands-on across architecture, code, delivery, operations, security, and team. Inside the regulated environments your business lives in. Restructured how I work around agents. Now using them daily to ship Voder, the Claude Code plugin suite I run my own delivery with, and this site.
Receipts, not buzzwords.
May 2026 – present Endava Senior Architect on Visa Click to Pay initiatives: discovery and implementation.
2024 – Feb 2026 Westpac Project Director on FATCA / CRS (cross-border tax reporting) at Westpac. Led a 50+ person team across BA, PM, change, architecture, and delivery. Line-managed the leads of each track. Took entity-customer compliance from 0 to 97 percent in 10 months. 5,300 bankers, 614 branches. Then ran discovery for ongoing know-your-customer (KYC) and anti-money-laundering / counter-terrorism financing (AML / CTF) reform across two Consumer business units.
2022 – 2024 Pacific National Rail Systems team lead. 25+ developers, business analysts, and support engineers. Halved open incidents and eliminated recurring ones through root cause analysis. Product Owner for a new internal API platform on Node.js + Fastify + OpenAPI + Turborepo.
2019 – 2022 Greater Bank Digital transformation consultant for a 50+ developer organisation. Worked closely with the bank's risk team to design SDLC (software development lifecycle) controls that support high velocity: deploys to production multiple times per week, delivery cycle dropping from ~50 to ~8 days, all with "no objection" from APRA (Australian Prudential Regulation Authority). Testing team 1 person to 9. Production security vulnerabilities from hundreds to near zero. Identity and access management (IAM) architecture and staged migration design.
Where the regulated-services instincts came from.
2014 – 2019 AMP Application and Integration Architect, then Solution Architect. Led the "My AMP" rebuild of banking and wealth-management web for AMP's 1 million+ customer base, including 46,000 home-loan customers at AMP Bank. New Zealand iteration. Bett3r. Salesforce + IRESS adviser-platform integration prototype.
2017 – 2018 Rabobank Solution Architect for new web and mobile banking channels. Java + Spring Boot + Backbase (banking channel framework). Continuous Delivery and behaviour-driven testing embedded in the channel-build process.
2011 CSC for BPAY One of the architects on the next-generation BPAY (Australia's bank-to-bank bill payments scheme) hub. Owned the NFRs: how fast, how reliable, how supportable. Hit every 6-month milestone before the project was cancelled at investor level. Designed a file-transfer security solution that signs payments record-by-record, not file-by-file.
2008 – 2011 NAB / MLC Senior Analyst Programmer, then Technical Lead for the Integration Services Team (15+ developers). Introduced Continuous Integration and automated deployment plans. Jython for integration extensions. Support Lead for 20+ BusinessWorks engines in production.
Stack across the timeline: Python (CSIRO), Jython (MLC), Java + Spring (AMP, Rabobank, Greater Bank), C++ (Team Bondi, CSIRO RoboCup), TypeScript / Node (today). Cloud: AWS (Addressr, AMP), GCP (Voder). Snowflake: not yet.
Solo entrepreneur. Built. Sold. Supported. Funded.
Unit testing for TIBCO BusinessWorks (enterprise integration platform).
Filled a gap nobody else did: real unit tests for TIBCO BusinessWorks projects. Mid six-figure revenue across paying customers in financial services across Asia-Pacific (APAC), Europe, and the US. Still in use.
Apache Ant tasks for TIBCO BusinessWorks.
Brought modern build automation to TIBCO BusinessWorks projects. The build-and-deploy story TIBCO never shipped. Low six-figure revenue from paying customers in production across APAC, Europe, and the US. Still in use.
Australian address validation. Free, or hosted.
Two flavours, one codebase. Free and self-hostable from GitHub (110 ★, 23 forks, 43 releases). Hosted as a service (SaaS) on AWS via RapidAPI, five-figure lifetime revenue from 16,473 users (830 active in 30d). Used in production by Australian services.
The discipline behind all three:
Continuous Delivery
Tech turned out to be the easy part. People, processes, orgs are the work. Fireteams of Awesomeness: small, cross-functional, military-inspired teams I built, taught, and shipped with. At 15-person, 25-person, and 50+ scales, across super, banking, and rail.
Support experience going back to 2002. The systems I design survive contact with production because I know what production actually breaks like. I've been the one debugging it.
2002 · TIBCO
Rendezvous Support Engineer
Started in the queue. Windows, Solaris, HP-UX, Linux. Bus topologies, retransmit storms, the lot. 24×7 follow-the-sun rotation across Sydney, London, and Palo Alto. Every architecture I've drawn since carries that scar tissue.
MLC
Integration Support Lead + Tech Lead
Led production support for the Integration team alongside running its delivery. The team that ships is the team that supports.
Pacific National
80 → 40 / month
Halved the monthly incident rate on the Rail Systems backlog. Same team. Better signal, because I knew where to look. Build-it-and-throw-it-over-the-wall is how systems rot.
The thinking I've kept returning to:
The Phoenix Project
The Unicorn Project
The DevOps Handbook
Team outcomes across the employers. The talks. The literature.
Greater Bank
24 → 8
Delivery cycle, days.
Greater Bank
1 → 9
Permanent testing team, headcount.
Greater Bank
100s → ~0
Unpatched production security vulnerabilities.
Pacific National
100 → <10
Open incidents in the Rail Systems backlog. (Separately, halved the monthly incident rate, 80 → 40.)
MLC
15+
Developers led, Integration Services.
Westpac FATCA
50+
Cross-functional team across business analysis, project management, change, architecture, delivery.
Talks · 510+ leaders across three rooms
Aligned with the field. Sometimes ahead of it.
Team of Teams
Team Topologies
The High-Velocity Edge
This is what restructuring engineering around agents looks like in practice. Voder shipping into production. agent-plugins running my own delivery loop. The Shift translating the practice for other engineering leaders. Specific systems, specific outputs, specific risk posture. Not "we should use AI more."
Weekly LinkedIn newsletter for engineering leaders. Procurement, security, governance, vendor risk, regulatory trajectory. Issue 07 reached 1,079 impressions, top of the series.
Co-founded consumer fintech. "Helping you own your financial well-being." 21 percent spending reduction proven in prototype. Pre-launch.
Open-source Claude Code plugin suite. Architecture governance, ISO 31000 risk, test-driven development, delivery quality. The toolkit I use to ship Voder, Well Financial, and this site.
1999 to 2001 at CSIRO (Australia's national science agency). Autonomous software agents in C++ on Linux / Solaris. Real-time decisions, noisy data, multi-agent. CybeRoos placed 2nd Pacific Rim, 9th World. Three co-authored papers.
Where I draw the line today:
Agents own code generation and code review today, behind architecture, risk, and JTBD (jobs-to-be-done) guardrails. Human pace there would slow what AI pace makes possible. Humans still own architecture, scope, and business decisions. Not for chest-thumping. The guardrails aren't yet good enough. The bottleneck argument holds: human-pace on those decisions still leaves implementation running at AI pace. Better guardrails (evaluations, red-team patterns, human-in-the-loop checks) move the line.
