dwg skm-2026-001 · rev 04 software engineer · backend, ai/ml systems & llm infra

Sandeep Kumar Mahto · Software Engineer

I build software that ships and holds up: backend services with real tests (34 and counting), a distributed inference platform batching to ~16× throughput with exactly-once billing, a multi-agent LLM engine with hybrid RAG that reports its own faithfulness — and the CI, containers and guardrails around all of it. Open to entry-level software engineering and AI/ML roles.

Who Sandeep Kumar Mahto
Looking for SWE · backend · AI/ML
Search projects, skills, commands…

email me résumé (pdf-ready) github linkedin see the work ↓

this is version four.
a drawing set now. the numbers didn't change.

visitor@skm:~ — zsh

try , , ,

capability brief · for recruiters & hiring managers

What I can do for your team

Entry-level software engineer (B.Tech CSE ’26, CGPA 7.14/10), open to software engineering, backend and AI/ML roles. I build backend services with real tests, and AI/ML systems that measure and report their own accuracy. The short, keyword-matched version is right here — the evidence is one click further down.

  • Backend engineering

    REST services with hashed-key auth, tiered rate limits and quota billing. Postgres with row-locked, exactly-once billing on top of an at-least-once bus.

    Python · JavaScript · SQL · PostgreSQL · Redis · REST APIs

  • AI / LLM systems

    Hybrid RAG (dense + BM25, RRF fusion, cross-encoder rerank), agents over MCP tool servers, and RAGAS evaluation with guardrails that reject ungrounded output.

    RAG · LangGraph · MCP · RAGAS · Embeddings · LLM evals

  • ML & data

    End-to-end scikit-learn pipelines (GridSearchCV, PCA), A/B testing with power analysis and SRM checks, and NLP sentiment scoring over thousands of records.

    scikit-learn · pandas · NumPy · A/B testing · NLP · statistics

  • Shipping & quality

    Docker Compose, CI on every push, Lighthouse budgets, and 34 end-to-end tests that run in ~18s with no infrastructure to stand up.

    Docker · GitHub Actions · testing · CI/CD · Prometheus

LLM answer grounding
0.911
RAGAS faithfulness, measured offline
Inference throughput
~16×
dynamic batching, same GPU
End-to-end tests
34
in ~18s, no infrastructure
Unsafe LLM actions
0
across a 50-ticket sweep
résumé — print / save as pdf email me about a role see the work

Certifications: Microsoft SQL AI Developer Associate · Oracle Generative AI Professional · Oracle AI Vector Search Professional. Reach me at skm.edu4@gmail.com.

01

The short version

long version available over coffee, or the CLI above.

I'm a software engineer (B.Tech CSE, 2026) who likes turning fuzzy requirements and messy data into software that behaves. Backend systems, tests and deployment are the craft; AI/ML is where I've chosen to pointedly apply it.

The work so far: a six-layer multi-agent support engine (MCP tool servers, hybrid RAG, a cyclic QA loop, RAGAS evals), a distributed LLM inference platform with Redis Streams, Postgres, Docker Compose and 34 end-to-end tests, an end-to-end churn pipeline, an offline AI assistant quantized to fit an 8GB laptop, and freelance automation that replaced hours of manual work. The pattern is always the same: break the problem down, measure it, write code someone else can read, ship it. Now I want an entry-level software engineering or AI/ML role to do exactly that full-time.

Also: freelance automation work on the side, three certificates I'm unreasonably proud of, and an is-a.dev subdomain I tell everyone about.

02

Stuff I've actually used

no percentage bars. those measure confidence, not skill. here's the evidence instead.

software engineering

Python & JavaScript
the two languages across 20 public repos: services, CLIs, a web UI, a Tkinter GUI and this hand-coded site.
Backend & APIs
gateways with hashed-key auth, tiered rate limits and quota billing; four MCP tool servers speaking JSON-RPC.
Databases
Postgres with row-locked reservations for exactly-once billing, SQLite + FTS5 as a shared store, Redis Streams as the bus.
Testing & CI
34 end-to-end tests in ~18s in inferfleet; this site runs 100+ jsdom checks plus Lighthouse on every push.
Docker & delivery
one codebase, one process in dev, four containers in compose — the bus is an interface, so nothing rewrote.

