The story behind the portfolio
I'm Shaswat Raj — a computer science student, software engineer, open-source contributor, and persistent builder. My journey has been less about collecting technologies and more about repeatedly turning curiosity into working software.
79+
external PRs merged
Open-source repositories I don't own.
4.3M+
SopKit requests
A privacy-first browser tool platform.
5,000+
live participants
Event infrastructure built for Bitotsav.
1,350+
college network target
CampusLoop's verified student network.
Class 7 →
01
I started coding before I had a career plan. The first projects were small, sometimes messy, and mostly driven by one question: “Can I build this myself?” That habit stayed. I still learn fastest by turning an idea into something people can actually use.
College
02
At BIT Mesra, software stopped being just a subject. I started treating every project as a chance to understand the whole system — product thinking, UI, APIs, databases, deployment, performance, and what happens when real users show up.
Open source
03
I began contributing beyond repositories I own. My portfolio documents 79 external pull requests merged into open-source projects, including a fix merged into Google's gemini-cli. Open source taught me to read unfamiliar code, explain trade-offs, respond to review, and ship changes that have to survive someone else's standards.
Products
04
I've built developer tools, AI systems, web products, infrastructure, and experiments — from SopKit and SopPlayer to Debo, IndexFast, MCP Pure, and CampusLoop. The common thread is ownership: I enjoy going from “this could be useful” to architecture, implementation, deployment, iteration, and feedback.
A few things I'm proud of
SopKit taught me how performance, SEO, product design, and infrastructure meet in one product. It grew into a privacy-first suite of browser tools with millions of requests while keeping processing client-side.
Bitotsav taught me that software behaves differently when thousands of people depend on it at the same time. I worked on event infrastructure, verification, real-time systems, and operational reliability.
Open source taught me humility. A contribution is not finished because it works on my machine. It has to make sense in an unfamiliar codebase, survive review, and be useful to people I may never meet.
CampusLoop represents the kind of product I want to keep building: something with a real user problem behind it, technical depth underneath it, and enough ambition to force me to learn along the way.
I prefer understanding who needs something and why before deciding what to build.
I don't wait until I know everything. I build a small version, measure what breaks, and learn from reality.
Frontend, backend, infrastructure, deployment, debugging, documentation — I'm comfortable crossing boundaries.
Whether it is a product or an open-source codebase, I want my contribution to be easier to understand and maintain.
I'm looking for environments where I can be trusted with meaningful engineering problems, learn from people who are better than me, and contribute beyond the narrow definition of a job description. I care about strong engineering, thoughtful products, and teams that value ownership.
I still have a lot to learn. That's part of the point.