Gecko - Embedded IoT firmware shipped on 150,000 systems a year
The challenge
Embedded firmware drives physical equipment in tens of thousands of homes: a silent regression can't be fixed by redeploying a web app. The constraint isn't the feature - it's reliability at industrial scale, year after year.
What I built
At Gecko Alliance (Quebec) I worked on the firmware and connectivity of embedded control systems produced at scale - on the order of 150,000 systems deployed per year. Industrial C / FreeRTOS context: tight memory budgets, real-time constraints, over-the-air updates of a hardware fleet you can't 'patch in prod' with one click. The engineering discipline this demands is exactly what I now apply to critical .NET systems.
If your product has a hardware or embedded component - IoT, sensors, edge, connected equipment - I've already operated at industrial scale, where a regression means a field recall, not a hotfix. That rigor carries over to the backend and the cloud.
Key engineering points
Embedded C / FreeRTOS firmware on control systems produced at ~150,000 units/year.
Real-time constraints: reaction within a guaranteed window, counted memory and CPU.
Over-the-air (OTA) updates of a massive hardware fleet - the procedure must be infallible.
Cloud connectivity: large-scale telemetry without saturating the network or the backend.
Similar technical risk?
I can help scope the risk, architecture and first deliverable.
A 30-minute first call is enough to see whether I am the right profile for the problem.
A similar challenge?
A system like this one to build? Let's talk.
I take on critical technical work — from scoping to production, no debt or lock-in once it's handed over. Fastest way to see if it fits: a 30-minute call.
I reply within 24h — often sooner.