THE HUMAN BEHIND THE CODE

Engineer.
With a point
of view.

Balbir Singh

I spent four years in India writing algorithms, traversing binary trees, and making sure my logic was solid. It was rigorous, but I kept hitting the same wall: I wanted things to look cool. So, I packed exactly two bags and moved to the UK to get my MSc. Living in a city of dreams, where even the architecture feels like a design grid, changed how I think. It taught me that heavy logic should still feel effortless to use.

I started as a frontend developer because I like pretty things. I started learning backend because a pretty button is completely useless if it doesn't save your data. Now? I kind of love writing the database schemas just as much as tweaking a CSS animation. I am not a master full-stack developer yet, but I am learning it out of sheer stubbornness, simply because I want people to actually use my products.

Let's be honest about modern workflows: I build with , and I use them a lot. They write code fast; my job is making sure it's the right code. I decide what gets built, notice when the output is wrong, test it until it breaks, and debug it until I understand why. Every engineering story on this site started with something breaking and ended with me understanding why, because if I can't explain a piece of my own project, it isn't finished. When I step away from the keyboard, I try to because I thought it would make me look cool. It is ridiculously hard (and I deeply apologise to my neighbours for the noises I make). I also maintain a .

Download Resume (PDF) File to be supplied