For hiring teams
I lead engineering teams that ship to production.
Engineering Lead and senior engineer. Seven years building, five of them shipping production software in TypeScript and Node.js. I own the architecture, run delivery and grow engineers — and I am still the one writing the hard parts.
Open to engineering leadership roles, full-time or fractional.
Scroll — it builds as you goA business runs on it
Storefront, orders, payments, stock, suppliers, delivery — one platform
Leads, and still builds
I run the team and still write the hard parts
Payments that stay correct
Through retries, duplicates and out-of-order callbacks
Selected work
Three, not thirty. Each one reads as a release: what was broken, what I did, when it went live.
- 2026
A retail business needed one system to run on — orders, money, stock, suppliers and delivery — instead of separate tools that disagreed with each other by the end of every day.
Engineering Lead — architecture, delivery, and the team
STARTFIRST BUILDSTAGINGLIVEThe system the business actually operates on — orders, payments, inventory, fulfilment, suppliers and delivery, in one place that stays correct. Built and maintained over a year, and still mine to look after.
TypeScriptNestJSFastifyPrismaPostgreSQLSocket.IOBullMQDockerAzureAWS S3 - 2026
A client product needed a backend, a back office and a front end delivered together, with quality that did not depend on which engineer happened to pick up the ticket.
Co-founder & CTO — technical direction, delivery, and review
STARTFIRST BUILDSTAGINGLIVEDelivered across backend, back office and front end over fourteen months, with a written QA and testing benchmark the team worked to rather than an informal understanding of done. I remain CTO at Tektariq.
TypeScriptNestJSDockerPostgreSQL - 2026
Clinicians need software that holds patient records correctly, runs a consultation end to end, and loses neither when the network drops halfway through.
Senior Software Engineer
STARTFIRST BUILDSTAGINGLIVEFour surfaces on one record — the clinician EHR, the patient portal, the telehealth consultation and an embeddable widget — built on a shared component system so they stay consistent and cheap to extend.
TypeScriptNext.jsReactTailwind CSSDocker
How I run a team
Four habits, applied the same way whether the team is three people or thirteen.
01
Plan
Work starts from the outcome, not the ticket. I size it with the people who will build it, so estimates come from the team rather than at them.
02
Review
Every change is read by a person before it ships. Review is where engineers get better, so I treat it as teaching time and not as a gate.
03
Release
Small, frequent, reversible. Staging mirrors production, and anything that cannot be rolled back gets a plan before it gets a deploy.
04
Grow
Each engineer owns something real within a month. I hand the hard problems over early, then stay close enough to catch the fall.
Need someone to own engineering?
Twenty minutes is enough to work out whether this is a fit. No deck, no pitch.