Psychology and behavioural science
Why people do what they do. This is the part of product design that never fits into a framework.
About
Platforms · Messaging · AI
Nine years of production software, three of them on AI
Hi, I'm Kashish. I build software for a living and think about people for a hobby, which turns out to be the same job.
I'm an engineer with nine years in enterprise software - messaging platforms, multi-tenant SaaS, and the interfaces people run them from. Most of that time has gone into one thing: taking systems that are genuinely complicated and making them feel simple from the outside.
I started in frontend, which is where I picked up the habit of caring how something feels to use and not only whether it works. The work widened from there into platform architecture and real-time messaging infrastructure, and for the last three years into AI - mostly the evaluation, cost and failure handling that decide whether a language model is a product or a demo.
I hold an MBA in Operations and Data Science. It confirmed something I already suspected: the engineers who do well next are the ones who understand the product and the people as well as the stack.
Away from the screen, I hail from the mountains - which is probably why I still measure a good day by how quiet it was.
I love to travel, and the trips I remember are the ones where the plan ran out somewhere around day two. I run on espresso and a playlist that never ends. I play more games than I admit to in standups. I read psychology to understand why people do what they do, and I watch crime and thrillers mostly to call the twist before the reveal, which I usually get right.
Working in tech came with the obvious occupational hazard: I am a gadget freak. I read spec sheets for things I have no intention of buying, which is the day job pointed at objects instead of systems.
None of that is a personality section. It is where most of my better product instincts have actually come from.
Practice
Concept through execution
I build digital products end to end, from the first sketch to the thing running in production. The background behind that: multi-tenant platforms, conversational messaging across RCS, WhatsApp and SMS, Angular architecture at scale, and LLM systems that have to hold up once real customers are talking to them.
The part I enjoy most is working with designers, product managers and other engineers on software that stays reliable once real people are using it. Anything else is a prototype wearing a suit.
Beyond engineering
Four standing interests
Technology is a big part of my identity, not the whole of it. None of the below is a hobby I do to look interesting. It feeds straight back into how I design things, mostly by reminding me that software is for people who are tired, busy and half distracted.
Mindfulness
Attention is the scarcest thing I have, at work and everywhere else. So I practise it on purpose.
Travel
New places reset my defaults. A few of my better product instincts showed up nowhere near a desk.
Personal growth
The same learning habit I apply to the stack, turned on myself. It is slower and less comfortable.
Also
Podcast
I host Positively Yours
32 episodes about healing, change and the parts of growth nobody posts about. It is the least technical thing I do and probably the most honest. On a break since February 2026, but the whole archive is here.
Listen to the podcast →Build with intention. Keep learning. Leave every product better than you found it.
How I try to work