Skip to content

Stack: AI agents, Node.js, PostgreSQL, React, React Native, TypeScript, Docker, AWS, Redis, Schema to deploy

Abhishek Jha

Abhishek Jha, full stack engineer

0bhishek.com — Full stackKolkata, IN
Portrait of Abhishek Jha outdoors among trees
// Schema to deploy. Solo.

I built Lonch, my own Vercel, on AWS.

Full stack engineer, 1.5 years at Code Samdevx and DealzUp. Also built Sutra AI, scheduled AI agents. Looking for a full-time or contract full stack role.

// Open to

  • Full-time & contract
  • Remote or relocate
  • Can start now
Discuss a roleResume (PDF)

// Manifesto

I buildthe back.I buildthe front.I testit first.I shipit myself.

One pair of hands from schema to deploy: database, API, web or mobile interface, pipeline and tests. At Code Samdevx that meant taking features to production in sprints. On my own products it also means owning the infrastructure and the bill.

// Languages & tools

What I work with

  • AI agents

    Agents that run on a schedule and stream every step live. My own ReAct loop with no framework, plus hard caps on steps and spend so a run can't loop forever or overspend.

    • ReAct loop
    • Tool use
    • LLM APIs
    • BullMQ cron
    • Redis Streams
    • Go
    • Python

  • Backend

    APIs, queues and databases. Validated requests, one shared error shape and structured logs, so a production issue traces back to a request.

    • Node.js
    • Express
    • Go
    • Python
    • PostgreSQL
    • Redis
    • BullMQ
    • Prisma

  • Frontend

    Interfaces wired to real data. Heavy queries rewritten, repeat reads cached, and anything that doesn't need to load first is lazy-loaded.

    • TypeScript
    • React
    • Next.js
    • Tailwind
    • Zustand

  • Mobile

    Onboarding, two-factor auth and screens that don't refetch everything on every visit. Profiled the slow ones and cut the re-renders.

    • React Native
    • React Native CLI
    • Expo
    • Formik
    • Axios

  • Infra & tests

    Isolated Docker builds, rolling deploys on ECS Fargate, static sites on S3 + CloudFront. Jest unit and integration tests on the APIs I own.

    • Docker
    • AWS ECS
    • S3 + CloudFront
    • GitHub Actions
    • Jest

Before&After

// Real numbers from my own products. First version vs what runs today.

  • Upload traffic my server pays for

    Dropdesk · files go straight to S3

    Before: 100%After: 0%

  • Most an AI run can cost

    Sutra AI · budget checked every step

    Before: ∞After: $0.25cap

  • Most steps an AI run can take

    Sutra AI · no runaway loops

    Before: ∞After: 10max

  • Live progress kept if you reconnect

    Sutra AI · Redis Streams replay

    Before: 0%After: 100%
Why each one changed

// Swipe →

Selected work

  • Demo

    № 01 — August 2026

    Lonch

    My own deploy platform. Connect a GitHub repo, Lonch builds it in an isolated Docker container and streams the logs live. Static sites go to S3 + CloudFront, backends to ECS Fargate with rolling deploys.

    Node.js · Docker · AWS ECS

    Live Code
  • Demo

    № 02 — October 2026

    Sutra AI

    Scheduled AI agents you run from the terminal. A hand-written ReAct loop (no agent framework), BullMQ for cron jobs, Redis Streams to stream each step live, and hard caps of 10 steps and $0.25 per run.

    Go · TypeScript · Python

    Live Code
  • Demo

    № 03 — June 2026

    Dropdesk

    File sharing for teams, like a small Google Drive. Uploads go straight to S3 through presigned URLs, workspaces have role-based permissions, and sign-in is Google OAuth.

    Next.js · Node.js · PostgreSQL

    Live Code
  • Uptime24 screenshot

    № 04 — July 2025 - Sept 2025

    Uptime24

    Uptime monitoring where independent validators check your site and report back over WebSockets. A hub collects their results into status pages, alerts, and incident history.

    Next.js · TypeScript · WebSockets

    Live Code
  • React Starter Plus screenshot

    № 05 — August 2025

    React Starter Plus

    An npm CLI that scaffolds a React app with JS or TS, Tailwind v4, Zustand, and a CI/CD workflow already wired up.

    NPM · React 19 · CLI

    Live Code

  • // The rest

    All 9 projects

    Demos and screenshots for everything, including the React Native apps and the npm CLI.

    See all projects

01 / 06

// 1.5 years · web & mobile

Where I've worked

  1. Nov 2025 — July 2026Mumbai, India

    Code Samdevx Pvt. Ltd.

    Full Stack Developer

    Shipped whole features on a product team, from the database to the screen, every sprint.

    • Features end to end
    • Faster slow pages
    • Tested what I built
    • Took features from database schema to API to UI to deploy, shipping in sprints through the team's CI/CD pipeline.
    • Wrote Node.js/Express APIs on PostgreSQL, with request validation, a shared error-handling middleware, and structured logs so production issues could be traced.
    • Fixed slow pages by rewriting the heavy queries, caching repeat reads, and lazy-loading the parts of the UI that didn't need to load first.
    • Wrote Jest unit and integration tests for the APIs I owned, reviewed teammates' PRs, and kept the API docs current.

    Node.js · Express · PostgreSQL · REST APIs · CI/CD · Jest

  2. Apr 2025 — Nov 2025Toronto, Canada

    DealzUp Technologies

    Full Stack Mobile Developer

    Built the vendor side of the mobile app, from sign-up to the screens vendors use every day.

    • Vendor onboarding
    • Two-factor login
    • Smoother screens
    • Built the vendor side of the app: onboarding, two-factor auth, and the login flow wired to the backend.
    • Connected screens to REST APIs with Axios and Formik, with local caching and data sync so screens didn't refetch everything on every visit.
    • Profiled the slow screens, then cut unnecessary re-renders by restructuring state and lazy-rendering what wasn't on screen yet.

    React Native CLI · REST APIs · Axios · Formik · Performance

// Same 4 steps, every feature

How the work goes

  1. Scope

    Agree on what we're building and what done looks like.

  2. Core

    Data and backend first, so everything rests on something solid.

  3. Screens

    Web or mobile, working with real data from day one.

  4. Ship

    Tested, deployed, and watched after launch.

// Long form on dev.to

Writing

All writing & notes