Open for client work · Kharar, India

I build the product your users actually stay in.

Senior full-stack engineer. Nine years shipping healthcare, commerce, and content products with React, Next.js, Laravel, and Node — from the first client call to a live release.

See selected work LinkedIn GitHub

HealthcareClinic portals patients and staff use daily

CommerceOrders, delivery zones, and admin control

MediaLive debates and sports audiences

SaaSTools people finish and download

Selected work,
not a job list.

Each card is a product in the world. Open it. The stack is what I used to get it there.

Healthcare · Live

Rheumera

A clinic platform for rheumatology teams. Patients log symptoms. Staff see who needs a call, a report, or a new order — without hunting through five screens.

I owned business logic, the API, and the architecture that keeps patient workflows stable.

Open rheumera.com →

// clinic queue
patients.filter(needsCare)
.sort(byUrgency)
staff.see({ call, report, order })

Commerce · Live

UdderMilk

Organic milk, ordered by customers and delivered by zone. I built the customer portal on my own and extended the admin and driver tools around it.

Open uddermilk.com →

order → zone → driver
customer picks a slot
admin sees the route

SaaS · Built solo

ResumeMaker

People pick a template, fill a form, and download a PDF resume. I designed and built the whole product — editor, templates, and the PDF engine.

Open resumemaker.in →

template + answers
→ pdf.download()

Sports · Live

Sports Injury Central

Free injury analysis for NFL, NBA, and MLB fans, written with pro doctors. I built the admin and the APIs that feed it.

Open sicscore.com →

league: NFL | NBA | MLB
analysis published
admin stays in control

Media · Live

Sided

Radio audiences argue, in public, on the topic of the day. I worked on the interface and the features that keep a debate readable while it is happening.

Open sided.co →

topic goes live
votes land in real time
the side with the room wins

What you hire.

No twelve-page process. Three things clients feel in the first month.

I sit in the requirement call.

I turn a messy brief into screens, data, and an API contract before a lot of code exists.

One person across the stack.

Laravel or Node on the server. React or Next on the screen. MySQL when the data has to be trusted.

It ships, then it stays up.

Git, reviews, and a deployment path. I stay through the first real users, not just the demo.

How the code looks.

Short samples of the style I bring to a client repo. Copy any of them.

Samples

api/orders.php

A 40-second reel.

Press play. Four scenes from the kind of product work I take on. Drop your own Loom link in the embed when you record one.

A clinic that knows who to call.

Queues, reports, and orders in one place so staff stop guessing.

An order that finds its driver.

Customer, zone, and route — built so the morning delivery actually leaves.

An API your frontend can trust.

Clear inputs, predictable errors, and a response shaped for the screen.

Then we ship it.

You get a product link, not a slide. Email me and we start with the riskiest screen.

Hire me

Tell me the product. I will tell you how it ships.

Jitendra Kumar · Senior software engineer · B.Tech, computer engineering · +91 90410 64990

LinkedIn · GitHub