UK-based software engineer. Around five years of production experience. I design and ship AI infrastructure and platform-grade software, end to end — most of it open source, all of it production-shaped, every project shipped with a whitepaper and an architecture diagram.
What pulls me back to the desk every weekend is the quiet thrill of building something from scratch. A blank repository, a problem worth solving, a system that did not exist yesterday and ships today. Most of that work used to live in private repositories. Earlier this year I made a deliberate decision to put years and months of it into the open as a contribution back to the community that gave me the tools.
The result: twelve MIT-licensed repositories, fifty-plus long-form engineering essays, a live multi-provider AI gateway, and now — actively looking for the next chapter on a team that is shipping something serious.
|
|
|
|
Every repo ships with a project page on sarmalinux.com/products — whitepaper, architecture diagram, quick-start guide.
A few good entry points into the fifty-plus long-form essays:
- 📄 SarmaLink-AI failover deep dive — how 14-engine failover actually works in production
- 📄 Building Agent Orchestrator — the journaled-Postgres pattern behind deterministic replay
- 📄 Why I open-sourced 12 repos — the reasoning, the trade-offs
- 📄 Terraform Stack vs Pulumi vs SST — honest comparison
I am open to permanent, full-time software engineering roles across the United Kingdom — remote, hybrid, or on-site. Senior or mid-level individual-contributor positions in AI infrastructure, AI engineering, platform engineering, backend, or full-stack development. Not taking contract or consulting work.
If you have a role I might be a fit for:
built in the open · MIT all the way down