hello —Creative engineer · Backend & AI · Open to work

GaneshReddy.

I build backend systems for AI-assisted health tech and ONDC commerce.

Three years on Go, RAG pipelines, multi-agent orchestration — currently shipping the Clinical Copilot at UnitedForHer.

↑ a clinical copilot, abridged
3 yrs
shipping in production
5k+
tx/day on ONDC
18%
latency drop on CCOP
23%
faster client cycles

Selected work

Three years.
Backend, agents, protocols.

01UnitedForHer

Clinical Copilot

UnitedForHer · 2025–present

A wrapper API over RAG + LLM for AI-assisted prescription generation. Doctors get grounded suggestions, edit inside dynamic templates with variable injection, and export as PDF.

  • Go
  • OpenAI
  • RAG
  • React
  • PDF render

18% latency drop · adopted end-to-end

Read the case study →
02Shayr Omnichannel

Adya Multi-Agent Platform

Shayr Omnichannel · 2023–2025

Autonomous multi-agent orchestration over LangChain + OpenAI. A no-code UI lets non-engineers configure agent behaviour declaratively, replacing per-client integration work.

  • LangChain
  • OpenAI
  • Microservices
  • Node.js
  • MongoDB

23% shorter dev cycles · 27% faster deploys

03Shayr Omnichannel

ONDC Buyer/Seller Protocol

Shayr Omnichannel · 2023

Core protocol modules for ONDC commerce — data-mapping, API surface, and interoperability for retail and logistics partners. MVP delivered in the planned six-week window.

  • Spring Boot
  • Go
  • REST APIs
  • MySQL

5k+ tx/day · 6-week MVP

Deep dive · Case study 01

Clinical Copilot.

The wrapper that hides the LLM — and the latency, and the hallucinations.

UnitedForHer · 2025–present · Go · OpenAI · RAG · React

18%
latency drop, end-to-end
1
wrapper holding the contract
5+
artefact types reusing the pattern

Context

UnitedForHer is a women's health platform where doctors run virtual consults and produce clinical artefacts — prescriptions, follow-up letters, lab requests. Growth was outpacing the time clinicians had to write these by hand.

Problem

Templates were rigid. Patient context — history, prior consults, allergies — was scattered across systems. Every prescription was drafted from scratch, and the consult slowed with it.

Approach

A wrapper API between the doctor's dashboard and a RAG + LLM stack. One pass: retrieve grounded clinical context, draft the artefact, pipe it through a dynamic template with variable injection, live preview, and PDF export.

Architecture

DoctorWrapper APIRAGLLMTemplate + PDFVector DBguardrails + auditclinical KB
the wrapper holds the contract — everything else is replaceable.
The wrapper holds the contract.
Everything else is replaceable.

Decisions

  • A wrapper, not direct LLM calls.

    One chokepoint for guardrails, rate limits, audit logging, and template variables. Every clinical artefact passes through the same lane.

  • Cached embeddings.

    The same patient's records get hit many times per consult. Re-embedding on every call would have killed latency.

  • Render-time variable injection.

    The LLM produces narrative with {{patient_name}} placeholders. Resolving at render time keeps templates human-editable.

Challenges

  • Hallucination safety.

    Prescriptions are high-stakes. Strict prompt scaffolding, retrieval grounding for every clinical claim, and a final clinician-facing review before PDF export.

  • Latency.

    Doctors won't wait. Embeddings cached; retrieval and the LLM call run in parallel where the prompt doesn't depend on retrieved context.

  • Doctor trust.

    Adoption depended on the tool feeling like a faster pen, not a black box. Live preview + edit-then-export kept the clinician in the seat.

Outcome

  • 18% reduction in end-to-end response latency.
  • Expert dashboard adopted as the clinician's primary workspace — prescription generation, session handling, PDF export.
  • The pattern (wrapper → RAG + LLM → template) now reused across clinical artefacts on the platform.

Stack

What I work in.

Backend & Systems

Node.js

  • Node.js
  • Go
  • Spring Boot
  • Microservices
  • REST APIs

AI / LLM

RAG

  • LangChain
  • RAG pipelines
  • Multi-agent orchestration
  • OpenAI API
  • Tool-calling agents
  • Prompt scaffolding

Frontend

React

  • React
  • React Native
  • TypeScript
  • Tailwind CSS
  • Redux
  • ES2022+

Data

MongoDB

  • MongoDB
  • MySQL
  • Redis
  • Vector stores

About

I draw the systems before I write them.

— me, in a notebook somewhere

The engineer.

Started as an intern at Eunimart, then Shayr (Adya), where I went from API contributor to multi-agent system builder in three months. Now at UnitedForHer, building the Clinical Copilot.

Backend is home — Go, Spring Boot, message buses, microservices. The AI work followed naturally; LLMs are interesting because of the orchestration problems they create, not the model itself.

The artist.

I draw — sketches, line studies, the occasional system diagram before I write any code. The drawing isn't a hobby alongside engineering; it's how I reason about systems before committing them to a repo.

The sketches in the margins of this site are the same ones in my notebook before each project starts.

Contact

Let's build
something.

— say hi