I enjoy taking on problems that don't have obvious solutions, exploring them deeply, and designing systems that are reliable enough for real world use. I build production systems where accuracy matters, transforming unreliable model outputs into software people trust.
Hi!! I'm Harsh. I'm an engineer and I enjoy solving problems, building software, and understanding how everything works under the hood.
What keeps me interested isn't a particular language, framework, or industry. It's the shape of a problem. The ones where the answer isn't obvious, where the constraints aren't well understood, and where solving it requires more thinking than coding.
I'm naturally curious. If I don't understand how something works, I'll keep pulling it apart until I do. Whether it's software, a business, or a new technology, I enjoy getting past the surface until I understand what actually makes it work.
I start from first principles. Before looking at how others solved a problem, I want to understand what's actually true about it: the real constraints, the assumptions everyone accepts, and what nobody has questioned. A surprising amount of software complexity comes from solving problems that never existed.
So my optimisation isn't "how do I build something impressive here." It's "can I solve this in a simpler way." A simpler system has fewer places to break, fewer things to explain, and it's still working two years later when the person who built it has moved on. Complexity is easy to add and very expensive to remove.
The rest of my thinking is about how pieces fit together. Not just whether something works today, but what happens when one part quietly stops doing its job, and how long it takes anyone to notice.
I learn by building. Reading teaches me the concepts. Building teaches me the trade offs.
Simple beats clever. If I can remove a moving part, I will. The best systems are usually the ones that do less.
I think about failure early. Validation, monitoring, and safety nets aren't the exciting parts, but they're what make production systems dependable.
I like owning the whole system, from the experience users interact with to the infrastructure that quietly keeps everything running. Building both keeps technical decisions grounded in how the product is actually used.
I don't think AI is a finished product. I think it's infrastructure, closer to electricity or the internet, and everything will be built on top of it for the next few decades.
That changes what's worth building. The interesting work isn't the demo that impresses people for a week. It's the layer underneath: the infrastructure that makes AI reliable, predictable, and trustworthy enough for real products and businesses to depend on. That foundation is still being built, and that's where I want to spend my time.
Outside of work, I love watching cinema, playing football, and experimenting in the kitchen. I also spend a fair bit of time reading, exploring new ideas, and learning about things that have nothing to do with my day job.
A client-side quotation builder. Create, manage and export professional PDF quotes with a client book, multi-currency support and status tracking, all stored locally in the browser.
Fastest way to reach me is the form belowon the right, or just drop a line at hpsingh5612@gmail.com. I read every message and reply within a couple of days.
