gunraj mehta  ·  toronto

Senior
Software
Engineer.

11 years building systems that handle real money, real data, and real compliance obligations. I go where the hard problems are.

The data you didn't mean to train on
Why DSR workflows break the moment personal data enters a training pipeline, and what to build instead.
privacy · AI
Evals are not tests. That distinction costs teams months.
The gap between "correct" and "acceptable" is where most AI teams lose time they didn't know they were spending.
ai · evals
Build the harness before you need it
The same reason you backtest a trading strategy before putting money behind it applies to LLMs in production.
ai · infra
Privacy Engineering Habits for Backend Teams
Practical habits that make access and deletion flows less painful when regulations eventually show up.
privacy
Container-First Modernization — A Lightweight Playbook
What actually works when you're modernizing a legacy ETL stack without burning the team.
platform
All writing →

I'm a senior software engineer based in Toronto. Over eleven years I've worked at JPMorgan, Scotiabank, AWS, and Dropbox — each time moving toward a harder class of problem.

My background spans financial compliance systems, cloud data infrastructure, and privacy engineering. I don't specialize by domain. I specialize in the kind of work where correctness, security, and scale aren't optional — where the system failing has a cost you can measure in dollars, data breaches, or regulatory action.

I write here when I have something to say that is specific enough to be useful. Most of it comes from building things, breaking things, and watching other people build and break things in high-stakes environments. I'm not a consultant, and this is not a content calendar.

You can reach me at hello@gunraj.dev or find me on LinkedIn.