I build backend systems and cloud platforms that stay fast, observable and maintainable long after launch day.
For the last seven years I have worked with fintech, logistics and healthcare teams — turning ambiguous requirements into architecture, shipping production services, and leaving behind documentation and tests the in-house team can actually own.
Four areas where I do my strongest work. Most engagements combine two or three of them.
Designing service boundaries, REST and gRPC APIs, event-driven pipelines and data models that hold up as traffic grows.
Infrastructure as code on AWS, containerised deployments on Kubernetes, and CI/CD pipelines that ship safely many times a day.
Accessible, fast front-ends in TypeScript and modern frameworks, wired to well-documented APIs and sensible state management.
Observability, SLOs, load testing and incident review practices that turn firefighting into predictable operations.
Rebuilt a double-entry ledger and settlement engine handling multi-currency transactions for a fintech serving small businesses.
Outcome: Cut end-of-day reconciliation from 3 hours to under 6 minutes.
Streaming ingestion service processing GPS and sensor events from 18,000 vehicles, with live dashboards for dispatch teams.
Outcome: Sustained 40k events/second at p99 latency under 120 ms.
Patient-facing appointment and records portal built to WCAG 2.1 AA with strict audit logging and role-based access control.
Outcome: Reduced call-centre booking volume by 34% in the first quarter.
Every engagement starts with a written problem statement, constraints and success metrics. Good architecture follows a clear question.
I ship in thin vertical slices behind feature flags so stakeholders see progress weekly and risk stays contained.
Runbooks, dashboards and tests are part of the deliverable. Software you cannot operate is not finished software.
I take on a small number of engagements each quarter so every client gets focused attention. Tell me about your product and timeline.