Work
Everything below runs in production today, serving 20–30k users. Each is presented the way it lives in the codebase — as a document type with fields, behavior, and consequences.
The platform's entire revenue system — 40+ DocTypes on ERPNext, from payment plan to GL posting.
An EMI lifecycle state machine with single-writer settlement eliminated double-booked payments; auto-posted settlement Journal Entries removed manual reconciliation.
An automated code-review pipeline: every pull request is read by an LLM, grounded in the changed code's context, before a human ever sees it.
Reviewers start from a machine-annotated diff instead of a cold one — cutting review turnaround and catching the boring bugs before humans spend attention on them.
Six payment gateways — including an education-loan EMI provider — behind one pluggable routing layer.
Every callback verified with constant-time comparison, deduplicated, and recoverable — dropped callbacks are swept back in on a schedule.
One shared core serving 4–5 institutions and 20–30k users — 25+ custom Frappe apps, 250+ DocTypes.
New institutions onboard without forking the platform; the core stays clean through Frappe version upgrades.
Production AWS EKS provisioned end-to-end with ~9k lines of Terraform, deployed by Helm and ArgoCD.
A documented 43% infrastructure cost reduction while raising the security posture — with the runbook to prove it.
Live GPS school-bus tracking for parents, built on Frappe's realtime stack.
Parents watch the bus approach in real time; the system degrades gracefully instead of failing when networks do.
Four production React SPAs and a tri-lingual parent mobile app on top of the Frappe backend.
An exam engine that survives network loss mid-exam, and portals that 20–30k users rely on daily.
Client and institution names are kept private. Numbers are real and happily discussed in an interview.