ConceptGraph AI
Course-aware GraphRAG that turns PDFs into searchable concept graphs, reranks evidence, and returns page-grounded answers.
New Delhi, India · IST
I build intelligent systems that survive beyond the demo.
I’m a Software Engineering student at DTU, building retrieval systems, reliable backends, and data-heavy products. The interesting part usually starts after the happy path.
Open to engineering internships & research collaborations.
Course-aware GraphRAG that turns PDFs into searchable concept graphs, reranks evidence, and returns page-grounded answers.
A PostgreSQL-backed job runner that makes retries, worker crashes, lease recovery, and cancellation visible—with Python and Go workers.
Lap-time prediction and Monte Carlo simulation for comparing pit-stop strategies using real 2021–2025 F1 data.
A mood-aware journaling and conversation product designed around secure personal data, recent context, and restrained AI assistance.
Parses résumés locally, scores five ATS dimensions, compares job descriptions, and exports actionable feedback.
Data Analyst Intern
Built a mutual-fund analytics platform covering 40 schemes, 10 datasets, 87K+ records, and 4.5 years of NAV history.
Python · Pandas · SQL · Power BIOpen Source Contributor · Gold Engineer
Ranked 20th of 592 nationally, earning 475 contribution points and the Gold Engineer distinction.
Open source · Engineering collaborationOpen Source Contributor
Finished eighth of 422 participants, in the top 2%, with 1,680 contribution points.
Open source · Rank 8A short selection from my FixNearby and Open Connect work: product features in one codebase, interaction and reliability fixes in the other.
Select a record to inspect the contribution trail.
On my FixNearby fork, I worked across the React client and Express/MongoDB server. The largest slice was a set of export and continuity tools—worker contact cards, booking calendars, comparison CSVs, civic-issue GeoJSON, and recently viewed workers—alongside runtime and authorization guardrails.
Added browser downloads for vCards, iCalendar bookings, worker-comparison CSVs, and civic-issue GeoJSON. Each utility is small, testable, and attached to the screen where the data is already being reviewed.
Added bounded, de-duplicated recently viewed worker history with a local-storage fallback, so returning to a useful profile does not require a new search round-trip.
Added health/readiness endpoints, a graceful shutdown lifecycle, and request correlation IDs. Together they give deploys and incident logs clearer boundaries without introducing another service.
I’m interested in the parts of software that stop being obvious once the demo works: retrieval quality, retries, distributed state, data consistency, and product edge cases.
Most of my recent work sits between AI systems, backend engineering, and data infrastructure. Outside that, I spend time solving DSA problems, reading about system design, and occasionally running or playing badminton.
Live solved counts, platform ratings, and a LeetCode difficulty split are collected in a separate practice record.
Open comp. prog. record ↗Semantic similarity finds nearby language. It does not automatically preserve prerequisites, hierarchy, or evidence chains.
A pipeline is easier to trust when every transition has an owner, an invariant, and a cleanup path.
The happy path demonstrates possibility. Production is the accumulation of unusual inputs, interrupted requests, and ambiguous ownership.
Running, badminton, F1, and engineering reading. Currently thinking about reliable RAG evaluation and what happens when a backend has to recover.
What I’m exploring now ↗Build something small. Understand it deeply. Make it a little better.
I’m open to software, AI systems, backend, and data engineering internships, research collaborations, and interesting engineering problems.