About
LS
Data and backend engineer. I build the system, not the demo.
Not an AI tool.
An engineer.
There is a lot of noise right now. A chatbot wired to a spreadsheet gets called an agent, and a business ends up paying for a demo that breaks the first time the data changes.
I am a software engineer, trained at McGill. My work has been the data layer and the backend: first payments infrastructure, where every record has to reconcile to the cent, then the data platform behind a software product that hundreds of businesses run on every day. That is where a business's real problems live, and it is what I build for.
AI is the newest tool in that kit, and a good one. It only works on top of clean data and sound engineering. So that is what gets built first. The intelligence comes after, and it lasts because the foundation does.
In practice
Data before anything.
Before a single task is automated, the data is reconciled, modelled and trusted. Every result the system gives you traces back to a source.
Built into your stack.
Real integrations with the accounting, CRM and operations tools you already run. No copy-paste, no middleware you don't own.
Yours to keep.
Code, database and infrastructure in your name, documented. If I disappeared tomorrow, it keeps running.
Background
Where the experience comes from.
- MontréalBased in, works anywhere
- B.Eng.Software Engineering, McGill
- FR · ENWorking languages
- Now
LS Engineering
Custom systems for owner-run businesses and firms: operations hubs, document intelligence, cross-system reconciliation, reporting.
- Data Engineer
FLiiP
The data platform behind a software product that hundreds of gyms and studios run their business on: pipelines, reporting, migrations, and the AI tooling built on top of them.
- Back End Developer
ValPay
Payments infrastructure. Backend systems where a wrong number is somebody's money, so every record has to reconcile.
- B.Eng.
McGill University
Computer Software Engineering.