Skip to content
View asingleneuron's full-sized avatar

Block or report asingleneuron

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.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

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

Report abuse
asingleneuron/README.md

πŸ‘‹ Hi, I'm Shobhit Upadhyaya

Principal Data Scientist | LLM / RAG / Conversational AI

πŸ“ Bangalore, India
πŸ“§ [email protected]
πŸ”— LinkedIn
πŸ”— YouTube


πŸš€ About Me

Principal Data Scientist with 16+ years of experience (9+ in ML/AI) specializing in:

  • LLM-powered conversational systems
  • Retrieval-Augmented Generation (RAG)
  • Multi-turn reasoning & ambiguity resolution

Built production AI systems serving:

  • πŸ‘₯ ~148K users
  • ⚑ ~4K queries/day
  • πŸ“š ~5K internal knowledge documents

πŸ‘‰ Improved system deflection from 26% β†’ ~50%


🧠 AI Service Desk β€” LLM + RAG Conversational System

Enterprise-scale conversational AI system designed to handle ambiguous user queries using LLMs, RAG, multi-turn reasoning, and retrieval optimization.


πŸš€ Overview

This system powers an AI Service Desk (AISD) used by ~148K employees, handling:

  • ⚑ ~4,000 queries/day
  • πŸ“š ~5,000 internal knowledge documents

πŸ‘‰ Improved automation/deflection from 26% β†’ ~50%


🧩 Problem Statement

Users frequently submit vague and ambiguous queries, such as:

  • β€œI need help”
  • β€œUnable to login”
  • β€œReset password”

Key Challenges:

  • Missing context in user queries
  • Over-specific refined queries causing LLM failures
  • Poor UX (long, unstructured responses)
  • Scaling ambiguity resolution across topics

πŸ—οΈ System Architecture

User Query ↓ Query Understanding (Rephrase + Context) ↓ Semantic Retrieval (OpenSearch - Top 100) ↓ Reranking (Cohere - Top K) ↓ LLM Reasoning Layer ↓ Answer Generation ↓ Structured Response (UX Layer)


πŸ”§ Key Innovations

1. 🧩 Multi-Turn Conversational Intelligence

  • Transitioned from single-turn β†’ context-aware system
  • Maintains conversation history for better reasoning

2. 🌲 Dialogue Model (Rule-Guided)

  • Decision-tree-based disambiguation
  • Handles structured flows for known topics
  • Example flow:
    • Reset password β†’ Ask OS (Windows/Mac) β†’ Ask login status β†’ Provide resolution

πŸ‘‰ Improved deflection: 26% β†’ 40%


3. 🀝 Mutual Understanding Model (LLM-Based)

  • Handles unconfigured / scalable scenarios
  • Uses top-k retrieved documents to generate follow-ups

πŸ‘‰ Impact: +10% deflection

4. πŸ”„ Query Simplification (Failure Recovery)

Problem:
Refined queries became too specific, causing LLM to fail (~10%)

Solution:

  • Generate multiple simplified queries
  • Remove unnecessary constraints
  • Retry retrieval + generation

πŸ‘‰ Results:

  • +10% answer coverage
  • +5–6% deflection

5. 🧾 Wall of Text β†’ Structured UX

Problem:

  • Long LLM responses reduce readability in Slack

Solution:

  • Structured output:
    • πŸš€ Quick Solution
    • Step-by-step instructions
    • Notes / context

πŸ‘‰ Impact:

  • +2–3% deflection
  • Improved user engagement

πŸ“Š Final Impact

Component Improvement
Multi-turn baseline 26%
Dialogue Model +11%
Mutual Understanding +10%
Query Simplification +5–6%
UX Optimization +2–3%
Final Deflection ~50%

πŸ› οΈ Tech Stack

  • LLMs: LLaMA (llama4.scout)
  • Architecture: RAG, Multi-turn reasoning
  • Search: OpenSearch (semantic retrieval)
  • Ranking: Cohere rerank
  • Cloud: Oracle Cloud Infrastructure (OCI)
  • Data: ATP DB
  • Languages: Python, SQL

🧠 Key Learnings

  • Ambiguity handling is critical in real-world AI systems
  • Retrieval quality directly impacts LLM performance
  • Over-specific queries can degrade answerability
  • UX design is as important as model performance

🎯 Future Improvements

  • Adaptive retrieval strategies (dynamic top-k)
  • Better query intent classification
  • Reinforcement learning from user feedback
  • Latency optimization for real-time interaction

πŸ† Achievements (Top 1%)

  • πŸ₯ˆ Ericsson ML Challenge β€” 2nd / 4120
  • πŸ₯‰ USAID Forecasting Challenge β€” 3rd
  • πŸ₯‰ MakeMyTrip β€” 3rd / 3556
  • πŸ† BrainWaves (SocGen) β€” Finalist (4926)

🎯 What I Focus On

  • Building production-grade LLM systems
  • Solving ambiguity in real-world AI systems
  • Improving retrieval + reasoning + UX together

πŸ“¬ Let’s Connect

If you're working on:

  • LLM systems
  • RAG architectures
  • Conversational AI

Feel free to connect or collaborate!

Pinned Loading

  1. hackathons_solution hackathons_solution Public

    Find the solution of machine learning competitions I am participating.

    Jupyter Notebook 43 27

  2. amazon-ml-challenge amazon-ml-challenge Public

    Amazon machine learning hiring challenge

    Jupyter Notebook 22 5

  3. Ericsson-Machine-Learning-Challenge Ericsson-Machine-Learning-Challenge Public

    This repository contains the winning solution of Ericsson Machine Learning Hackathon.

    Jupyter Notebook 10 8

  4. leetcode-solutions leetcode-solutions Public

    This repository contains the solutions of leetcode problems

    Python 1