llm & retrieval systems

Hybrid RAG
dense + bm25 fused with rrf, cross-encoder rerank, 0.969 context precision @4 in sentinel's evals.
Agents / MCP
supervisor routing over four MCP servers, with a qa agent that rejects its own drafts before anything ships.
Local LLMs / GenAI
qwen2 & mistral 7b at 4-bit, offline on an 8GB MacBook Air (MLX). plus RAG basics from the Oracle certs.
Azure AI / Edge-TTS
SQL AI on Azure, and Text2Speech shipping on Microsoft Edge-TTS.

ml & modeling

Scikit-Learn
twelve-section churn pipeline (pipelines, GridSearchCV, PCA) and a titanic predictor at 82.68%.
A/B Testing
two-proportion z-tests, power analysis, guardrail metrics and SRM checks in the funnel study.
NLP
VADER sentiment scored over thousands of YouTube comments, exported as CSV.
ML Lifecycle
data in, model out, evaluation before deployment. in that order.

ml engineering: evals & serving

Evaluation & guardrails
ragas faithfulness 0.911, 0 unsafe outputs across 50 tickets, escalation p50 at 6.4ms. measured, not vibes.
Inference serving
redis streams + dynamic batching at ~16x throughput, exactly-once billing, 34 tests and prometheus metrics.
Streamlit / Jupyter
the Hindsight Ledger is a full streamlit app; notebooks for exploration.
Git / GitHub
20 public repos, all of them readable. most of them.

data & experimentation

Python
the common thread: churn pipelines, an ETL scraper, a streamlit app, a local llm assistant. all below.
SQL
sqlite staging layer in the youtube analyzer (primary keys, dedup) plus a Microsoft SQL AI certification.
Pandas / NumPy
comment cleaning, funnel events, cohort tables. vectorized or it didn't happen.
DBMS
schema design and queries that don't need a second pass.
Excel / Canva
50+ Canva templates fed from cleaned Excel data, zero manual entry.

still figuring out

Frontend frameworks
i hand-code html/css/js (this site is proof). haven't shipped react in anger yet.
Deep Learning
know the theory, still living in PyTorch tutorial land.
MLOps
can train a model. haven't monitored one in production yet.
Distributed Systems
read the papers, built a toy, can't explain vector clocks sober.
03

Things I've built

ranked by me, pulled live from my github. the featured ones open up: architecture, numbers, and what broke.

syncing with github...

