Skip to content
SUSHIL

About

Main bio

I'm Sushil a fullstack developer in India who likes turning messy problems into things that just work .

I picked tech early and never really looked back. After 12th (non-medical) I joined the BCA at Guru Nanak Dev University College in Pathankot, and while I was learning computer science properly I was also the person friends and local businesses called when they needed a website or a quick fix. That taught me the part no syllabus covers: people don't care how it's built, they care that it works when they need it.

Alongside the degree I joined Harkirat Singh's 0 to 100 cohort, which pushed me to understand the whole product instead of just one layer of it. Since then I've worked in three very different places: a young social commerce startup, a publishing company where three teams ran on spreadsheets and chat threads, and now a services company where a new kind of product lands every few months. The products keep changing. What I enjoy stays the same: working out what someone really needs, then building every layer of it until it holds up on a busy day.

Right now I'm at Mind Roots as an associate fullstack developer, building Bless Me, a marketplace for booking online sessions with spiritual leaders. Before that I spent April to August 2025 at Script Space, and July 2024 to March 2025 at Grovyo.

Portrait of Sushil Kumar smiling in a yellow bomber jacket on a beige background
it's me

After work I build things for myself (a few of them are below) and write down what broke and why. Usually late at night, usually after a deploy.

How I work

Ship first, polish after

A working version in front of real people teaches more than another week of planning. I get the core running early, then improve it with what people actually do, keeping the design open enough to grow into. Most products don't need to be perfect on day one. They need to be usable, and ready for what comes next.

working beats perfect.

No handoffs, no lost context

Most problems in software live between people, not inside the code. A requirement gets reworded, a decision goes unwritten, and three weeks later something doesn't fit. I like to see the whole path, from what someone needs to what runs on the server, so the reason behind every decision stays attached to it.

one head, whole stack.

Boring tech, on purpose

Good systems are usually plain ones. I choose tools by how they behave when things go wrong, and I'd rather understand a few of them deeply than sample many. A new idea earns its place by solving a problem that is really there, not by being new.

boring ships.

The unglamorous stuff builds trust

Retries, queues, validation, tests and a deploy pipeline you never have to think about don't show up in a demo. They decide whether a product holds up on a busy day. I build them in from the start, because adding them after the first outage costs far more.

trust lives in the details.

Now

Building

Namestead: free identity subdomains on community-funded domains. The backend and dashboard are in; the launch is next.

At work

Bless Me at Mind Roots: the booking flows for online sessions with spiritual leaders.

Learning

Running servers beyond one box, for Homeport. I haven't run Kubernetes in production yet, so I'm taking it slowly.

// updated OCT 4, 2026

Work & study

Timeline


  1. Mind Roots

    Associate Fullstack Developer

    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
    SEP 2025 – PRESENT
  2. Script Space

    Fullstack Developer

    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
    APR 2025 – AUG 2025
  3. Grovyo

    Fullstack Developer

    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
    JUL 2024 – MAR 2025
  4. Harkirat Singh's 0 to 100 cohort

    Full-stack development cohortCohort

    Alongside my degree I enrolled in Harkirat Singh's full-stack development course, the one that takes you from zero to a hundred.

    • Full-stack
    • Web development
    DURING MY DEGREE
  5. Guru Nanak Dev University College, Pathankot

    Bachelor of Computer ApplicationsEducation

    After 12th (non-medical) I joined the BCA because tech was what I wanted from the start. Those years went into learning computer science properly and building my skills, with small jobs for local businesses and friends along the way.

    • Computer Science
    • BCA
    GRADUATED 2024