Jaipur, Rajasthan, India · Open to relocate
Full-Stack Software Engineer
I build things to understand how they really work.
I build web and mobile software end to end, from the screen down to the database and the cloud. I’ve shipped it for clients in healthcare, logistics and commerce. Now I’m building a finance app where the AI can explain the numbers, but never change them.
It started with wanting to know how things work.
02Origin
What made me want to build software?
I wanted to understand how the things I used every day actually worked. Once I started coding, I realised I could take an idea in my head and build it. I liked that loop: try something, watch it fail, figure out how to make it work.
So I started with the fundamentals.
03Journey
Each step changed what I paid attention to.
Computer Science & Engineering · Amity University Rajasthan
I started with fundamentals. Then I wanted to see whether the things I was learning could work outside the classroom.
Fundamentals first — C and C++, data structures and algorithms — then Python, web development and databases as the projects got bigger.
The first time they did, the program was for someone else.
Python programming intern · Remote
My first program with a real person on the other side: you type, it measures, it answers.
A speed typing test in Python and Tkinter that scores speed and accuracy as you type.
Real input made me think about data, and what it says about the people behind it.
Data science & ML intern · Bhilwara
Then data became the problem: models that get evaluated, not just run.
A movie recommender combining collaborative and content-based filtering, in pandas, NumPy and scikit-learn.
Next, the software had to work for real businesses.
04Experience
The internship where the scale changed.
Junior software developer intern · Jaipur
The question changed from “can I make this work?” to “how will this behave in production?”
Same foundations, different businesses
Underneath all of them, the same work kept coming back.
React · TypeScript · Node.js · NestJS · Express · MySQL · AWS · Docker
Two of those applications went deeper than the rest.
05Selected work
Two for clients, one for my degree, one for myself.
01 / 04Logistics · 2026 · Primary developer
Cross-platform logistics software built around real business workflows.
Software has to fit the way a business actually works, not just look right technically.
The next client added prices, stock and three kinds of user.
02 / 04Commerce · 2026 · Primary developer
End-to-end commerce platform spanning customer, staff, and admin workflows.
Correctness and security live behind the UI. Small assumptions became production bugs.
Then, for my degree, health data: where a wrong answer costs more.
03 / 04Healthcare · 2026 · Full-stack developer, team of five
Healthcare and pharmacy platform focused on practical patient workflows.
AI output met real consequences: a misread medicine name must never reach an order unchecked.
In my own project I took that rule further: the AI doesn’t get to change anything.
04 / 04Fintech · 2026 · Solo
Personal finance system with an integrated AI layer.
From features to systems: a ledger that can’t drift, and AI that can explain the numbers but never change them.
Looking back, it’s the questions that changed the most.
06How I changed
The clearest sign of growth isn’t the stack. It’s what I ask before I write code.
01Early
How do I make this work?
Getting a program to run and respond was the whole goal.
Then things started breaking where I couldn’t see them.
02Developing
Why is this breaking?
In production, most bugs weren’t inside a function. They sat between systems.
Fixing bugs one at a time stopped being enough once there were more clients.
03Engineering
What happens when this grows?
More roles, more platforms, more clients. Structure started to matter more than speed.
And then there are the parts I don’t control at all.
04System thinking
What happens when everything around it changes?
Now I design for the parts I don’t control: bad input, missing data, and models that are sometimes wrong.
Here is what that looks like as a decision.
07How I think
Choices I made on real projects, and the trade-off behind each one.
Made on · Wallet
Option A
A mutable balance column
Option BChosen
A double-entry ledger
Not every decision was made up front. Some came after something broke.
08What broke
Things that failed in real deployments, and what was actually wrong.
FixedE-Commerce
Around the bigger projects, I kept smaller experiments going.
09Lab
Smaller experiments from the same repositories: some shipped inside something bigger, some still open.
Reading prescriptions with GeminiSwastha
Read the medicines on a photo of a prescription.
Keeping a sales team in step with TallyABS Infotech
Give a field-sales app the stock, customers and balances the business already keeps in its accounting system.
Scheduled client reportingABS Infotech
Take recurring client reports off people’s hands.
Hybrid movie recommenderAvalon Tribe
Recommend movies a person is likely to enjoy.
Payments from bank SMS, on the deviceWallet
Record a payment from the bank’s message without the message leaving the phone.
Gym management for a chain of branchesWith a teammate
One system for a gym brand with many branches: memberships, invoices with GST, and a ledger per branch.
AI video generation pipelinePersonal experiment
Turn a written script into a short animated video.
On-device categorisationWallet
Suggest a transaction’s category without the data leaving the phone.
Forecasts as rangesWallet
Replace a single forecast number with an honest range.
Two-factor sign-in, desktop and mobileABS Infotech
Protect an internal tool with codes from an authenticator app.
Some of them are what I’m working on now.
10Now
The journey isn’t finished.
11Contact
Looking for the next hard problem.
