Bandile
Ndlovu.
I turn ambiguous business problems into systems that survive contact with real traffic, real budgets, and real teams.
I got into tech the long way — curiosity first, formality later. What kept me here was the moment a system I designed handled a load nobody planned for and simply kept going. Since then I've worked across financial products, business intelligence, and cloud platform tooling, mostly in TypeScript, C#, and AWS.
I care about the decisions that get expensive later: data contracts, failure modes, cost models, and handover. Where I'm going is more of the same at a larger scale — architecture work that stays close to the code, plus writing that makes the reasoning public instead of tribal.
How I decide.
Constraints before diagrams
Budget, latency, team size, and compliance decide the shape. Everything else is decoration.
Boring where it counts
Novelty belongs in the product, not in the datastore or the deployment model.
Design for the handover
If the team cannot operate it without me, the architecture is incomplete.
One slice in production
A thin end-to-end path in production beats a complete design on a slide.
- TypeScript, C#, SQL.
- AWS (Lambda, API Gateway, DynamoDB, S3), Terraform, CI/CD pipelines.
- Postgres, warehouse modelling, dbt, event-driven pipelines.
- Domain modelling, service boundaries, cost-aware architecture, technical handover.
- Strata — a multi-cloud handler for provisioning, drift, and cost in one interface.
- Deeper event-driven patterns and the operational side of serverless at scale.
- Notes on architecture trade-offs, published when they are worth reading.
My CV is available on request.
It isn't published publicly. Send a short request and I'll share a private, time-limited link once approved.
Request CV