I'm most useful when the decision is expensive and hard to reverse: an architecture you'll live with for years, an inference stack that works today and won't at ten times the load, a team you're about to double. Least useful as an extra pair of hands on a settled plan.
Open-ended advisory for founders and engineering leaders: what to build, what to buy, what to stop doing. Useful when the decision is expensive and reversible only at cost.
Hands-on training for teams working in Java and Spring Boot — service design, testing, performance, and the patterns that keep an enterprise codebase workable three years in. Delivered from years of building and reviewing exactly these systems.
Designing systems that hold up: service boundaries, data flow, streaming and messaging, and the cloud footprint underneath. Particularly relevant for AI and voice products where latency is a product feature, not an implementation detail.
Turning a product ambition into a sequenced technical plan — what gets built in which order, what the team needs to exist first, and where the real risk sits.
How to hire, structure and grow an engineering org that ships. Drawn from leading teams as CTO and from mentoring engineers through senior levels.
A structured read of an existing system with findings you can act on: bottlenecks, coupling, failure modes, and the two or three changes that would matter most.
An assessment of how a system handles authentication, tenancy, data isolation and its exposed surface — with prioritised remediation rather than an undifferentiated list.
Consulting and advisory across software architecture, AI and voice systems, technology strategy, team building, and architecture or security reviews. Engagements range from a single review to ongoing advisory alongside a team.
Conversational and voice AI systems, streaming architectures, and enterprise Java and Spring Boot. That combination — real-time AI on top of systems that have to stay up — is where most of my work sits.
Yes. I'm based in Bengaluru and have run remote engagements since 2015 through Pyloom Innovations. Email or WhatsApp is the fastest way to sort out time zones.
Email [email protected] or send a WhatsApp message. Mention which service you're interested in and enough context about the system or team, and I'll come back with whether I'm the right fit.