Skip to content
Utkarsh Jaiswal
Available for select workMumbai, India

Backendsystems thathold.

I am Utkarsh Jaiswal, a backend engineer building multi-tenant Node.js and PostgreSQL systems, data migrations, search infrastructure, and AWS deploy paths for products that cannot afford fragile foundations — and I leave the team able to run them.

Resume Read the writing

Role
Software Development Engineer II at Shuru, on the Balio platform
Focus
Multi-tenant NestJS/PostgreSQL systems, data migration, and the AWS layer
Open to
Senior roles, and a small number of contract engagements
24
California cities and counties served
Shuru / Balio
142K
legacy compliance and expense reports
Shuru / Balio
4TB
JSON searched in Elasticsearch
WhiteCrow
+18%
ITR filings after the 26AS parser
Fisdom
Stack: Node.js, TypeScript, NestJS, PostgreSQL, Elasticsearch, AWS, Docker, Python, SQS, SES, EventBridge, MySQL, GitHub Actions
01

Selected work

Three systems, and what changed

Each one is the same shape: what was breaking, what I built, and what it did to the numbers.

  1. Architecture: agency users reach a NestJS API that enforces RBAC route guards and tenant-scoped queries against PostgreSQL, where a JSONB form engine holds per-tenant field configuration and revision snapshots. Notifications and program-window recomputation leave the request path through SQS and EventBridge-triggered ECS tasks that send mail via SES. A Python migration tool reads the 38-database legacy estate and emits JSON for V2 imports.ASYNC PATHtenant-scopedenqueueJSON imports24 agenciescities · countiesNestJS APIRBAC · tenant scopePostgreSQLJSONB form engineLegacy V138 DBs · read-onlyPython migration142K reportsSQS + EventBridgeoff request pathECS tasksSES mail
    01Jul 2025 — Present

    Replacing a 38-database legacy compliance system while production stays online

    Shuru · Software Development Engineer II · Mumbai

    A 20-year-old grant and housing-compliance system serves 24 California cities and counties, with a legacy estate spanning 38 databases and 142K compliance and expense reports — and it has to be replaced without taking production offline.

    I own the backend architecture for the NestJS/PostgreSQL V2 platform: a JSONB-backed form engine so agencies configure conditional fields and tenant overrides without a deployment, revision snapshots and field-level diffs that preserve grant amendment audit trails, and RBAC with per-resource CRUD/APPROVE/REJECT permissions enforced through route guards and query-level tenant scoping. A Python migration tool carries 200–500-field legacy records across per-jurisdiction mappings, validating budgets and required fields, folding in client Excel corrections, and emitting JSON for V2 imports.

    24

    cities and counties

    Production V1 stays read-only throughout, and notifications and program-window recomputation run off the request path on SQS, SES, and EventBridge-triggered ECS tasks.

    • NestJS
    • TypeScript
    • PostgreSQL (JSONB)
    • Python
    • AWS (ECS, SQS, SES, EventBridge)
  2. Architecture: API clients pass a per-client rate limiter, which escalates lockout windows on the Fibonacci sequence for repeat offences inside 24 hours, before reaching the Node.js REST API. On AWS instances, the API queries a 4 TB JSON corpus in Elasticsearch and uses MySQL with a scheduled maintenance event. Sign-in is Google login over OAuth.AWS INSTANCEStuned queriesAPI clientsRate limiterFibonacci lockoutGoogle loginOAuthREST APINode.jsElasticsearch4 TB JSONMySQLscheduled event
    02Jan 2022 — Mar 2025

    Protecting search over a 4 TB Elasticsearch corpus from runaway API clients

    WhiteCrow Research · Software Engineer · Mumbai

    Talent search ran over a 4 TB JSON corpus, and an unthrottled API surface meant one heavy client could degrade the platform for everyone.

    I owned backend development for three years — REST APIs, data models, and client integrations — optimised the Elasticsearch queries and database operations behind search, and built an anti-scraping rate limiter with per-client request budgets and Fibonacci-escalating lockout windows for repeat offences inside 24 hours.

    4TB

    JSON corpus searched

    I also automated application deployments to the AWS instances through deployment scripts, implemented Google login for authentication, and used MySQL events for scheduled database maintenance.

    • Node.js
    • Elasticsearch
    • MySQL
    • AWS
    • REST API design
  3. Architecture: a Python parser reads the government Form 26AS and pre-fills the filing journey, which files returns directly through ERI client registration. Taxpayers self-file on the CodeIgniter portal, and eMitra and CSC partner channels file on a taxpayer's behalf.pre-filledForm 26ASgovt. document26AS parserPythonFiling journeyCodeIgniterERIfiles directlyTaxpayerself-filingeMitra / CSCassisted filing
    03Apr 2021 — Dec 2021

    Automating tax-data extraction behind an 18% rise in ITR filings

    Fisdom (now part of Groww) · Software Engineer · Jaipur

    Self-filing stalled wherever a taxpayer had to key in data that already sat in a government document, and assisted filing needed a route through government partner channels.

    I built a Python Form 26AS parser to automate taxpayer-data extraction, and implemented E-Return Intermediary (ERI) client registration with eMitra and CSC integrations so partner channels could file on a taxpayer's behalf.

    +18%

    ITR filings

    ITR filings rose 18%, and the PHP CodeIgniter portal was secured with CSRF protection.

    • Python
    • PHP (CodeIgniter)
    • MySQL
    • ERI
    • eMitra / CSC

