Interfaces
React and Next.js front ends built out of components, responsive down to 375px. They should still make sense once the content doubles.
- React.js
- Next.js
- Responsive UI
Full-Stack Developer · Pune, Maharashtra, India
Full-stack developer working in React, Next.js, Node.js and AWS. I care about load time and about layouts that stay sane when the content doubles. I also care about the parts nobody sees, like clean APIs and deploys that behave. Second-year B.Tech student in Artificial Intelligence, looking for a software engineering internship.

React and Next.js front ends built out of components, responsive down to 375px. They should still make sense once the content doubles.
Node.js services and REST endpoints over MongoDB and MySQL. I work out the data shapes before designing the screens, which saves rewriting both later.
Deploying on AWS, plus supervised models for regression and classification. I reach for them where they beat something simpler and skip them where they do not.
Conversion-focused web systems for service businesses
Client work rebuilding service business websites so they convert. Most of them already looked fine. That was the problem.
AI-powered colour grading platform
Frontend for a platform filmmakers use to build and preview colour LUTs. If the preview lags the whole tool feels broken, so most of the work went into keeping it quick.
Data-driven apps and predictive models
Freelance work covering full-stack delivery and applied machine learning. Some of it was the data cleaning nobody volunteers for. Some of it was the model sitting on top.
A component turns up with a width. Drop it into a slot that width fits. Put it in the wrong one and the layout breaks. Three breaks and you are done.
It loads nothing until you press Play, so it costs a passing visitor exactly zero.
A component arrives with a width. Move the highlight with the arrow keys and press space to drop it into a slot that width fits. Wrong slot breaks the layout. Finish a page and the next one gets tighter.
Nothing loads until you press start
I started building for clients before I started my degree, so most of what I know came from shipping things other people relied on. Problem first, then code. I still work that way.
The part I like most sits between the frontend and the infrastructure. How a page gets fast. How an API survives being changed six months later. Mostly how much you can delete before something breaks. I am studying artificial intelligence alongside that, and I use it where it beats a simpler answer.
I am looking for a software engineering internship where I would be writing and reviewing production code with people who have been doing it longer than me.
B.Tech, Artificial Intelligence
GH Raisoni University
Aug 2025 — May 2029
Email is the fastest way to reach me. I read everything that is not automated.