AI Multi-Agent Orchestration Platform
A production agentic system that decomposes complex tasks, dispatches specialised agents, maintains working memory, and routes tool calls through a typed execution graph.
Harshit S
Software Engineer · Java · TypeScript · React
Building scalable web applications with Spring Boot, React, distributed services, and reliable automation.
I build enterprise-scale applications with Java, TypeScript, React, and distributed service architectures. My work focuses on systems that stay maintainable as their usage and business impact grow.
I develop Spring Boot microservices and integrate REST, GraphQL, and gRPC APIs across distributed systems. I also build reusable React and Next.js components, modernize legacy Angular applications, and design scheduling and rate-limiting mechanisms for busy services.
Recent work includes AI-assisted KYC and credit decision integrations, gRPC APIs that improved customer data synchronization accuracy by about 95%, and SFTP automation for more than 15 banking clients. I take features through design, testing, deployment, and production support.
I care about practical delivery: clear service boundaries, useful automation, and tests that catch regressions before release. My toolkit includes Playwright, Jenkins, GitHub Actions, AWS, PostgreSQL, MongoDB, and the AI-assisted development tools I use to move from idea to dependable implementation.
Full-stack depth from interface to service. Select a scenario below to see which layers activate across a production workflow.
Longer context doesn't make retrieval irrelevant — it changes what retrieval is for.
2025-05Every agent decision that can't be reviewed is a gap in your production architecture.
2025-03The skill isn't writing better prompts. It's knowing when the prompt is the wrong abstraction entirely.
2025-04Treating the context window like a conversation history is the first mistake most teams make when building agents.
2025-06JSON mode doesn't save you from an underspecified schema. It just makes the failure more consistent.
2025-07Most teams choose the most capable model and then discover their latency requirements. That's backwards.
2025-09You can't improve what you can't measure. In LLM systems, measurement is the hard part.