Architecture reviews / Technical conversations
A useful conversation.
A clearer decision.
I’m currently a Senior Engineering Manager at UOLO. Alongside my engineering leadership work, I’m open to selective architecture reviews and technical advisory conversations, depending on scope and availability.
Start with the question.
Share the technical decision, a little context and the kind of perspective you’re looking for. We can then see whether a focused conversation or review would be useful and fits my availability.
01 / Focused review
AI & Systems Architecture Review
You’re weighing an architecture decision and would value another engineering perspective.
What we can explore
- Voice and AI pipeline boundaries, interruption handling and recoverable application state.
- LLM tool boundaries, retrieval design, evaluation and observability.
- Failure scenarios, build-vs-buy trade-offs and the assumptions worth validating next.
02 / Technical discussion
Cloud & Performance Discussion
You have a latency, reliability or cloud-cost question and want help thinking through the evidence.
What we can explore
- Request-path profiling across application code, PostgreSQL, Redis and infrastructure.
- Queue boundaries, concurrency, workload isolation and capacity trade-offs.
- Which measurements or experiments could make the next decision clearer.
03 / Engineering mentoring
Technical Mentoring & Decision Reviews
You’re growing into broader technical ownership or working through a consequential system decision.
What we can explore
- Framing architecture decisions and explaining trade-offs to engineering and product teams.
- Reviewing design reasoning, operational concerns and failure scenarios.
- Building technical judgment and communicating the context behind a decision.
Scope and availability.
My current engineering leadership role remains my primary focus. Any advisory work is selective, with the scope and time commitment agreed before we begin.
For more context on my professional background:
View résumé & experience →