What I do
Three practice areas. Most engagements start with a short audit; after that I either build it myself or reinforce your team. I write code, not just slide decks.
01
Cloud architecture
Infrastructure the whole team understands — and nobody is afraid to change on a Thursday.
- —Azure landing zone design, networking, environment separation
- —Monolith → services: where to cut, and where not to
- —Cost and reliability: budgets, autoscale, a plan for a region outage
- —Terraform IaC and deployment pipelines that make sense
engagement: 2-week audit · fixed project · hourly consulting
02
Integrations and APIs
Systems that were never designed to talk start talking — reliably and predictably.
- —Event buses, queues, idempotency and retries
- —Public APIs: versioning, contracts, docs, rate limits
- —Data migrations with no downtime window
- —Observability: tracing the full path of a request
engagement: fixed project · embedded with your team for 2–3 months
03
LLM applications
From the prototype that impressed leadership to a feature users actually trust.
- —RAG on your own data: retrieval quality, not just the prompt
- —Evals and regression checks in CI, so releases stop breaking answers
- —Tool calling, permission boundaries, auditing what the agent did
- —Token cost, caching, graceful degradation when the model fails
engagement: audit · 4–6 week pilot · hourly consulting
How an engagement starts
01An email and a 30-minute call. You describe the problem; I tell you honestly whether it is mine to solve.
02A short statement of work. Scope, timeline, what counts as done. One page, no legal fog.
03Kickoff with weekly demos. Every week: a working increment and a written note on what changed.