Software that takespayments, passes theaudit, and ships.
I design and build products end to end, then stay accountable for them in production. Right now: the booking platform for PVR Cinemas.
Companies bring me in for the parts of a product where a mistake costs money: checkout and payments, security and compliance review, and the whole journey from first click to confirmation. I have shipped through VAPT and PCI DSS reviews, so the audit is part of the plan, not a surprise at the end.
The engineering version
- Stack
- Next.js App Router, React 19, TypeScript, Redux Toolkit, Tailwind. Node and Python where needed.
- Payments
- Razorpay full lifecycle: order, auth, webhook verification, reconciliation, compensating refunds, wallets.
- Browser
- WASM codecs and Web Workers for heavy work. Virtualized tables, normalized state, memoized selectors.
- Review
- CSP, token handling, dependency audits, PCI scope on the frontend. Findings closed before launch.
Four systems, one workbench
Each drawing reads on its own. Press Run to watch it happen, or turn on engineering detail to see what runs underneath every step.
Ticket booking for 600+ cinema screens. Every payment ends in a confirmed seat or a refund. There is no third outcome.
Razorpay full lifecycle, compensating refund on booking-write failure, wallet with partial payments and split refunds, real-time QR. Open case study
Shipped
Every one of these is in production. Open any for the full story.
PVR Cinemas booking platform
Ticket booking for 600+ screens. If the payment goes through, the seat is confirmed. If it cannot be, the money comes back.
Open case study
SnapWap
Compress, convert and compare images in the browser. Nothing is uploaded, so nothing can leak.
Open case studyHR portal
Attendance, leave, onboarding and payroll for 500+ employees in one place.
Open case studyPipeline inspection classifier
Fewer false alarms in ultrasonic pipeline inspection. Accuracy up 50%, review time down 3x.
Open case studyWhat working with me looks like
Step 1: Scope
We write down what “done” means, what it costs, and what could go wrong.
Detail
User journeys, data model, payment and compliance requirements written before any code.Step 2: Build
You see a working version early and every week after. No big reveal at the end.
Detail
Next.js and TypeScript, staging on Vercel, weekly demo links, a changelog you can read.Step 3: Review
Security and payment review before launch, with findings fixed, not argued with.
Detail
VAPT findings triaged and closed, PCI DSS scope confirmed, CSP and dependency audit in place.Step 4: Launch and after
It goes live, and I stay for the month after to watch it in the real world.
Detail
Monitoring, webhook logs, refund edge cases, handover docs your next engineer can read.
How an engagement works
Fixed scope for a defined build, or a monthly retainer for ongoing work. Estimates in writing before anything starts.
Not the right fit for: Native mobile apps, pure design work, or WordPress theme tweaks.
Experience
- 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.
Writing
- Compressing images without uploading them6 September 2026
- What happens when the payment succeeds and the booking failsComing soon
- What a security audit actually asks of your productComing soon
- Why “it works on my machine” is not a launch planComing soon