Skip to content
SUSHIL

SUSHIL KUMAR

Portrait of Sushil Kumar smiling in a yellow bomber jacket on a beige background
// builds it, ships it, keeps it running
Discuss a projectSee my work

// manifesto

I build front.I build back.I test everything.I scale & deploy.

I'm one developer who can take an idea from a rough sketch to a product that's running and holding up: the screens people see, the API and data behind them, and the servers it all lives on. For you that means fewer handoffs, fewer surprises, and one person who understands how the whole thing fits together. Bring me the problem, and I'll help you shape it, build it and keep it running.

What I work with

// languages & tools

Frontend

Interfaces and admin panels that stay fast and clear when the data gets busy. Server-rendered and mobile-first by default, because most people arrive on a phone.

  • TypeScript
  • React
  • Next.js
  • Redux Toolkit
  • Tailwind
  • shadcn/ui
  • Motion

Backend & data

APIs, auth, queues and data that keep working as more people show up. I shape the schema and the endpoints together, so they fit each other.

  • Node.js
  • Fastify
  • PostgreSQL
  • Prisma
  • Redis
  • BullMQ
  • pg-boss
  • MongoDB
  • Zod

Servers, delivery & tests

I set up the servers too: reverse proxy, process manager, CI/CD and test suites, so a release is routine instead of an event.

  • Linux servers
  • Docker Compose
  • Caddy
  • PM2
  • GitHub Actions
  • AWS S3
  • Stripe
  • Jest
  • Playwright

3D & motion

Scroll-told brand sites where one 3D object carries the story. Models, labels and light are generated in code, so the pages stay light and still work without WebGL.

  • three.js
  • React Three Fiber
  • GSAP
  • ScrollTrigger
  • Lenis
  • GLSL shaders
  • WebAudio

AI & media pipelines

Pipelines where rules decide the facts and a language model only picks the taste: transcription, scene detection and rendering that pick up where they left off after a crash.

  • Claude API
  • OpenAI
  • Gemini
  • WhisperX
  • ffmpeg
  • OpenCV

// where I put my effort

MarketVSfocus

// what the market rewards, and what I choose to get good at. Not better, just mine.

Speed
What the market leans toward:Ship fast, with AI writing much of the code. Often the right call.
Ship fast too, and understand every line that reaches production.When something breaks at 2am, someone has to know why. I'd like that to be me, not a guess.
Scope
What the market leans toward:A specialist per layer, with handoffs in between.
One person across the layers, so every decision keeps its reason.I'm not the deepest expert in every layer. I'm good at making them fit, and I say so when a project needs a specialist.
Tools
What the market leans toward:The newest framework every year.
Tools I can debug under pressure: Postgres, Redis, queues, plain Node.I still play with new things (there's 3D on this site), but production gets the parts I understand.
Done
What the market leans toward:Done when the demo works.
Done when it holds up on a busy day: retries, validation, logs and tests.None of that shows in a demo. It decides whether people still trust the product a month later.
Progress
What the market leans toward:A big reveal at the end.
A working build every week, with decisions written down.Most problems live between people, not in the code. Short loops catch them while they're small.
After launch
What the market leans toward:Hand it over and move on.
Stay around after go-live: watch it, fix it, improve it.Launch is when you start learning what people actually need.

Neither column is wrong. Plenty of great teams work the left way, and for a quick prototype it's often the better choice. The right column is simply what I'm good at, and the kind of work I'd like to be hired for.

Work Experience

// the pipeline

  1. Associate Fullstack Developer

    Current

    Mind Roots

    SEP 2025 – PRESENT

    A software services company, which is exactly why I joined: a new kind of product every few months, each one built end to end. So far that's a mobile guessing game with its backend and admin panel, a grocery list and recipe app, a gym trainer booking app with real-time changes, and a deep linking platform with custom domains and payments. Now I'm on Bless Me, a marketplace for booking online sessions with spiritual leaders. On each one I take a requirement from a rough idea to something running in production: the interface, the API, queues, servers, pipelines and tests.

    • Node.js
    • Next.js
    • React
    • PostgreSQL
    • Redis
    • BullMQ
    • CI/CD
    Built hereBless MeMind MatchDeep Links

  2. Fullstack Developer

    Script Space

    APR 2025 – AUG 2025

    Hired to keep about 56 journal websites running on OJS. The bigger problem sat inside the company: customer relations, writing and finalizing teams passed work along through Excel sheets and WhatsApp, and something got lost at every handoff. I built a single CMS for all three teams on shared data, with roles, assignment and approve or reject steps, so work moves from one person to the next with a clear trail. Once it was stable the job became mostly upkeep, so I moved on to keep learning.

    • CMS
    • Workflows
    • Roles & approvals
    • OJS
    Built hereJournal CMS

  3. Fullstack Developer

    Grovyo

    JUL 2024 – MAR 2025

    An early-stage social commerce platform for India, meant to help local workers and home-based women sell handmade goods and grow as creators. I worked across the whole product from day one: a queue system and microservices, a continuous upload service, server tuning so videos play in different qualities, the platform's own ad system for creators, and the first seller page and web-page builder. When funding stopped, the team paused the product. They are good people and we still stay in touch.

    • Node.js
    • Microservices
    • Queues
    • Uploads
    • Video quality
    • Ads
    Built hereAdSpace

Selected work

// scroll sideways →

All work

// now building

Namestead

Building

Free identity subdomains on community-funded domains. Sign in, claim yourname.devportfolio.com and go live in seconds.

Visit NamesteadHow it's built

// follow the build

Build logs will show up here as I write them.

Writing

// notes from the build

  • Two scenes from the 3D explainer: a hoodie stamped 'sold twice' next to a MySQL database, and three buyers each locking a different token in a glass bowl, labelled SKIP LOCKED, take the next free one.
    Article

    How Shopify stopped selling the last hoodie twice

    Shopify moved checkout holds from Redis into plain MySQL to close a gap between two databases, then kept it fast by storing one row per unit and claiming rows with SKIP LOCKED. The bug, the fix, the trick, and four things that only show up under load.

    • System design
    • MySQL
    • Databases
    Read the post : How Shopify stopped selling the last hoodie twice
All writing

How the work goes

// 4 steps, no magic

  1. Discovery

    Functional and non-functional requirements first, then what to build first.

  2. Architecture

    Key entities, APIs and data flow, kept simple enough to grow.

  3. Development

    Short demos, tests from week one, optimized where it counts.

  4. Launch

    Deploy, monitor, fix. I stay on after go-live.