Andrew Montgomery · Sydney

Twenty years in enterprise technology, and I still ship the code.

Thirteen of them as a software engineer. Then solution architect. Then I built the partner sales engineering function for Asia Pacific and Japan, and hired half of it. Then I was the third hire who opened Australia for an American company. Three agent systems are running on my own infrastructure tonight. I would rather show you one than describe it.

Verifiedlinks to the thing that proves it.
Self reportedis just my word.

One job, four altitudes.

Understand the business, build the thing, make it produce revenue. Same job every time. The altitude changed.

2005-18Built it. Analyst programmer to Lead Software Engineer.Praxa · News · David Jones · ING
2018-21Architected it. An enterprise data model, deployed to 25,000 staff in twelve months.Tableau
2022-23Hired the people who do it. Built partner sales engineering for Asia Pacific. Eight engineers. I hired four.Snowflake
2024-Opened the market. Third hire in region. Built the partner program, then closed the first customers on it.Coalesce
Self reported

Solution Architect of the Year, APAC. Partner Sales Engineer of the Year, APJ. Two vendors, two disciplines.

Self reported

$1.24M closed at Coalesce. I do not publish a quota attainment percentage, because I cannot verify one.

Self reported

I know seven Australian and nine New Zealand system integrators by name. That bench takes two years to build from cold.

How I work

Non deterministic systems do not fail loudly. They fail plausibly.The reason I built a nightly reconciliation pass, after finding a live producer and a dead consumer in my own agent. It had been quietly returning nothing for days, and looking fine while it did.
Self reported

I do not arrive with a playbook.

Twenty years is a lot of reps. It is not a method.

Self reported

An agent writes most of my code. I am accountable when it is wrong.

It can change its own capabilities on a branch. Only I can merge to the live one.

Self reported

Only a probe or a citation may confirm a fact. Never the model.

Which is why this page has marks in the margin.

Self reported

Reduce the next fire, not the one in front of you.

The reconciliation pass took a day. It has been catching that failure ever since.

Self reported

Name the gap.

Nobody has paid me to write software since 2018. I have written it every day anyway.

What I have built

Three systems I built end to end, alone, and run every day. Small enough that I have had to fix every failure myself, which is how I know where agents actually break. Every number below is one I can be held to, including the ones that do not flatter me.

HLAA

Private. Walkthrough on request.

An agent that administers nine servers. It proposes changes to its own capabilities, and it cannot merge them. I do. Every enterprise is going to ask you how you let an AI near production, and this is the answer I have actually run rather than the one I would put on a slide.

One run, last Tuesday

NoticesA disk is at 91%and climbingReadsIts own runbookfor this boxFixes itPrunes logs,grows the diskOutcomeFixed, and itwrote down whyIt only learns the lesson if I approve it
0Changes the agent merged by itself
66Decisions written down
36Of those, later reversed

For engineers. Nine declarative NixOS hosts, a Proxmox cluster, an OPNsense edge, a self-hosted mesh. The agent develops its own skills and hooks on a branch; only a human merges to the live one. Thirty six of the sixty six architecture decisions were later superseded, which means I was wrong more than half the time and wrote down why on each occasion. That record is the thing an enterprise security review actually asks for. The honest limit: nine hosts in a house, one user, and nobody has ever been angry with me about it at 3am. The scale is not enterprise. The shape of the gate is.

SignalAgent

Private. Walkthrough on request.

It finds companies that are about to need what you sell, and shows its working. It never contacts anyone. It suggests, and a human decides.

One run

SpotsA manufacturerposts 4 SRE jobsScores itHiring, funding,news, timingChecks itselfIs the evidenceactually real?Outcome"They are scalinginfra. Here is why."
15Hand-labelled adversarial cases
100%Planted fabrications caught, with a tool
33%Caught without one

For engineers. I planted fabricated evidence in fifteen cases and measured whether the judge caught it. With a verification tool it caught all of them. Without one it waved two thirds of them through. That second number is why the tool is not optional, and it is the only reason this system is worth anything. The honest limit: fifteen cases is a smoke test, not a benchmark, and I wrote both the cases and the rubric, so the judge and I share a blind spot by construction. A second labeller would be the real test and I have not run one.

TheWatcher

Private. Walkthrough on request.

It probes six applicant tracking systems directly, pulls every new role, and judges each one against what I am after. A guard drops any fact the model cannot cite. I built that guard after the model invented investor lists for three companies, and four rows in my database still predate it.

One run, this morning

ProbesA company'shiring systemPulls19 roles comeback, rawGuardsDrops any factit cannot citeOutcomeOne worth reading.Every fact sourced.
6ATS platforms probed, not scraped
804Roles pulled and judged
4 / 112Records that still fail my own rule

For engineers. The rule is: only a probe or a citation may confirm a fact, never the model. It is not a slogan. It is a function that drops any field whose source URL is not in the retrieved corpus, and it has tests, including one that plants a fabricated source URL. I wrote it after the model copied “Sequoia, Accel, Y Combinator” out of an example into three unrelated companies. The guard shipped after the data, so four rows still carry facts it would now reject. They are still there. The honest limit: 39 percent line coverage. Ninety one percent on the ATS parsers, eighteen percent on the sweep that actually runs them. I know which half is load bearing, and I know which half I tested.

The seat I want

The first technical person on the ground when a frontier AI company lands in Australia. Deployment strategist, forward deployed, solutions architecture. The title matters less than the scope.

Self reported

Standing up a region is five jobs at once. Find the problem worth solving. Build the thing that proves it. Hold the architecture conversation with their CTO. Structure the terms so it pays for itself. Hire the engineers who will do it a hundred times after you.

Most people can do two or three. I have done all five, though not yet on the same day.