Software Developer crafting production-grade software — typed APIs, real-time systems, and interfaces people actually enjoy using.
ScrolleBook marketplace with an integrated EPUB reader — highlights, notes, themes, progress tracking — plus author publishing, JWT auth with email verification, and Stripe checkout across 30+ REST endpoints.
$ react 18 / typescript / redux-toolkit / node / express / mongodb / stripe / epubjs
Real-time monitoring for 3,000+ deployed IoT devices. Live fault detection and daily monitoring workflows that cut support response times for multiple internal teams.
$ typescript / mqtt / websockets / rest apis / real-time telemetry
End-to-end production management across 6+ factory stages — kit planning, SMT, assembly, testing — with OK/NG/rework flows tracking every manufactured device, gated by role-specific backend APIs for 10+ roles.
$ typescript / node / postgresql / rbac / workflow engine
Two connected apps: a server-rendered Next.js 14 guest portal with real-time availability and dynamic pricing, and a React admin dashboard with KPI analytics, revenue tracking, and full booking & cabin management.
$ next.js 14 / react query / supabase / recharts / ssr
I like software you can lean on — the kind teams run their day on, and readers fall asleep with at 2 a.m.
I'm Samarpit — a software developer in Gurugram, currently at Mediology Software. Before that, at IOTFY, I built the unglamorous, high-stakes middle of connected products: monitoring platforms watching 3,000+ devices in the field, factory floors tracking every unit from kit to test, and real-time pipelines that shaved ~80% off critical service operations.
My happy place is the full stack — a typed API on one end, an interface people actually enjoy on the other, and a database schema in between that won't embarrass me in a year. I sweat auth flows, role-based access, and empty states.
Off the clock: grinding data structures & algorithms, studying system design, and playing chess — where, much like in production, the losing move is always the one you didn't think through.
$ cat ./toolbox
$ mailto — have a role, a product, or a stubborn bug?
Let's talk ↗Usually reply within a day. Happy to walk through code, architecture decisions, or why that one query was slow.