Skip to content
View Nishaanth419's full-sized avatar
🏠
Working from home
🏠
Working from home

Block or report Nishaanth419

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Nishaanth419/README.md

Nishaanth K N

LinkedIn · Email · Portfolio

I build AI systems that work outside the notebook.

Not just the model — the pipeline behind it, the infra under it, and the context window you have to fight for every token of. I pick up whatever the problem needs. Polyglot by habit, not by resume.


things I'm actually good at

  • Tracing why a system behaves differently in prod than it did on my machine
  • Knowing where in a RAG pipeline the answer went wrong — retrieval, chunking, prompt, or model
  • Wiring together the unglamorous parts: queues, deduplication, alert routing, context management
  • Working with LLMs without trusting them — evals, fallbacks, and knowing when to not use one

layers I've gotten my hands dirty in

Retrieval Documents, embeddings, hybrid search — and the ranking decisions nobody talks about
Agent orchestration Multi-turn flows with LangChain and LangGraph, tool use, and graceful failure modes
Infra Kubernetes, Docker, Azure, event-driven pipelines that need to stay up
Model work BERT fine-tuning, prompt engineering, inference pipelines, HuggingFace
Interfaces Streamlit apps and Teams bots — whatever gets the output in front of the person who needs it

Things I've used: Python, LangChain, LangGraph, FAISS, PyTorch, Azure, AKS, Docker, Kubernetes, PostgreSQL, HuggingFace, Streamlit, SQL, Java. The list keeps changing. That's the point.


Stuff I've Worked on

SRE incident bot — RAG system for AKS cluster debugging. The hard part wasn't the retrieval. It was deduplication, conversational coherence, and getting engineers to trust it at 2am.

AKS observability dashboard — cluster health monitoring. Useful tools are boring tools.

Real-time ingestion pipeline — Kafka + RisingWave for continuous stream processing with materialized views. Fresh state without full rebuilds.

MovieLens analytics — collaborative filtering, graph analysis, text mining. The point where algorithms get real.


what's keeping me up right now

Production AI systems break in ways demos never do — the model returns something plausible but wrong, the tool call fails silently, the user asks something the system was never designed to handle. I'm interested in the gap between "it works in the demo" and "it works six months later with real users."


Pinned Loading

  1. AKS_diagnosis_Dashboard AKS_diagnosis_Dashboard Public

    A Python-based diagnostic dashboard for Azure Kubernetes Service (AKS) clusters, providing health insights and operational visibility.

    Python

  2. Delta_Writing_Risingwave Delta_Writing_Risingwave Public

    Demo project writing Delta Lake data using RisingWave — a streaming SQL database for real-time data processing from Kafka, Azure Event Hub, and Kinesis.

    Python

  3. SRE_Bot_Bosch SRE_Bot_Bosch Public

    A Virtual SRE bot that receives incident alerts via Power Automate, analyzes logs with Azure OpenAI GPT-4.1-mini, retrieves similar past incidents from Azure AI Search, and posts structured Runbook…

    Python

  4. TarkaFoods_RAG_Support TarkaFoods_RAG_Support Public

    A RAG pipeline for customer support using Qdrant + Ollama LLM, serving grounded answers with citations via FastAPI endpoints (/ingest, /query, /stream).

    Python