A bit more about me.
I'm a software engineer based in India. I build product surfaces, backend state, realtime protocols, data contracts, and AI workflows with explicit guardrails.
I'm most interested in the part after a product demo: when retries, permissions, partial failure, and real people enter the picture, but the experience still needs to feel simple.
My work spans backend-heavy products, data systems, and applied ML. The common thread is making state, failure, and evaluation legible enough that a system can be trusted and improved.
How I work
- 01
Keep the contract clear
I prefer clear product boundaries, simple state transitions, and systems that are easy to reason about under failure.
- 02
Make correctness visible
For backend and data work, I care about validation, retries, idempotency, edge cases, and monitoring that shows what happened.
On record
- Focus
- Backend-heavy product systems that hold up under real use
- Operating range
- Realtime protocols, AI workflows, evals, data contracts, dashboards, and launch paths
- Strengths
- State, idempotency, auth boundaries, edge cases, proof paths, reliability
- AI/data
- Human-approved AI actions, retrieval, quality gates, trusted analytics, monitoring
- Experience
- Software Development Engineer (Contract), MyNotedApp, Jan. 2025–Jun. 2025
- Education
- Master of Science in Electrical Engineering, Columbia University, May 2022
- Education
- Bachelor of Technology in Electronics and Communications, VIT, Vellore, May 2020
Say hello
For product systems that need to hold up beyond the happy path, or just to talk shop.