Backend architecture
Clean boundaries, data models, tenancy, RBAC, jobs, caching, and systems that still make sense when scope grows.
TH
/ Loading — please wait
/ Loading — please wait
/ Contact / 07
Tell me what you're building, what is stuck, and what outcome would make this conversation useful. A plain summary is better than a polished pitch.
/ Send a message
Email and message are required. Name and conversation type help me route the reply.
/ Good fit
Open to opportunities. Best conversations include a concrete constraint, current tradeoff, or production symptom.
Clean boundaries, data models, tenancy, RBAC, jobs, caching, and systems that still make sense when scope grows.
Slow queries, missing indexes, N+1s, load problems, and the practical fixes that move production metrics.
REST, tRPC, queues, consistency tradeoffs, and API contracts that stay easy to reason about.
I read for fit first, then send useful next questions. For anything urgent, email is still the cleanest channel.
/ Other places
Browse work history and public notes, then send the message when you have enough context.
/ FAQ
Backend engineering roles, architecture reviews, production debugging, and focused full-stack work where the backend matters.
Most weekdays, within 24 hours. Short, specific context gets the fastest useful response.
Send the context first. If it is a fit, the next step is usually a short call or written notes.