Hi! I'm Kabir a Software Engineer|

A short walk through how I ended up in CS, what's kept me here, and where the throughline shows up across the work I've done. Less a résumé, more the shape of the answer.

Why CS

I picked CS because it was the only discipline where the gap between "I had an idea" and "the idea exists in the world" could collapse to an afternoon. Most engineering disciplines have a tax on iteration — materials, tooling, regulatory friction. Software has almost none. You can build, break, rebuild, and share before lunch.

What kept me in CS is different from what got me into it. The early appeal was speed of iteration; the lasting appeal is leverage. A well-designed system multiplies the effort of everyone using it. The same instinct that makes me want to refactor a 5000-line RL framework into something a junior researcher can extend in an afternoon is the instinct that makes me care about good infrastructure, clear abstractions, and writing code that other people can actually read.

Biology got added as a minor because I wanted at least one domain where my intuitions weren't pre-formed. Combinatorics & Optimization got added because the math underneath ML kept showing up in places I didn't expect, and I'd rather understand it once than fake it forever.

The throughline across every job I've taken — Pelmorex, Geotab, Eoxys, NRC — has been the same question: where is the leverage point in this system, and what's the smallest change that moves the most weight? An 84x BigQuery speedup at Pelmorex was one answer. A modular refactor of an RL framework at NRC was another. Same instinct, different surface area.

I'm still figuring out the long-term version of this, and I expect the answer will shift a few more times before it settles. For now, the question itself is enough.