All five engagements and side projects

02

What I do

Four kinds of work

Scoped engagements with a target we agree before I start. Not open-ended staff augmentation.

  • 01

    Legacy replacement and migration

    • Schema and JSONB modelling
    • ETL and data migration
    • Read-only cutover plans
  • 02

    Multi-tenant platforms

    • Tenant scoping and RBAC
    • Configurable form engines
    • Audit trails and revisions
  • 03

    APIs and integrations

    • API design and versioning
    • Stripe, Razorpay, OAuth
    • Transactional mail
  • 04

    Infrastructure and deploys

    • AWS (ECS, SQS, SES, EventBridge)
    • CI/CD with GitHub Actions
    • Docker and deploy scripts

Scope, process, and questions

03

Writing

Notes from production

Multi-tenant data models, migrations, search, and rate limiting — written from the systems above.

04

Free tools

Free things I built to stop explaining

Browser-only, no sign-up, nothing sent anywhere. The rate limiter playground runs six algorithms against real traffic shapes and hands you the config.

05

Recommended

Tools I point people at

Two things I recommend when the question is not one I bill for.

  • Hosting

    Where to put a small site

    Not everything needs ECS and a Postgres cluster. For a brochure site, a WordPress install, or a first project that has to be live this week, shared hosting is the right answer — and Bluehost is what I point people at when they are not going to maintain a server.

    Shared and WordPress plansNo server to maintainLive the same day

    See Bluehost plans

  • Privacy

    What a VPN is actually for

    It does not make you anonymous. It moves who can see your traffic from the network you are sitting on to the provider you picked — which is the trade you want on hotel wifi, and very little use against the sites you are logged into. ICE Privacy is where I send people when that is the trade they need.

    Traffic off untrusted wifiYour ISP sees one endpointNot an anonymity cloak

    Visit ICE Privacy

06

Work together

Two ways in

Hiring for a senior role, or bringing a system that has to hold. Pick the door that fits — I read everything and reply myself, usually within a day.

For hiring teams

Looking for someone who has already run APIs, rate limits, search, and deploys in production — not someone who will learn it on your roadmap.

For contract work

Selected engagements on Node/TypeScript backends, PostgreSQL, Elasticsearch, and AWS — queues, mail, rate limiting, and the deploy path. A small number at a time.