I like problems where being wrong has consequences.
I am in my final year of Computer Science (AI) at McGill, graduating in May 2027. I joined OR Royalties — a royalty company listed on the TSX and NYSE — as its first in-house developer, with no codebase and no platform to extend, and over one summer took its AI and data systems from an empty repository into production. I stayed on part-time through term, and both systems are now used daily by Corporate Development and Finance.
That job taught me something I did not expect to find interesting: the hard part of applied AI is almost never the model. It is knowing what a correct answer looks like. An extraction pipeline for NI 43-101 technical reports is not difficult because the documents are long — it is difficult because a royalty term that is subtly wrong is more dangerous than one that is obviously missing. So that system has explicit human validation states on every field, and the impairment pipeline for IAS 36 is built to refuse rather than guess.
The same instinct shows up in my own projects. TaxMapCA has no language model anywhere in its decision path, because a tax answer that can hallucinate is worse than no answer. TabScribe runs entirely on-device on Gemini Nano, because research tooling that uploads your reading is unusable for anyone handling anything confidential. The constraint is usually the design.
I also know when to stop. VectralQ was my company — hybrid retrieval, cited answers, into McGill TechAccel within a month. I ran the pilots, read the signals honestly, and shut it down. The retrieval worked and the demand did not, and I would rather have four months of evidence than a year of hope.
Outside of that: I build small tools compulsively, mostly to automate things that have annoyed me more than twice. A few of them have ended up on the Chrome Web Store and the VS Code Marketplace. One of them files a public GitHub issue every time I get distracted, which I maintain was a reasonable response at the time.
Education
Expected May 2027
B.Sc. Computer Science (Artificial Intelligence)
McGill University · Montreal, QC
Experience
Sep 2026 — present
AI and Data DeveloperPart-time
OR Royalties Inc. (TSX/NYSE: OR)
- Retained after the internship to build a versioned database of royalty, stream and offtake terms extracted from NI 43-101 technical reports, with a human validation state on every extracted record, feeding analysis for Corporate Development.
- Maintain and extend the production platform and pipelines built during the internship, which Corporate Development and Finance rely on daily.
May 2026 — Aug 2026
AI and Data DeveloperInternship
OR Royalties Inc. (TSX/NYSE: OR)
- Joined as the company's first in-house developer and took its AI and data systems from an empty repository to production, working directly with Corporate Development and Finance to scope, review and roll out each one.
- Built the firm's first production market-intelligence platform in Python, Next.js and Azure Container Apps, ingesting mining filings and news from six live sources daily and ranking signals by materiality. In daily use by both teams.
- The platform's ranked feed surfaced a material royalty buyback and related M&A signal that the existing manual review had missed, confirmed by Corporate Development.
- Replaced a daily manual PDF-to-print review with a zero-touch overnight pipeline, removing the step from the team's workflow entirely.
- Built an LLM pipeline producing first-pass input for the quarterly IAS 36 impairment process, reviewed by Finance before use, and evaluated commercial market-data vendors to inform the firm's data-sourcing strategy.
Skills
Listed only where there is work on this site to back itLanguages
AI and retrieval
Web and APIs
Data and infrastructure
Domain
Recognition
2026
2nd place — National Bank Challenge
For ARMM, an adaptive market-making strategy built solo in 24 hours.
2025
For RememberThroughMe, from a field of more than 800 participants.
2025
VectralQ was accepted within a month of starting.
Open to Summer 2027 new-grad roles
2027
I graduate in May 2027 and I am looking for new-grad software or AI engineering work, in Montreal, elsewhere in Canada, or the US. I am most useful somewhere the engineering touches a domain with real rules in it — finance, compliance, anything where being wrong has consequences and the correct answer has to be traceable.