I build software that survives real operational use.
I'm Aditya. I lead engineering at a renewable energy SaaS company in Pune, where the systems I build carry 3,400+ MW of live plant data, 33+ automated daily reports, and AI agents that read operational chatter across dozens of sites. The scale keeps me honest. If a report fails to arrive by 8 AM, someone's phone rings.
On the side, I take on independent projects for founders and operations leads who need something built once and built to last. Fixed scope, fixed price, delivered on the date I promised.
The non-traditional path
No CS degree. My formal education is a Mechanical Engineering diploma from 2020, and I'm wrapping up a PGDM in IT Management at MIT School of Management right now. Everything I know about code, I taught myself.
It started with games. I wanted to build my own, so I picked up C# and Unity, spent late nights chasing tutorials and breaking things until something moved on screen. Some of that early work still lives at @arcadeaart on Instagram. That obsession with seeing code do something real is what kept me going.
From there I jumped into web. I picked up PHP at my first internship at Climate Connect Digital and shipped it for two and a half years, mostly building an automatic reporting system for wind and solar plants. Got promoted twice. Then got laid off in the 2024 round. Somewhere in the middle I started learning the MERN stack on the side, then went deep on vanilla JavaScript, TypeScript, and the modern React and Node stack.
In June 2024, I joined a renewable energy SaaS company as a Software Engineer and got promoted to Lead Engineer on the back of what I shipped. This is where it clicked. Real stakes. Systems that have to stay live. Reporting automation for 33+ plants that runs every single day. You do not learn this from tutorials. You learn it by being on call when something breaks at 6 AM.
What working with me actually looks like
- Fixed scope, fixed price — Every project starts with a paid scoping sprint. You get a written scope, a fixed quote, and a delivery date. No hourly billing games.
- One senior engineer, not a team — You get me. The person who wrote the code is the person you talk to. No account manager in the middle, no junior developer copy-pasting your requirements.
- WhatsApp for the fast lane — The main channel is WhatsApp. Async, fast, everything in one thread. Weekly video call if the project needs it.
- Ship in weeks, not quarters — Most builds are 2 to 8 weeks. If your project cannot be scoped into a small first release, we should talk about whether you actually need something bigger or something smaller.
- Honest about what I will not do — I do not do pure design work, mobile-native apps, or 6-month enterprise rollouts. If your project is one of those, I will tell you and point you at someone better.
What I'm working on now
The day job is real and I love it. The long game is shipping AI-native products that earn on their own. Pieter Levels is the template. Ship fast, kill faster, keep what works.
Right now I am in the "ship and learn" phase, not the "scale a winner" phase. Here is what that looks like:
- AI agents in production — Shipped an AI ops agent monitoring 35+ sites and an autonomous forecasting agent that runs continuously across a portfolio. Every indie product from here is AI-native by default.
- Social Copilot (MVP) — Social media scheduler with AI video generation. My main indie bet for the year.
- SEO experiments — MSMEVault.in and GoSolarIndex.in started as weekend tests. Built with Claude Code, indexed with Claude AI, and pulling organic traffic now.
- Day job — Leading engineering on forecasting, reporting automation, realtime monitoring, and now AI agents for 3,400+ MW of renewable capacity.
Have a project in mind?
The fastest way to know if we are a fit: message me on WhatsApp with what you are trying to build or fix. I usually reply within a business day, and if it is not something I can help with, I will tell you and try to point you at someone who can.