counting the last 12 months of pushes…

  1. skm-edu4/sentinel featured
    001

    Sentinel

    • 0.911faithfulness
    • 0.969context precision @4
    • 0unsafe / 50 tickets
    • 6.4msescalation p50

    A six-layer multi-agent support engine: four MCP servers (tickets, knowledge base, CRM, action executor) over one shared SQLite/FTS5 store, a System-1 classifier that returns typed intent/sentiment/urgency JSON in milliseconds instead of burning an LLM on routing, hybrid RAG (dense MiniLM + BM25 -> reciprocal-rank fusion -> cross-encoder rerank, with query decomposition), then a LangGraph supervisor running research -> resolution -> QA with a cyclic retry when grounding fails. Auto-reply fires only on QA pass AND confidence >= 0.8, and the >$50 refund rule lives inside the MCP server so no client can bypass it. The whole pipeline runs offline with zero API keys: faithfulness 0.911, context precision @4 0.969, 50 tickets swept with 0 unsafe actions.

    what i learned: guardrails belong in the server. anything a client can skip, a client will skip.

    • LangGraph
    • MCP
    • Hybrid RAG
    • RAGAS
  2. skm-edu4/inferfleet featured
    002

    InferFleet

    • 34passing tests
    • ~16×gpu throughput
    • ≤20msbatch window
    • 4microservices

    A distributed LLM inference serving platform: a gateway doing hashed-key auth, tiered rate limits, quota billing and circuit-breaker degradation; a Redis Stream with pull-based load balancing feeding GPU workers that dynamic-batch inside <=20ms windows for ~16x throughput; two-tier caching (shared exact + local semantic cosine >= 0.90) that keeps answering while the fleet is down; and row-locked reservations settling idempotently, so billing is exactly-once under at-least-once delivery. One codebase runs as a single process for dev or four containers in Docker Compose, because the bus is an interface with two implementations. 34 tests, Prometheus metrics, live ops dashboard.

    what i learned: the bus being an interface is why one process became four containers without a rewrite.

    • Redis Streams
    • Dynamic Batching
    • Circuit Breaker
    • Prometheus
  3. skm-edu4/E-commerce_funnel_analysis featured
    003

    E-Commerce Funnel & A/B Test

    • 82.4%orders completing
    • p=3.1e-6z-test
    • +3.5%relative lift
    • £298Kper year

    Find out why shoppers abandon carts, then prove the fix actually works. Dual conversion funnels, time-aware refund matching and 25 monthly cohorts over two years: 82.4% of started orders complete, 19% of completed orders are refunded, and 27.7% of customers never come back. Then a two-proportion z-test (p = 3.1e-6) with power analysis, guardrail metrics and SRM checks certifies a +3.5% relative lift worth roughly £298K a year. Five scripts reproduce every number.

    what i learned: an a/b test you can't reproduce is just a screenshot.

    • A/B Testing
    • Cohort Analysis
    • Statistics
    • pandas
  4. skm-edu4/Customer-Churn-Prediction featured
    004

    Customer Churn Prediction

    • 12labeled sections
    • 3models compared
    • 5-foldcross-validation
    • 0api keys needed

    One file, twelve labeled sections, the entire classical ML workflow: synthetic customer data, EDA, a Pipeline + ColumnTransformer for preprocessing, logistic regression vs random forest vs gradient boosting, cross-validation, GridSearchCV tuning, precision/recall/ROC-AUC evaluation, feature importance, PCA and K-Means, then joblib persistence and inference on unseen data. Clone and run: no downloads, no API keys.

    what i learned: my first grid-searched pipeline. overfitting taught me to stop trusting training accuracy.

    • Scikit-Learn
    • GridSearchCV
    • PCA
    • joblib
  5. skm-edu4/Personal-Ai-Assistant featured
    005

    Personal AI Assistant

    • 4.5GBper model, 4-bit
    • 7Bparameters
    • 8GBmacbook air m2
    • 0cloud calls

    An assistant that never phones home: Qwen2 7B and Mistral 7B running fully offline on an 8GB MacBook Air M2 through Apple's MLX framework. 4-bit quantization shrinks each model from ~15GB to ~4.5GB so nothing swaps, with multi-model routing and session memory. Zero cloud calls after the download.

    what i learned: quantization is the difference between "runs on my laptop" and "runs on someone else's server".

    • MLX
    • Local LLM
    • 4-bit Quantization
    • Apple Silicon
04

Notes

short writing. same rule as the projects: every claim traces back to code you can run.

n.01 sentinel · guardrails oct 2026 · 3 min

guardrails belong in the server

the >$50 refund rule lives inside the MCP server, not the agent. here is why that is the only place it survives contact with a real caller.

read the note

every layer of sentinel can say no — the classifier, the supervisor, the QA agent — but the rule that actually stops money is the refund ceiling: anything above $50 waits for a human. I first put that check in the orchestration code, because that is where the decision felt like it happened.

then I wrote a second client that called the action tool directly. the check was gone. orchestration-level guardrails are suggestions to anyone holding the endpoint — another agent, a script, my future self at 2am. moving the rule into the MCP server made it non-optional: every caller passes through it, and the 50-ticket sweep ends with 0 unsafe actions.

the lesson I keep re-learning: put safety where the capability is, not where the reasoning is. anything a client can skip, a client will skip.

n.02 inferfleet · design oct 2026 · 3 min

one codebase, two deployments, zero rewrites

the bus is an interface with two implementations. that single decision is why dev runs as one process and prod runs as four containers.

