The code making your money and the code scaring your engineers is usually the same code. That's where I work - across e-commerce, retail, higher education, legal, startups, and digital agencies. The problems are rarely unique to the industry - they come down to systems that have grown faster than the people maintaining them.
I'm hands-on and I get involved beyond the code - helping teams understand complex systems, reduce risk, and make better decisions when the trade-offs aren't obvious. I've shipped production work in PHP, JavaScript, Node, and Rust - and I built systems for years before AI tooling existed, which is why I can use it well now.
Recent work includes stabilising live e-commerce platforms, closing operational gaps, reducing infrastructure cost, building a multi-tenant Laravel platform from scratch, and improving workflows in business-critical systems.
I've been programming since childhood - BASIC on the family PC, dial-up internet, LAN parties, building my own rigs. Studied computing through school, college, and university, but I was already hooked long before that.
It's never just been a job.
Amarjit was Principal Engineer across two teams here, with checkout under him specifically. He made the architectural calls, not just the day-to-day ones, and he's the reason we finally got on top of a few checkout problems that had been ignored for years because nobody wanted to deal with them.
A few numbers that back it up.
Each of these has a story. Ask me about them.
Where the job's been heading
Senior Software Engineer. Forward Deployed and Product Engineer by practice.
Those two titles are newer names for how I've already worked since the start of my career - it's not a pivot. Same requirements-first, full-lifecycle approach, now including RAG pipelines, agentic tooling like Claude Code, and API integrations against models like Codex.
Owning the why, not just the how
Scoping what to build in the room with the people who'll use it, not from a spec handed down by someone else.Integration across systems
Connecting client products to in-house APIs and platforms, and the reverse, so both sides work together in production.Training & enablement
Teaching the people who inherit the system, not just handing it over and moving on.Ongoing maintenance
Staying accountable after ship - support, fixes, and iteration, not a one-time delivery.
PHP from Zero
PHP from Zero is a site I designed, built, and shipped solo - no team, no brief, no external deadline. Built to help beginners learn PHP with clear explanations and practical examples. It's a small proof of something I value: being able to scope, build, and ship a complete thing on my own.
View projectRecent writing.
I own the code. Claude decided I didn't.
Claude Code found a ToS file in my own repo, then decided I wasn't licensed to use my own API
You've been a polyglot this whole time.
Ask most engineers what they do and you'll get a framework back.
My GitHub was a graveyard. So I deleted 30+ repos.
I started on GitHub in 2010. Last week I sat down and went through every single repo. I had over 60. I got it down to 26, with a few more still to go.
Working with me
The practical details.
UK-based LTD contractor, open to the right permanent role.
Sometimes the fastest fix is someone from outside - no history with the codebase, no stake in past decisions.
LinkedIn is the best place to reach me.
Connect on LinkedIn →