Backend Developer · Node.js

I build fast, reliable backends for web and mobile apps.

3.5+ years designing REST APIs, microservices and data pipelines for EdTech and hospitality products used on Android, iOS and web. Based near Mumbai, open to roles in Mumbai, Thane, Pune or remote.

3.5+ yrsNode.js in production
20K+students on APIs I built
11,000+reports generated in one run
145s → 3.7sreport latency, root-caused

Experience

Apr 2024 – Present

Backend Developer

Revoeducation Pvt. Ltd. · Mumbai · EdTech

  • Built REST APIs in Node.js for a learning platform (Android & iOS) serving 20K+ students: live lectures, recorded content and doubt resolution.
  • OTP mobile login with JWT, Redis caching on high-traffic endpoints, and MongoDB, Firestore and SQL chosen per feature.
  • Work on Target PEAK, a school-administration platform: automated reporting, WhatsApp delivery and performance fixes (case studies below).
Mar 2023 – Feb 2024

Node.js Developer

Retvens Services Pvt. Ltd. · Indore · Hospitality

  • Backend services in Node.js and Express for hospitality mobile and web apps.
  • REST APIs for community features, analytics dashboards and admin functions used by Android, iOS and web teams, plus backends for React admin panels.
  • Authentication, authorization and MongoDB storage optimized for analytics processing.

Case studies

A nightly reporting pipeline for school administrators

Target PEAK · Node.js microservices · daily reports for every level of a school system, from district down to class

Problem
Daily reports were generated once per user, even though everyone under the same part of the hierarchy saw identical content. Administrators also wanted Excel, not only PDF, and the reports had to reach them on WhatsApp.
What I did
Redesigned generation to run once per hierarchy scope instead of once per user. Added Excel (xlsx) output that shares one view model with the existing PDF path, and proved the PDF output stayed byte-identical across 13,830 test renders before changing the live path. Put generation and sending behind per-organization feature switches.
Delivery
One Excel file per scope (two sheets), sent each morning as a download link in a WhatsApp template through Wati. I chose a link over an attachment or an interactive flow so each delivery costs a single template message under WhatsApp's 2026 pricing.
Result
11,000+ reports generated and stored in S3 in a single run.
Node.jsSQLExcel (xlsx)PuppeteerAWS S3WhatsApp APICron

Hunting down a 145-second report timeout

Production 504s on report downloads

Problem
Report requests were timing out (504). The first suspect was slow SQL fan-out across thousands of rows.
What I did
Timed every stage of a single report: data ~1.1s, HTML ~30ms, Chrome ~2.4s. The remaining ~141s sat inside the caching wrapper: with Redis unreachable, the client queued commands offline and kept retrying for minutes before the fail-open fallback ran. I showed the earlier fan-out numbers were artifacts of the same stall, and proposed a fail-fast cache (no offline queue plus a command timeout).
Result
With the cache bypassed, the same report went from 145.1s to 3.7s, with identical output.
Redis / ioredisProfilingNode.js

Taming headless Chrome for PDF generation

Batch PDF rendering with Puppeteer

Problem
PDF batches were slow, used a lot of memory and sometimes failed with 30-second navigation timeouts.
What I did
Found that the shared-browser check called a method that no longer existed in the Puppeteer version in use. The error was swallowed, so every PDF launched a new Chrome that was never closed: 32 PDFs left 32 browsers using 9.4 GB of memory. Fixed the check, and switched the page-load wait from networkidle0 to load because the report HTML has no external resources.
Result
In testing, block-level PDFs dropped from ~5s to ~1s, and the intermittent timeouts went away.
PuppeteerPerformanceMemory

WhatsApp OTP for login and account recovery

Auth service · Wati WhatsApp Business API

Problem
OTPs went out only by SMS. The product wanted WhatsApp delivery as well, without making login fragile.
What I did
Added WhatsApp OTP delivery alongside SMS for sign-up, resend, password reset and two-factor login. The sender never throws and has a 10-second timeout, so a WhatsApp outage can't block a login. Logs mask phone numbers and never contain the OTP.
Result
When some messages seemed to be "dropped", I traced it to the provider holding broadcasts for 2–71 minutes, not to our code.
Node.jsJWTOTPREST

Projects

AI Chatbot

Full-stack · runs on a locally hosted LLM

A chatbot powered by a local model through Ollama. The Node.js + TypeScript backend keeps conversation context so multi-turn answers stay coherent, and a React chat interface sits on top.

Node.jsTypeScriptReactOllama

AI Text Summarizer

Web app + REST API

Summarizes long-form text with a local LLM and returns bullet-point, short or long summaries, each shaped by its own prompt design.

Node.jsTypeScriptReactPrompt engineering

Skills

Languages
JavaScript (ES6+), TypeScript
Backend
Node.js, Express.js, REST API design, microservices, JWT and OTP auth, cron jobs, Puppeteer
Data
MongoDB, MySQL, Microsoft SQL Server, Google Firestore, Redis; schema design, indexing, query tuning, caching
AI / LLM
LLM integration, Ollama, prompt engineering
Cloud & tools
AWS (EC2, S3), Git, React.js
Education
B.E. Computer Engineering, St. John College of Engineering and Management, Palghar (2019–2023), CGPA 8.21