Shaswat Raj · Software Development Engineer
I write code that passes review from people who don't know me.
Most of my proof is in other people's repositories: reading an unfamiliar codebase, finding the actual cause, writing the fix with tests, and getting it through maintainer review. Alongside that I build and run my own products for real users.
Looking for: SDE internships and new-grad roles on product or infrastructure teams. B.Tech CSE, BIT Mesra, graduating 2028.
Evidence
What I have done that is relevant
google-gemini/gemini-cli #20778 — cancellation bug in the core package
Cancelling a turn did not cancel the background chat-compression request. Traced where AbortSignal propagation stopped and threaded it through the execution and compression layers.
mergedpreactjs/preact #5331 and codex-team/editor.js #3040
A type-definition fix in Preact (the list attribute on valid input types) and an inline-toolbar fix in Editor.js. Small, scoped changes in widely used libraries.
mergedParser and UI edge cases in Lexical, micromark and Radix UI
Markdown import/ordered-list handling in Lexical, a CommonMark list-interruption case in micromark, and pointer/focus fixes in Radix Select and DismissableLayer.
in reviewSopKit — 605+ browser tools, 4.3M+ requests in 30 days
A client-side utility platform I built and run solo. Processing happens in the browser (WebAssembly and Web APIs), so there are no uploads and no server compute.
liveData structures and algorithms
Competitive programming on Codeforces, plus AlgoForge — an interview-prep platform I built around pattern-based problem sets.
Tools I have shipped with
How I work
- Reproduce first, then fix: every upstream PR starts from a failing case.
- Small diffs with tests, written so a reviewer can say yes quickly.
- I respond to review instead of defending the first draft.