SENIOR SOFTWARE ENGINEER · INTEGRATIONS, DELIVERY & AI · SYDNEY
Senior software engineer who makes integrations work and stays through production.
I've spent six years at Suncorp delivering third-party integrations, platform migrations and production support for millions of customers. I work directly with vendors and business teams, turn unclear requirements into working solutions and find the root cause when integrations fail. I also build full-stack products and practical AI systems independently.
Pub Thursdays
● LIVE ON THE APP STORE · APR 2026Pub Thursdays started because my friends and I needed a better way to run our weekly pub night. I built the app we wanted, then took ownership of everything behind it: the SwiftUI client, Supabase backend, venue data, reminders and a pipeline that checks 500+ Sydney venue websites for current deals. Anything uncertain comes to me for review before it goes live.
- 1240
- APPROVED DEALS
- 289
- PUBS WITH LIVE DEALS
- 761
- PIPELINE RUNS · 28 FAILURES
- 1.00
- AVERAGE EXTRACTION CONFIDENCE · 0–1
● PRODUCTION DATA · UPDATED 17 NOV 2026
DEMO
A quick look at how it works.
I walk through the app, then show the pipeline that finds, checks and publishes pub deals.
HOW DEALS GET INTO THE APP
The pipeline does the repetitive work. I keep the final say.
01 · FIND
Start with the pub
The pipeline checks each pub's own website and menu PDFs for likely deals.
02 · STRUCTURE
Use AI where it helps
Rules narrow the page down, then Gemini turns the useful bits into structured deal data.
03 · REVIEW
Only publish what holds up
Anything below 85% confidence comes to me. Only approved deals go live, with the source attached.
Behind that, results are cached for 30 days, every published deal keeps its source and every pipeline run is logged.
SwiftUI · Supabase · Deno/TS · Gemini API
OPEN IN THE APP STORE →DealZ
● PRICE HISTORY FOR AUSTRALIAN TECH · IN DEVELOPMENTDealZ shows what consumer tech has actually sold for in Australia, so you know whether today's price is a good one. The idea is simple. The hard part is the data: finding every seller of the exact variant, proving each price came from its source and keeping paid API costs under control.
COLLECTION
Prices from every kind of source
Retailer storefront search, JSON-LD product data, the Wayback Machine and Google Shopping via SerpApi. When an LLM extracts a price, it's confirmed on the source page before it's stored.
MATCHING
The right product, not a close one
Sellers are matched by barcode (GTIN), model code and variant, filtering out wrong variants and phone-plan prices. In live runs it found 10 verified sellers for one phone.
GUARDRAILS
Cost caps and a CI gate
Every paid API call goes through daily cost caps and a usage ledger. 2,600+ automated tests and a CI gate check typecheck, lint, tests and schema drift.
HOW I BUILD
Claude Code as a pair programmer
Six layer-scoped subagents, 28 recorded architecture decisions and a review before every merge. I own the architecture, review and testing of what ships.
Next.js · TypeScript · Supabase/Postgres · Drizzle · Vitest · Playwright · GitHub Actions · SerpApi
Suncorp
SENIOR SOFTWARE ENGINEER · SINCE 2020- VENDORS
I integrated Mastercard, CMT telematics and Adobe Analytics into the app through vendor SDKs and REST APIs, working directly with vendor teams, reviewing API contracts and staying involved through production support.
- TRIAGE
I ran defect triage across the Duck Creek migration, getting owners assigned and blockers cleared across teams. I also built a HAR analysis tool that cut diagnosis of failing requests from days to a couple of hours.
- −25%
I helped rebuild Suncorp's iOS login during the ForgeRock migration. Login-related calls to the contact centre fell 25% after release.
- DELIVERY
I led mobile delivery for the Duck Creek insurance migration, setting the iOS approach and guiding my Android counterpart. That work led to my promotion to senior in September 2026.
- −50%
I shipped self-service features that helped cut contact-centre call rates by more than 50% over five years.
Understand the problem, then stay until it works.
I like working close to the problem and the people affected by it. I ask questions early, make the trade-offs clear and stay involved through the build, release and whatever turns up in production.
- 01 / ASK
Ask before I build
I start with what someone is actually trying to achieve, what's getting in the way and what a good result looks like.
- 02 / PLAN
Make the trade-offs clear
I turn unclear requirements into a scoped plan, explain the choices plainly and keep the work moving against the timeline.
- 03 / SHIP
Stay through release
I stay involved through integrations, edge cases, rollout and production support. When something breaks across system boundaries, I trace the evidence and bring the right teams together.
The tools I use to ship.
Swift and iOS are where I have the deepest production experience. I also build with TypeScript, Next.js, Postgres and Python, and use AI tools daily when they help me move faster. The useful part is knowing what to delegate, what to verify and what still needs a human decision.
- PRODUCT ENGINEERING
- Swift 6 · SwiftUI · UIKit · JavaScript / TypeScript · HTML · Next.js · React · Python · SQL · Tailwind
- BACKEND & ASYNC WORK
- Supabase/Postgres · Auth · RLS · Realtime · Storage · Edge Functions · Deno · Inngest · REST APIs · OAuth 2.0 / PKCE · Vercel · GitHub Actions
- AI-ASSISTED SYSTEMS
- LLM pipelines · AI-assisted log analysis · structured extraction · deterministic pre-filtering · confidence gating · provenance · human review · production safeguards
- DELIVERY & TOOLS
- Technical discovery · requirements scoping · vendor integrations · defect triage · API contract review · stakeholder communication · controlled rollout · Claude Code · OpenAI Codex · Git · LaunchDarkly · Jenkins · Firebase · Figma · App Store Connect
My defaults: understand the workflow, keep secrets server-side, make failures visible, put limits around cost and keep a human decision where confidence is low.