From curious experiments
to building with AI.
I'm Priyanshu Urmaliya — an AI engineer and full-stack developer who enjoys turning messy ideas into working products. I care about the details: clean APIs, useful interfaces, and systems that actually ship.
I believe the best builders learn in public, ship early, and refine until the product feels obvious to use.
Location
Indore, India
Status
Open to opportunities
Focus
AI · RAG · Full-stack
How it started
It started in school with a simple question: how does software actually work? I was fascinated by how a few lines of code could become something people use every day. That curiosity pushed me toward engineering — and eventually toward AI.
College became a mix of coursework, hackathons, and late-night builds. I failed plenty along the way — exams, competitions, and projects that never made it past version one. But each attempt taught me something about scope, teamwork, and staying calm when things break.
Hackathons changed the pace. Smart India Hackathon pushed me to ship under pressure with a team, communicate clearly, and demo something real — not just a slide deck. That experience shaped how I build today: fast iterations, tight feedback loops, and focus on what users actually need.
Now I spend most of my time at the intersection of AI and product — RAG systems, LLM workflows, and full-stack apps that connect models to real interfaces. I'm still figuring things out, but I'm doing it by building.
How I work
Stay curious
AI moves fast. I learn by building, reading, and talking to people a few steps ahead of me.
Ship, then refine
A working prototype beats a perfect plan. I prefer real feedback over endless polishing.
Sweat the details
Loading states, edge cases, and clear UX matter as much as the model or API behind them.
Build for humans
Technology is a means to an end. If it doesn't solve a real problem, it doesn't count.
Beyond the code
Outside of work, you'll find me writing on Medium, exploring new tools, or chasing the next hackathon idea. I like learning in public and sharing what actually worked — and what didn't.
I'm drawn to builders who combine technical depth with clarity. That's the kind of engineer I want to become.