-
01 until 2024
Foundations DAV Boys, Chennai
Finished school with 92% in CBSE Class XII and picked computer science.
-
02 2024
Init VIT Vellore
Started a B.Tech in CSE with a Data Science specialisation.
-
03 Aug - Nov 2025
Outreach Perplexity Campus Partner
Ran sign-up and referral drives and product demos across campus.
-
04 2026
Deep end Building from first principles
A database engine, a compiler, a distributed job queue, RAG and agent systems, an ML yield model and a routing solver.
-
05 2026 - 27
Next Consensus, inference, streaming
RaftKV, TinyInfer and StreamGuard are on the bench.
ShreyansChowdry
I build the parts of software most people never see: storage engines, job queues, retrieval pipelines and solvers.
- ChronoDB 126 unit tests
- ChronoDB 5 branches, 2,000+ versioned rows
- PGARA -20.4% cycles vs linear scan (geomean)
- PGARA -80% spill memory traffic vs linear scan
- QueueForge 99.2% jobs completed with 30% injected failures
- QueueForge 410/s ingest throughput
- TravelCraft -45% travel time per day
- TravelCraft 0 opening-hour conflicts (v1: 37% of days)
- CodeAtlas AI 93.3% top-15 retrieval hit rate
- CodeAtlas AI 312 ms average retrieval latency
- ResearchMate 6 agent nodes in a LangGraph state machine
- ResearchMate -40% LLM tokens via reference stripping
- Die-Yield Failure Prediction +7.8% AUC-PR over baseline
- Die-Yield Failure Prediction +8.8% recall on latent failures
- KernelLens AI 3+ log sources correlated
- KernelLens AI 10+ simulated failure scenarios
8 projects, each with a repo, a README and a number I can defend. Open one for the details.
-
A relational database engine with Git semantics: commit, branch, merge and time-travel your data.
- unit tests
- 126
- branches, 2,000+ versioned rows
- 5
- pages, LRU buffer pool
- 4 KB
- Built a Git-style relational database engine from scratch with immutable commits, copy-on-write branching, time-travel queries and conflict-aware three-way merge over a commit DAG.
- Wrote the storage layer (LRU buffer pool, B+ Tree indexes, WAL with ARIES-style redo recovery, mark-and-sweep GC), backed by 126 unit tests and benchmarked against SQLite.
- Python
- FastAPI
- Next.js
- TypeScript
-
A compiler for a C subset whose register allocator learns which paths are hot from a profiling run, then spends registers where they save the most cycles.
- cycles vs linear scan (geomean)
- -20.4%
- spill memory traffic vs linear scan
- -80%
- benchmark runs verified against the interpreter
- 50/50
- Built, in a team of 5, a full compiler for a C subset: DFA lexer, LL(1) recursive-descent parser, semantic analysis, pruned SSA, an SCCP/GVN/DCE optimiser and a cycle-counting RISC simulator; I owned the lexer, parser, AST and IR generation.
- Its profile-guided register allocator (per-value MDPs solved by policy iteration, sealed-bid auctions on the chordal interference graph) cut cycles by 20.4% and spill memory traffic by 80% vs linear scan across 50 benchmark runs; written up as an IEEE-format paper.
- Python
- JavaScript
-
A job queue built on Redis primitives that survives crashed workers and flaky jobs.
- jobs completed with 30% injected failures
- 99.2%
- ingest throughput
- 410/s
- jobs lost to dead workers
- 0
- Designed a distributed job queue on Redis sorted sets, hashes and Pub/Sub with priority scheduling, delayed execution and PostgreSQL as the durable source of truth.
- Added heartbeats, a reaper that re-queues jobs from crashed workers, backoff retries and a dead-letter queue; in a 500-job load test with 30% injected failures, 99.2% completed at 410 jobs/s ingest.
- Python
- Redis
- PostgreSQL
- Docker
-
Trip planning solved as a routing problem: which places, which day, what order, inside opening hours.
- travel time per day
- -45%
- opening-hour conflicts (v1: 37% of days)
- 0
- p95 solve time
- <25 ms
- Modelled trip planning as a Team Orienteering Problem with Time Windows and built an Iterated Local Search solver (greedy insertion, 2-opt/Or-opt, inter-day relocate and swap).
- Across 405 benchmark trips, cut daily travel time by 45% and eliminated the opening-hour conflicts that broke 37% of the old planner's days, at p95 solve time under 25 ms.
- JavaScript
- React
- Vitest
- Vercel
-
Ask a repository questions in plain English and get answers grounded in the code, with citations.
- top-15 retrieval hit rate
- 93.3%
- average retrieval latency
- 312 ms
- vector + keyword fusion
- RRF
- Built hybrid retrieval fusing pgvector cosine search and Postgres full-text search via Reciprocal Rank Fusion, with 1-hop import-graph expansion over tree-sitter code chunks.
- Reached a 93.3% top-15 retrieval hit rate on hand-annotated queries at 312 ms average latency; streamed answers over SSE with inline file citations.
- FastAPI
- pgvector
- Claude API
- Next.js
-
Six cooperating agents that search the literature, read the PDFs and write up the research gaps.
- agent nodes in a LangGraph state machine
- 6
- LLM tokens via reference stripping
- -40%
- live paper APIs (OpenAlex, Semantic Scholar)
- 2
- Orchestrated a 6-node LangGraph agent pipeline that searches OpenAlex and Semantic Scholar, parses full-text PDFs, extracts structured findings and synthesizes citation-backed research gaps.
- Stripped bibliographies during PDF parsing to cut LLM token usage by up to 40%; shipped with Docker Compose and GitHub Actions CI.
- LangGraph
- Gemini
- FastAPI
- PostgreSQL
-
Predicting which passing dies on a wafer will fail final test, and explaining why.
- AUC-PR over baseline
- +7.8%
- recall on latent failures
- +8.8%
- positive class: heavily imbalanced
- 4.2%
- Predicted latent die failures on a highly imbalanced (4.2% positive) wafer dataset by gradient boosting over 549 parametric, KD-tree spatial and PCA-compressed features with wafer-grouped CV.
- Lifted AUC-PR by 7.8% and recall by 8.8% over the baseline model, confirmed by a 2,000-resample wafer-level bootstrap; explained predictions with per-die occlusion attribution.
- scikit-learn
- SciPy
- pandas
-
Turns noisy kernel and system logs into correlated incidents with a likely root cause.
- log sources correlated
- 3+
- simulated failure scenarios
- 10+
- Python
- FastAPI
- Next.js
What I'm building next. Each one moves up to the list above, and onto my résumé, once it ships with numbers.
-
Planned, 2026
RaftKV
Fault-Tolerant Key-Value Store
Leader election, log replication and snapshots, checked for linearizability under network partitions.
- target ops/s on a 5-node cluster
- 8,000
- target fault-injection runs checked
- 500
- Go
- gRPC
- Protocol Buffers
-
Planned, 2026
TinyInfer
LLM Inference Engine
KV cache, paged attention, continuous batching and int8 quantisation, benchmarked against Hugging Face.
- target throughput vs Hugging Face generate()
- 3.2x
- target GPU memory with int8 weights
- -47%
- Python
- PyTorch
- FastAPI
-
Planned, 2027
StreamGuard
Real-Time Fraud Detection
Streaming features, low-latency model serving, drift monitoring and shadow deploys.
- target p99 scoring latency
- 14 ms
- target PR-AUC
- 0.84
- Kafka
- Redis
- LightGBM
- ONNX
- MLflow
Internships, collaborations, or a question about one of the projects. I reply within a day or two.