Hi, my name is

Vamshi Krishna Chatla

Java Backend Engineer

Backend systems engineer building production GenAI services.

Chennai, India

ResumeEmailLinkedInLeetCode

#About

I'm a backend engineer with 3+ years at Zoho Corp, working across Java, Spring Boot, and distributed systems.

For the last two years my focus has been production GenAI infrastructure — RAG pipelines, agentic tool-calling, and LLM orchestration across multiple model providers — all on a Java stack.

I care about systems that stay correct and fast under load: clean service boundaries, sensible caching, and observable failure modes.

#Skills

Languages

  • Java
  • Python
  • SQL

Backend

  • Spring Boot
  • Microservices
  • REST APIs
  • Multithreading

Data & Messaging

  • MySQL
  • Redis Cluster
  • Apache Kafka

Cloud & DevOps

  • AWS
  • Docker
  • Kubernetes

Search / NLP / GenAI

  • RAG
  • LLM Orchestration
  • Tool Calling
  • Apache Lucene
  • OpenNLP

Foundations

  • Distributed Systems
  • System Design
  • DSA

#Experience

Member Technical Staff · Zoho Corp

Jun 2023 — Present

Chennai, India

  • Build backend services on Java and Spring Boot for a production AI assistant used across Zoho products.
  • Designed a RAG pipeline for grounded question-answering over large document corpora.
  • Implemented LLM orchestration routing requests across multiple model providers (OpenAI, Qwen, Llama).
  • Owned microservices with Kafka messaging and Redis Cluster caching for low-latency reads.

#Selected Work

RAG Pipeline for Grounded Q&A

Retrieval-augmented generation over large document corpora with source-grounded answers.

  • Java
  • Spring Boot
  • RAG
  • Vector Search
  • LLM

Problem

TODO: What needed solving? (e.g. users needed accurate answers grounded in internal docs, not hallucinated ones.)

What I built

TODO: What you built + how. (e.g. chunking + embeddings + retrieval, prompt assembly, citation of sources, guardrails.)

Impact

TODO: Impact / numbers. (e.g. answer relevance, latency, corpus size, query volume.)

Async Query Processing Service

Non-blocking service for long-running query workloads with backpressure and retries.

  • Java
  • Multithreading
  • Kafka
  • Redis

Problem

TODO: What needed solving? (e.g. synchronous processing timed out on heavy queries.)

What I built

TODO: What you built + how. (e.g. async task queue, worker pool, Kafka for decoupling, Redis for state.)

Impact

TODO: Impact / numbers. (e.g. throughput, p99 latency, reliability under load.)

Multi-Provider LLM Orchestration

Routing layer that selects and falls back across LLM providers with tool-calling support.

  • Java
  • LLM
  • Tool Calling
  • Resilience

Problem

TODO: What needed solving? (e.g. single-provider dependency, cost/latency tradeoffs, rate limits.)

What I built

TODO: What you built + how. (e.g. provider abstraction, routing policy, fallback, tool-calling schema.)

Impact

TODO: Impact / numbers. (e.g. providers unified, cost saved, uptime under provider outages.)

#Get in touch

I'm open to backend and GenAI engineering roles. The fastest way to reach me is email — I'll get back to you.

Email

vamshikrishnachatla@gmail.com

LinkedIn

in/vamshikrishnachatla816

LeetCode

u/vamshikrishnachatla