Reference
Component catalogue
Every brick this site is built from, in each of its states.
Logo
Theme toggle
Button
Email pill
Carousel
Chip
Segmented control
Role card
- Apr 2026 - present
WhiskyInvestDirect
Full-Stack Engineer
Leading a greenfield rebuild of the core trading platform on SvelteKit - modernising architecture and embedding quality across engineering, delivery and product.
Empty state
Nothing matches those filters
Services and FAQ
The full section as it appears on the home page. Answers stay in the DOM while collapsed so crawlers and answer engines can read them.
Services
How this works. What working with me looks like
I take a product or a problem and build the software for it. Design, front end, API, infrastructure, tests and the accessibility work, as one person. No handoffs between four different suppliers.
- Engagement
- Contract.
- Length
- Any.
- Project size
- Small to huge. Let's chat about what you need.
- Location
- Remote worldwide, based in the UK.
- Availability
- Open to conversation.
Are you available and how soon can you start?
Always worth a conversation. Long engagements or small well defined jobs, both suit me. Tell me what you need and I will tell you honestly whether it fits. The CV above shows what I am working on now.
What do you build with?
Whatever suits the project. Recent work is SvelteKit, TypeScript, Node and AWS, but twenty years covers plenty of other stacks. The right choice depends on your problem and what you already run.
Do you work remotely and where?
I work remotely, worldwide, from the UK. I'll shift my hours to overlap with your team and travel for a kickoff when it helps.
Do you use AI?
Every day and deliberately. Claude is part of how I work rather than something bolted on. Planning, code, review, tests. Twenty years of knowing what good looks like is what makes that worth having: it decides what to keep, catches what the model gets wrong and holds the same bar I would hold without it. The speed is the tool. The judgement is what you are paying for and it is still mine.
How do you work with an existing team?
I hit the ground running and I join as one of the team rather than sitting outside it. Your standups, your board, your code review, your conventions.
What size of engagement suits you?
Small to huge. I have been the only developer on a project and one of a multi discipline team, so the shape matters more than the size.
What happens when the engagement ends?
You keep everything and your team understands it. I document as I go rather than leaving knowledge in my head, so there is no cliff edge when I stop.
Something not answered here? Ask me directly
Back to top
Appears fixed, bottom right, once the page is scrolled past 600px.