I take frontends that have outgrown their architecture and turn them into systems a whole team can build on.
7+ years building enterprise SaaS and real-time systems. React, Next.js, TypeScript, FastAPI. Design systems, live streaming interfaces (WebSockets, SSE, WebRTC), and workflow authoring engines.
Staff role
Whenever an app outgrows its stack, the hardest part is keeping product velocity alive while changing the engine underneath. I look for the cleanest seams, draw strict TypeScript contracts at the boundaries, and migrate one route or module at a time. Customers keep using the app, and the team never has to pause shipping.
When an app stutters, my first instinct isn't to start wrapping every hook in useCallback. It's almost always because the browser is juggling too many DOM nodes. At Scrut, when 50k security events streamed over WebSockets, we buffered incoming data off-screen and virtualized the table so only visible rows hit the DOM. Keep the DOM small and the tab stays fast.
A good design system should save engineers time, not trap them in review discussions about margins and paddings. I anchor themes and spacing to CSS custom properties at the document root. That way, dark mode, tenant customization, and layout density happen dynamically at runtime without having to touch dozens of component files.
I've never liked fixing weird framework quirks with random setTimeout workarounds or superstitious code. If lifecycle hooks fire out of order or bindings break, I pull down the framework repository and step through the compiler AST. That habit is how I ended up finding and fixing bugs in Svelte core and Qwik.
As autonomous agents become part of developer workflows, handing them master API keys with blanket write access is a huge blind spot. One malformed prompt can delete data or trigger irreversible actions. I built AgentGate because agents need a proxy layer: per-tool permissions, structured audit trails, and an immediate way to cut off access.
Senior Software Engineer
Promoted from SDE II (Jun 2024) to Senior (Apr 2025), same team
Senior Software Engineer
Vue.js React
Freelance Software Engineer
Freelance Software Engineer
Krafty Nuxt
Software Engineer
Software Engineer
Software Developer Intern
Permission control for AI agents over MCP. It sits between an agent and a server like GitHub, Stripe or Slack, enforces per-tool permissions, scans responses for security problems, logs every decision, and revokes access instantly. The agent never gets the real API key, only a gateway URL.
Give an agent a GitHub token today and it gets everything that token allows. There's no way to say “read repos, never delete them.” This is my answer to that.
A companion-first mental health check-in app for India. The idea is that it should feel like texting a friend, not opening a treatment tool. Built with FastAPI, Postgres/pgvector, React 19, Vite, Tailwind v4 and shadcn/ui, with NVIDIA NIM and Langfuse for tracing.
It's a prototype and I say so in the README. Anything safety-critical—crisis-language detection and clinical suggestions—sits behind an eval pipeline that tests retrieval and prompt outputs before it ships. The engineering docs cover the pipeline design, vector schema, and eval test cases.
5 pull requests merged into Svelte and one into Qwik: element bindings, a contenteditable regression, beforeUpdate firing twice, onDestroy ordering, each-block bindings with spread syntax. Small fixes, but they meant reading someone else's compiler until the bug made sense.
Google Summer of Code 2018. Wrote a Python tool that drops you straight into an analyzer's code and steps through it with a debugger interface like pdb, so debugging an analyzer got about as easy as writing one.
Google Code-in mentor, two terms, with coala, the open source static analysis org. Also 2 merged fixes into man-group/pytest-plugins and an ESLint plugin of my own for nested-if detection.