Skip to content

About

I’m Rajat - a software engineer, immigrant, and builder based in Vancouver.

I moved from India to Canada in 2015. Since then, I’ve built a life and career here, with six years of experience across co-op and full-time software engineering roles.

The technical side matters to me, but it is not the whole story. What keeps me interested in software is its ability to reduce friction and make an everyday problem easier for someone else.

01 · Story

My path

  1. A new beginning

    I moved from India to Canada and began building a life in a new country. It was the start of a personal chapter that would also shape my education and career.

  2. Learning and first opportunities

    I studied computer science through Fraser International College and Simon Fraser University. Co-op roles gave me an early opportunity to turn classroom ideas into software used by real people.

  3. Growing as an engineer

    Full-time engineering work brought larger backend, cloud, reliability, and automation problems. Those years clarified what I value: useful systems, deliberate trade-offs, and software other people can understand.

  4. Building around real problems

    I’m applying those lessons to products of my own and continuing to explore dependable backend systems, developer tooling, and reliable AI infrastructure.

02 · Motivation

Why I build

I don’t usually start with a technology. I start by noticing friction: information scattered across different places, repetitive work that consumes time, important details that are easy to lose, or a process that asks too much of the person trying to use it.

The software I want to build should quietly reduce that burden. It should help people feel more organized, informed, or in control without replacing one frustrating process with another.

HearthBringing scattered home records, maintenance, and responsibilities into one understandable place.MyBursarHelping people make sense of everyday finances while retaining control of sensitive information.

03 · Philosophy

How I build software

Empathy and engineering are connected. Understanding the person experiencing a problem helps define what the system actually needs. From there, I prefer the simplest design that solves the problem properly - and I expect that design to account for failures, privacy, maintenance, and change.

  • Begin with the personUnderstand who is struggling, what is getting in their way, and what a useful outcome actually looks like.
  • Make the simple path dependableSimple should still mean correct, reliable, private, and maintainable. It should never mean careless.
  • Let complexity earn its placeAdd another service, datastore, queue, or abstraction only when it solves a demonstrated problem.
  • Leave it understandableGood software should make sense to the next person who needs to operate, change, or depend on it.

04 · Beyond work

Outside software

Outside work, I enjoy creative and practical hobbies that help me slow down, notice details, and keep learning in a different way.

Photography
I am most drawn to nature and landscape photography - quiet places, changing light, and scenes that make me stop for a moment.
Anime
Some of my favourite anime are Naruto: Shippuden, Bleach, and Demon Slayer, though the full list is far too long to fit here.
DIY and woodworking
I am learning to take on small home projects and woodworking - a hands-on way to understand how things are built and improve them myself.
“Good software does not need to feel impressive. It should feel useful, understandable, and leave someone with one less problem to think about.”