Building software, creating brands, and solving real‑world problems.
I build scalable web applications, SaaS platforms, management systems, and digital products that combine clean engineering with business thinking. Alongside my engineering journey, I'm building HASHLAY and turning ideas into products that create real impact.
Eighteen and building — not waiting for permission to start.
My engineering journey didn't begin in a classroom — it began with curiosity about how the products I used every day were actually built, and a restlessness to build something of my own instead of just studying how others did it. That curiosity turned into late nights learning to code, and eventually into HASHLAY, a sneaker care brand I founded, designed, and shipped end to end.
Somewhere along the way, being a developer stopped being enough. I started thinking in terms of products — who they're for, what problem they remove, whether they can survive contact with real users and real money. That shift is what pulls me toward founder thinking as much as engineering: writing the code is one part of the job; understanding why it needs to exist is the rest of it.
I'm currently a Computer Science Engineering student, eighteen years old, splitting my time between coursework, client and personal builds, and HASHLAY — treating each as a different rep of the same skill: taking something from an unclear idea to a working, usable thing. I don't have it all figured out, and I don't think that's the point. I'd rather keep building, keep shipping, and keep learning by doing.
I believe software should simplify life, empower businesses, and solve meaningful problems. My long-term vision is to build products that improve everyday experiences through thoughtful design, scalable engineering, and continuous innovation.
Fast, conversion-focused sites that carry a brand's identity, not a template's.
Subscription-driven products built for scale from the first line of code.
Internal tools that turn messy operations into clean, trackable workflows.
Registration, scheduling and coordination software for large-scale events.
Storefronts with real cart, payment and fulfilment logic — not mockups.
Clear, data-dense interfaces built for the people who run the business.
Multi-sided products connecting citizens, admins, and services in one place.
Practical AI features layered into products — support, search, generation.
Interfaces engineered to feel native on any screen, at any size.
A closer look at what I've built — the problem, the thinking, and the product that shipped.
A platform built to take festival organisers from scattered spreadsheets to a single system of record — covering registration, scheduling, and on-ground coordination.
A civic technology platform bringing panchayat services online for rural Karnataka — built with a modern UI and a dedicated admin system underneath.
The storefront for my own sneaker care brand — a premium shopping experience with a product showcase built for speed and clarity.
A performance-focused platform for publishing and searching results at speed, backed by a clean admin dashboard.
Turning brand operations into a reusable software product.
Practical AI-driven tools for real workflows.
Multi-sided platforms connecting people and services.
Extending HASHLAY and future products to native mobile.
Purpose-built systems designed around how your business actually works.
Fast, distinctive sites that represent your brand — not a template.
Tools that bring order to operations, records, and internal workflows.
Clear, data-dense interfaces for the people who run the business day to day.
Interfaces designed for clarity first, decoration second.
Reliable, well-documented APIs that connect your systems together.
Practical AI features layered into real product workflows.
An outside eye on architecture, stack choices, and product direction.
HASHLAY isn't a side project — it's where I practice building a business, not just a website.
Outside of writing code, I spend a lot of my time thinking like a founder: sourcing and shaping products, figuring out how a brand should sound and look, and learning the parts of running a company that nobody teaches in a syllabus — pricing, packaging, customer trust, and the small operational details that decide whether a business actually works.
That entrepreneurial half is what keeps my engineering grounded. I'm not building features for their own sake; I'm building things that need to hold up in front of real customers, real payments, and real feedback. It's a slower, harder way to learn — and the one that's taught me the most.
Have a project in mind, or just want to talk product and engineering? My inbox is open.