Dipen Modi
I spent several years running operations at Amazon, where I learned that most problems are systems problems. Now I'm doing a master's in computer science at Northeastern and building the systems myself.
Now
I'm building a banking API with an append-only transaction ledger — FastAPI, PostgreSQL, deployed and monitored. It started as a coursework assignment that stored passwords in plain text. Getting it from there to production taught me more than the assignment did.
I'm also writing here every week about whatever I got wrong that week. So far that includes a test suite that passed thirty-two checks while missing a crash on the first line of user input.
I'm looking for a software engineering co-op starting January 2027.
Background
At Amazon Canada I led operations teams through peak season, where the constraint is never the plan — it's what happens when the plan meets reality at four in the morning. I ran shifts, built schedules, and spent a lot of time working out why a process that looked fine on paper kept breaking in the same place.
[Replace with specifics: team size, scale, one thing you changed and what it did.]
I moved into software because I got tired of describing the fix and wanted to build it. The operations instinct turned out to transfer better than I expected — most of what I do now is still about finding where a system quietly fails and making that failure loud.
Otherwise
Quantitative finance, systems programming in C, and the specific satisfaction of a test that fails for the right reason. I'm based in the Greater Toronto Area.