What I can do as an engineer
Seven areas of professional capability a hiring company can lean on. Each one is grounded in production code I have written, open-source repositories I maintain, and long-form writing I have published. The point of this page is to make the depth legible before any conversation starts.
Seven areas of capability
Each one is a body of work, not a brochure. Follow any tile through to a deeper view, then read the repos and essays that back it.
What is true in every lane
The six defaults below show up regardless of which capability is in play. They are the bar I hold myself to in production code.
Safe defaults, day one
Row-level security on every table, real audit logs, no secrets in the repo. The defaults you would actually want if you cloned the code at midnight.
Observability before features
Structured logs, error tracking and a health endpoint go in before the first feature. You can see the system before you ship the system.
Boring stack, sharp tools
Postgres before Mongo. Server-rendered HTML before another SPA framework. Reach for the exotic only when the boring option genuinely runs out.
Senior IC, end to end
From schema to deploy script, the person on the email is the person at the keyboard. No handoff layers, no junior shuffles.
Write the diagram first
An ADR, a Mermaid sketch, a one-pager of trade-offs. If the system cannot be explained in a paragraph, it is not ready to ship.
Open source by default
Generic infrastructure goes public, MIT-licensed. Eighteen repositories and counting. If a problem is general, the answer should be shared.
Why this matters to a hiring team
Most engineering CVs claim a stack. This page points at the running systems behind each claim. The repositories are public. The essays cite their sources. The architecture diagrams are in the wiki. A hiring team can audit the depth before the first interview, which is the way it should be. Sarma is taking PAYE full-time roles only until 14 February 2030; the hire-me page explains the shape of that.
The evidence behind every lane
Browse the public repositories, read the past-work write-ups, then look at the hiring page.
Nineteen open-source repositories
Everything I rely on in production, published MIT-licensed. Read the code before reading anything else.
- slipstream, token-efficient coding agent runner
- SarmaLink-AI, 14-engine LLM gateway
- forge-infer, minimal LLM inference server in Rust
- shipyard, multi-tenant SaaS starter with RBAC and billing
- lsmdb, LSM-tree storage engine in Go
- raftkv, Raft KV store with fault-injection harness
- sandboxd, WebAssembly sandbox in Rust
- agent-orchestrator, durable multi-agent workflows
- voice-agent-starter, sub-second WebRTC voice loop
Past work, written up plainly
The projects I can talk about publicly, with scope, stack and outcome. The same shape a hiring team would see in a technical review.
Past workFor a hiring team
Sarma is taking PAYE full-time roles only until 14 February 2030. Senior IC, specialist or founding-engineer shape, in the UK or remote.
Hire me, the page for companies