How do I work?
Clients describe the outcome they want rather than writing a
specification. I build towards it and stay in conversation as the
work takes shape.
Much of the value comes out of that conversation. The best chances
to improve a system only become apparent once the work is underway,
which is why they seldom appear in a brief.
I design systems whose results can be verified rather than assumed.
And I am interested in software that uses AI at runtime, where it
extends what the product can do, not only in using AI to write the
code faster.
What have I built?
A tool that proves a data migration moved everything. Single sign-on
for a national contact centre, SCIM written from scratch. A call
recording pipeline for a health line that stops dropping recordings
under load. Long-term vehicle booking across a car dealer network.
A retrieval platform that checks its own citations.
seven of them, with what each was worth →
What do I work with?
- languages
- Go · TypeScript · Node.js · Python · C#
- cloud & data
- AWS serverless · Lambda & SQS · Docker · PostgreSQL · DynamoDB · Redis
- identity & contact centre
- SCIM 2.0 · SAML 2.0 · Entra ID · AWS IAM · Amazon Connect · Twilio · Stripe
- AI
- Claude API · agentic tool-use · RAG · embeddings · Whisper · output verification
What's on my GitHub?
Three things I built to understand them properly: a distributed job
queue that recovers work from dead workers, Raft consensus on an
event loop so the state machine needs no locks, and a circuit
breaker for asynchronous calls.
what each one does →
How do you reach me?
If you have something that needs building, or a system that isn't
behaving, tell me about it. I answer plainly about whether I am the
right person for it.
message me on LinkedIn →