Technical Product Lead · Solutions Architect · Head of Systems & Data Engineering. Twelve years turning fragile, siloed, non-compliant systems into infrastructure nobody has to worry about — at a fraction of what managed cloud charges to run it.
The choices that cost the least in the moment tend to be the ones you pay for most later. These are three I made differently — and why they matter at scale.
The naive pipeline — detect, transcribe, think, speak — makes the user wait three to six seconds before hearing anything. Multiplexed HTTP/2 and sentence-level synthesis bring time-to-first-byte under 500 ms. The architecture is the moat, not the model.
On a constrained budget you cannot buy a segregated data tier. You can encrypt every PII field with a KMS-issued key before it touches the disk. Zero plaintext at rest is not a compliance checkbox — it stops an attacker even after the database server is compromised.
Aurora Multi-AZ, Kubernetes, managed observability stacks — those are not sold at cost. A stateless compute cluster with WAL-G backups and an enterprise CDN delivers the same resilience for $1,900/month where the managed equivalent bills $38,000.
Two systems shipping in production today. Full methodology and architecture on the technical case page.
Tell me the shape of the problem — the latency target, the compliance requirement, the architecture nobody wants to touch, or the infrastructure bill that arrived last month. I read every message and reply personally, usually within a day.
Tell me the shape of the problem — the budget, the latency target, the regulator, the architecture nobody wants to touch. I read every message and reply personally.
Prefer LinkedIn? Message me there →