Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Freelance · Node.js

Freelance senior Node.js developer for back ends that are already live

I am one senior engineer who builds and runs Node.js back ends: REST APIs, background jobs, live sockets and the Linux servers they sit on. My own product, TaxiDex, is a Node.js API with more than 1,000 routes that I operate in production. I join your team remotely, by the project or month by month.

Who hires a freelance Node.js engineer?

  • Teams with a Node.js API in production and nobody senior who owns it end to end.
  • Founders whose back end was built by a contractor who has moved on, and who need it stabilised before anything new ships.
  • Product teams that need one more senior pair of hands on the API, the queues or the real-time layer.

What do I do with Node.js?

  • API design and buildREST APIs in TypeScript on Node.js with AdonisJS, NestJS or Express, with validation on every route and one code path for each business rule.
  • Background jobs and schedulersQueues on BullMQ and Redis for the work that must not block a request, and scheduled jobs for recurring bookings, reports and reconciliation.
  • Real-time featuresSocket.IO channels that keep web and mobile clients in the same live state, including behind nginx, where idle connections are easy to lose.
  • Database workData models, migrations and query tuning on MariaDB, MySQL and PostgreSQL, with schema changes run and checked before the code that needs them.
  • Deploys and operationsPM2 or Docker behind nginx on Linux, scripted deploys, error reporting with Sentry and a check on the live system after every release.
  • Taking over an existing codebaseI get it building and deploying first, write down what is at risk, and then fix things in order of risk instead of rewriting.

Which Node.js problems am I usually called in for?

  • nginx shows 502 and the API is gone

    The process crashed, was never restarted or listens somewhere nginx does not look. I find which one from the logs before touching the configuration.

    The step-by-step fix
  • The app will not start because the port is taken

    Usually an old process that never exited, or two process managers fighting over one app.

    The step-by-step fix
  • It falls over when traffic climbs

    Leaked file handles and sockets show up as EMFILE long before the server runs out of CPU.

    The step-by-step fix
  • Live connections drop after a minute

    A proxy timeout closes idle WebSockets, and clients reconnect in a loop that looks like a bug in the app.

    The step-by-step fix
  • One unhandled error takes the whole process down

    An emitter with no error listener is enough to stop every request that was in flight.

    The step-by-step fix
  • An upgrade is stuck between CommonJS and ES modules

    A dependency went ESM-only and the build no longer loads it. There is a correct way through that does not pin old versions forever.

    The step-by-step fix

How does working with me on Node.js work?

  1. Send me the repo and the symptomA link or archive of the code and what goes wrong in production. I reply within 24 hours.
  2. A technical callWithin 48 hours, a call with whoever knows the API best, to read the main routes together.
  3. A written plan for the back endThe scope names the endpoints, jobs and deploy steps I will touch first, and what waits.
  4. Sprints and a weekly callKickoff is typically inside two weeks. Two-week sprints follow, with short written updates and one fixed overlap call a week.
  5. Safe releasesA backup comes before each production change, with a tested rollback and a check afterwards.

What do people ask about Node.js work?

Do you work alone or with my developers?

Either. I can own the back end outright, or join your team, review code and take the hard parts myself.

Which Node.js frameworks do you use?

AdonisJS for my own SaaS, NestJS and Express on other products. I work in the framework you already have rather than asking you to switch.

Can you take over a Node.js back end somebody else wrote?

Yes. I start with a short written review of the code, the deploy process and the risks, so you know what you have before I change anything.

What do you do when the process runs out of file handles?

I raise the limit where the service starts and stop opening thousands of files at once. I wrote a fix page on the EMFILE error that explains both.

How do you work across time zones?

With a shared task board, short written updates and one fixed overlap call each week for the decisions that need a conversation.

Proof

Products I built with Node.js

All projects

Own product · Taxi dispatch SaaS

TaxiDex

My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.

TypeScriptNode.jsAdonisJSNext.js

Attendance platform

Workforce

A field app, an admin console and a self-hosted Node.js server for push and reconciliation.

FlutterDartNode.jsExpress

Next step

Need a senior Node.js engineer?

A discovery call within 48 hours, and a kickoff typically inside two weeks.