Senior Software Engineer · Vision33 · Since 2015
Eleven years designing reliable software on one mission-critical platform — ERP integration, financial automation, and cloud architecture. I design for correctness first, and I build systems that earn trust and keep it.
Mohammad Hassan What I’ve come to believe
When code moves money, a duplicate invoice isn’t a bug ticket — it’s a customer-facing financial error. So I design for the failure case first: idempotent runs, replay-safe state, systems that fail without lying. Reliability isn’t bolted on at the end. It’s the shape of the thing from the start.
Evidence · Automated Billing & Tax Engine →Good architecture disappears. I build integration platforms that hum in the background — partners and staff get exactly what they need, the system of record stays protected, and no one files a ticket. Point-to-point sprawl is easy to start and impossible to maintain; a real platform grows in straight lines, not tangles.
Evidence · ERP Integration Platform →The strongest systems don’t ask to be trusted — they let you verify. In a privacy-preserving prescription protocol, a pharmacy can confirm a prescription is legitimate without ever learning who wrote it. That’s the aim everywhere: make the guarantee checkable, so trust never has to rest on faith.
Evidence · Secure NFC e-Prescription →Before I believe a result, I try to break it. Modeling osteoarthritis biomarkers, the easy answer — what correlates — is usually the wrong one; the real question is what drives the outcome, cross-validated until it survives scrutiny. I bring that same skepticism to production. A number I can’t defend is a number I don’t ship.
Evidence · Metabolomic Biomarkers →The evidence
Enterprise finance, integration architecture, applied cryptography, and causal inference. Each written up honestly — context, constraints, and the trade-offs I chose.
The ERP stays the single system of record. Everything else is a projection of it — protected, and available 24/7.
This code moves money. A duplicate invoice isn't a bug ticket — it's a customer-facing financial error.
A pharmacy can fully trust the prescription without ever learning who wrote it.
The question was never what correlates with the disease — but what plausibly drives it.
The eleven-year arc
Most engineers change jobs to grow. I grew by staying — taking one business-critical platform and modernizing it continuously while it ran the company. The stack changed completely. So did my role.
Vision33 · 2015 – Present · Remote, Montreal QC
Apr 2025 – Present
Jul 2016 – Mar 2025
Aug 2015 – Jun 2016
Foundations
2013 – 2016
M.Sc. Computer Science
Memorial University of Newfoundland
Pass with Distinction
2004 – 2009
B.Sc. Computer Science & Engineering
Shahjalal University of Science and Technology
University Merit Scholarship
Certifications
MCSD: App Builder · 2016 Exam 70-487: Azure & Web Services · 2015 MCSD: Web Applications · 2015 Exam 70-486: ASP.NET MVC · 2015 MCPS: Microsoft Certified Professional · 2015 Exam 70-480: HTML5, JavaScript & CSS3 · 2015 
Cisco CCNA Exploration · 2008 In my own words
I’m Mohammad — an engineer who spent a decade making one system more trustworthy, and still gets a quiet thrill the moment a hard problem finally goes calm.
I care about correctness, clarity, and building software that outlasts the hype cycle — and I keep learning whatever tools that takes. I’m most useful where the stakes are real, the systems are tangled, and someone needs to make them dependable.
Open to senior and staff engineering roles, and to interesting problems in reliable, large-scale software.
Based in Montreal, QC · Available remotely
