Usman Ali · Backend Engineer

I build the backend that holds everything together.

Distributed systems, data pipelines, and the APIs beneath them: the parts of a product you can't screenshot. One of them is drawn below.

FIG.01Pass Gallery migration: system at a glance
SOURCE PLATFORMSPicTimePixiesetShootProofZenfolioINGESTPuppeteer + APIsSQSwork queueECS WORKERSNode.js · ×NPASSGALLERYMongoDBjob + gallery state
The distilled path. The failure-and-resume detail lives in the teardown.
0k+images / clientPass Gallery, 2025 · per migration run
< 0hper clientdown from a multi-day manual process
§01Teardowns

Backend systems I've built in production, most recent first. The lead piece is a full teardown; the rest give the shape and the stack.

  1. 2025

    Pass Gallery migration

    A resumable, distributed pipeline that moves 500k+ images per client between gallery platforms in under 24 hours. It preserves folder structure and metadata, and recovers from mid-run failure without restarting the whole job.

    Node.js · AWS ECS · SQS · Lambda · MongoDB

    Read →
  2. 2025

    Paismo: Nexus API & HRMS backend

    A multi-tenant HRMS backend and public workforce API covering payroll, time & attendance, leave, and document generation, with bi-directional accounting sync.

    Node.js · NestJS · PostgreSQL · Unified.to · Nx monorepo

    Read →
  3. 2024

    Furniture Clinic data pipelines

    Automated ingestion of 30,000+ Amazon orders per month, pulled from Seller Central and the Advertising API into a unified MongoDB store that feeds live Power BI reporting.

    Node.js · MongoDB · Power BI · Amazon SP-API · Advertising API

    Read →
§02Writing

Field notes from production: what held, and what broke.

Get in touch

For backend, distributed systems, and platform work.