INFRASTRUCTURE PLATFORM ENGINEER IV · UF IT

Curiosity.
Code.
Real-world
impact.

I’m Sai Sri Harsha, an Infrastructure Platform Engineer IV at UF IT. I maintain a LiteLLM gateway on a shared 9B+ tokens/day platform, and build FastAPI services, Redis/Celery streaming workflows, and retrieval systems.

BASED IN THE WORLD OF

Backend engineering. AI infrastructure.
Thoughtful interfaces.

THE PERSON BEHIND THE CODE01 / INTRO
Sai Sri Harsha Guddati
Harsha.Engineer. Builder. Always learning.
A LITTLE CONTEXTUniversity of Florida✳Tata Consultancy Services✳From backend to AI
9B+tokens / day

Shared AI platform behind the LiteLLM gateway I maintain and extend

2,000+concurrent streams

Real-time token delivery across 12+ generative AI workflows

10+microservices

Production services deployed and operated on Kubernetes

The work behind
the numbers

ENGINEERING / CONTROL PLANE TO CLIENT

The systems
behind the scale.

IDENTITY + ROUTING

Shared AI gateway

  1. Applications
  2. LiteLLM gateway
  3. Model providers

API-key authentication, RBAC and team isolation define access. Provider routing and failover, team budgets, and audit logging keep shared usage accountable.

LiteLLMAPI keys / RBACBudgetsAudit logging
9B+ tokens/day on the shared platform

WORKERS + EVENT DELIVERY

Concurrent token streaming

  1. Celery workers
  2. Redis Pub/Sub
  3. SSE clients

Background execution and event delivery are separate from the browser-facing stream. My work redesigned this path for concurrent token delivery across generative AI workflows.

FastAPICeleryRedis Pub/SubServer-Sent Events
2,000+ concurrent streams · 12+ workflows

EVIDENCE + REGRESSION CHECKS

Retrieval and evaluation

  1. OCR + chunks
  2. Hybrid retrieval + rerank
  3. Source-attributed answer

Document extraction and metadata-filtered retrieval feed answers with source attribution. Evaluation checks relevance, groundedness, tool calls, schema conformance, latency, and provider failures.

BM25EmbeddingspgvectorEvaluation harnesses
Excel/PDF analysis · PostgreSQL/pgvector

01 / SELECTED WORK

Ideas, made real.

All projects

Three implementations to inspect: layered command-risk analysis, local browser Q&A, and a persistent document-retrieval pipeline.

02 / A LITTLE MORE HUMAN

More than
a tech stack.

My work sits at the intersection of backend architecture, AI infrastructure, and the people who use them.

I’m based in Gainesville, Florida, with an M.S. in Computer Science from the University of Florida. Before UF IT, I built enterprise services at TCS in Hyderabad.

At UF IT, I maintain and extend the LiteLLM gateway on a shared platform processing 9B+ tokens a day. My work also spans NaviGator Prompt Builder, document retrieval, model evaluation, and a departmental Data Science Agent.

ACADEMIC BACKGROUNDM.S. Computer Science
University of Florida · 2025
ENGINEERING THREADHyderabad, India
Gainesville, Florida
The full journey

03 / HOW THE WORK CONNECTS

From the inside, out.

Three layers.
One complete experience.

01

Execution & delivery

Services that move work

FastAPI request handling, Celery workers, Redis Pub/Sub events, and SSE clients. Separating background execution from token delivery.

FastAPI / Celery / Redis / SSE
02

Evidence & evaluation

Retrieval that can be inspected

OCR, chunking, metadata filters, hybrid search, and reranking. Regression checks for groundedness, tool calls, and output schemas.

BM25 / embeddings / pgvector / evaluation
03

Product & operations

Interfaces through deployment

Next.js and TypeScript products backed by services deployed with Kubernetes, Terraform, F5 load balancing, and GitLab CI/CD.

Next.js / Kubernetes / Terraform / GitLab

04 / NOTES & THINKING

A place for
the thinking, too.

Projects show what I build. The blog is where I share the ideas, discoveries, and lessons along the way.

Read the journal

A FEW THINGS I BELIEVE IN

Measure before
optimizing.

Reliability over cleverness. Simple systems scale better. Infrastructure as code, and documentation as a first-class feature. Principles that keep the work grounded when the technology gets complicated.

HAVE SOMETHING IN MIND?

Let’s build
something useful.

AI, software, or an interesting problem. I’d love to hear about it.