read the note

inferfleet's queue could have been "redis, imported everywhere". instead the gateway and workers talk to a bus interface, implemented twice: an in-process one for development and tests, and a Redis Stream one for docker compose.

the payoff showed up in testing — the full gateway → queue → worker → billing path runs in one process, 34 tests, no infrastructure to stand up. when I moved to four containers, nothing in that path changed except which implementation got wired at startup.

the other consequence is honest failure modes: pull-based workers make load balancing a consumer-group problem, dynamic batching happens inside ≤20ms windows for ~16× throughput on the same GPU, and billing settles idempotently — exactly-once where the bus only promises at-least-once.

n.03 e-commerce · statistics oct 2026 · 3 min

an a/b test you can't reproduce is just a screenshot

p = 3.1e-6 means nothing without power analysis, guardrails and an SRM check. five scripts reproduce every number in the repo — that is the whole point.

read the note

the experiment: a +3.5% relative lift, worth roughly £298K a year, certified by a two-proportion z-test at p = 3.1e-6. those numbers sit on this page as metrics, and I am careful about them because everything upstream earns them — power analysis before the test, guardrail metrics during it, an SRM check after.

the part I would defend in an interview is not the p-value. it is that five scripts rerun the whole chain from raw data to the shipped figure. a number that cannot survive someone else running it is a screenshot, not a result.

n.04 evals · practice oct 2026 · 3 min

what I measure before I trust a number

a held-out fold for models, a grounding check for generated text, guardrails + srm for experiments. three repos, one habit: decide first what would make you distrust the result.

read the note

the churn pipeline taught me the model version of this rule: training accuracy looked excellent before tuning, and it was lying. leakage and overfitting stay silent until you force a held-out fold the model has never seen. now the fold comes first and the celebration comes after.

sentinel is the same rule for generated text. every draft is scored for grounding before anything reaches a user — the QA agent literally rejects its own output and sends it back with the ungrounded sentences attached. across the 50-ticket sweep that gate held: 0 unsafe actions, faithfulness 0.911. an llm number without a gate is a wish.

and the funnel study is the statistics version: power analysis before the test, guardrail metrics during it, an SRM check after — because a broken randomiser produces beautiful, wrong numbers. three repos, three domains, one habit: write down what would make you distrust the result, then check that first.

05

now.md

what I'm actually doing this month. updated when life changes.

now.md updated oct 2026
  • learning: distributed systems, RAG architectures, and rust on weekends
  • building: freelance automation scripts for clients, open-source experiments between them
  • recently shipped: sentinel, a multi-agent support engine, and inferfleet, a distributed llm inference platform
  • next: running those evals on a real corpus, not a toy one
  • avoiding: setup.py files
  1. 2019-21

    Senior Secondary · Holy Cross School, Ghatotand

    70%. the beginning of everything.

  2. 2022-26

    B.Tech CSE · RTC Institute of Technology, Anandi

    CGPA 7.14/10. Coursework: DSA, DBMS, Operating Systems, Computer Networks, Machine Learning.

  3. 2025

    Freelance AI Data & Automation Specialist · Remote

    Python scripts that generated, cleaned and validated large-scale datasets into structured Excel. Automated 50+ Canva templates and cut content production time by over 80%.

  4. 2025

    Three certifications, zero chill

    Microsoft SQL AI Developer Associate, Oracle Generative AI Professional, Oracle AI Vector Search Professional.

  5. now

    Class of 2026. Open to SWE & AI/ML roles.

    Looking for entry-level software engineering, backend or AI/ML work. Learning in public until someone hires me to do it full-time.

06

Say hi

no contact form. those need a backend, and I'd rather you just email me.

Hiring for an entry-level software engineering, backend or AI/ML role, or just want to argue about system design and evals? Email is the fastest route, and I actually reply.

the live résumé is one click away — print it or save it as a PDF straight from the page. Need a version tailored to a specific role? ask me for the pdf and I send the current version within a day.

+91-9955421409 github ↗ linkedin ↗ back to top ↑