I like understanding whybefore deciding how.
Software engineer in Noida / Delhi NCR. I build the parts of a product where a mistake costs money, and I stay around to make sure they keep working.
Currently at Appinventiv on the PVR Cinemas platform. Open to full-time roles and freelance projects. Replies within a day.
Four things I keep coming back to
Understand why before how
I want to know why a product is built the way it is before I decide how to build the next part of it.
Simple over clever
Simple architectures, explicit state, and code another engineer can read six months later.
Own the outcome
Not just the feature. The payment that reconciles, the audit that passes, the month after launch.
Reduce complexity
Whether it is payments, state, or performance, the goal is to take complexity out, not add to it.
What that means in code
- State
- Normalized entities, one slice per module, selectors do the deriving, components stay dumb.
- Boundaries
- Modules talk through events, not imports. A payment write is idempotent or it does not ship.
- Types
- TypeScript strict everywhere. If a state is impossible, the type should say so.
- Review
- CSP, dependency audits and token handling are set up in the first week, not the last.
Where I have worked
- 2025 to nowAppinventiv TechnologiesFrontend Developer
Frontend for the PVR Cinemas booking platform and an enterprise HR portal, in parallel.
- Feb to Mar 2025VDT Pipeline Integrity SolutionsSoftware Development Intern
Defect detection algorithm optimization on ultrasonic inspection data.
- 2021 to 2025I.M.S. Engineering College, GhaziabadB.Tech, Computer Science and Design
Data structures, software design, side projects in React and Python.