I connect what others can't
I build from zero.
Aviation black box operating systems. Enterprise IIoT platforms. Production AI applications. I have done this in aerospace, energy, and consulting, and the thing they all have in common is that none of them existed when I started.
I make the connections.
Between the field and the boardroom. Between the OT system and the cloud. Between what the engineers know and what the executives need to decide. Most technical leaders solve one problem at a time. I solve the three underneath it.
I build for what comes next.
The systems I design run without me. That is not an accident. I build for the people who inherit the work, which means I think about failure modes, edge cases, and the problems that will show up in three years before I write a single line of code.
Right now that means grid modernization - building the OT/IT convergence infrastructure that utilities need to integrate distributed energy resources, modernize SCADA systems, and make ADMS and DERMS work at enterprise scale.
It started in aerospace.
I joined FLYHT Aerospace in 2006 as a firmware engineer and ended up co-inventing a patented system for transmitting aircraft black box data in real time from cockpit to ground. We built it to DO-178B safety-critical standards, and it was eventually adopted into ICAO international aviation regulation. That means it is in the rules that govern how the world flies.
I did not set out to write aviation regulation. I set out to solve a problem that kept showing up differently every time we looked at it. That is usually how the best work starts.
Then came energy.
At Husky Energy I worked as Corporate Portfolio Architect across 18 business divisions, building the data and automation infrastructure that cut bitumen extraction costs from $41 to $26 per barrel. At Suncor I took an IIoT platform from a $10K/month proof of concept to a production system running across 7-8 business units, earning Architecture Review Board approval and building the OT/IT bridge that made enterprise-scale adoption possible.
Energy is a hard industry to work in. The systems are old, the stakes are high, and the data is everywhere except where you need it. I found I was good at seeing where the connections were missing and building the thing that made them work.
That work maps directly to what the grid needs now. SCADA modernization, OT/IT convergence for utilities, AMI and distribution automation, ADMS and DERMS data architecture - these are the same problems I was solving in industrial energy, translated into grid language.
Then came consulting.
At KPMG I led a team of 8 and advised enterprise clients on AI strategy, responsible AI frameworks, and data architecture. I rolled out Microsoft Dynamics 365 for a major client. I built medallion architecture on Microsoft Fabric. I wrote AI use case assessments that helped organizations understand what they were actually getting into before they committed.
The thing I took away from consulting: most organizations do not have a technology problem. They have a translation problem. Someone needs to sit between the technical teams and the business leaders and make both sides feel heard and understood. That has always been my job, whatever the title said.
And through all of it, I built my own things.
ZeyTech Inc. has been running since 2012. I have solar PV installations recognized by the Federation of Canadian Municipalities Green Municipal Fund. I manage a self-run 4-suite rental portfolio at roughly 2% vacancy against a 5-10% industry standard. I built MyCashFlow, a production LLM application that bridges Wealthsimple Tax and Chequing using CRA transaction categorization. I am developing Fi.nD, a data sovereignty platform for personal data management.
I do not build side projects to pad a resume. I build them because I see a problem and I want to know if my solution actually works.
Hardware, software, data, and people, built into systems that work at scale and hold up for years.
Most technical leaders are strong in one direction: deep engineering expertise, or broad business strategy, or people leadership. I work at the intersection of all three, which means I can sit in a room with firmware engineers and executives and make the conversation useful for everyone.
I see patterns across problems that look unrelated on the surface. That is why I keep ending up in roles where nobody has written the job description yet, because the value I bring is connecting things that were not connected before.
And I build for the long term. The systems I design have to run without me. That constraint changes every decision: the architecture, the documentation, the team I build, the way I structure the handoff. I am not interested in solutions that require my continued presence to function.
WHAT I AM LOOKING FOR
I am currently exploring Director of Innovation and senior technology leadership roles in clean energy, industrial AI, and intelligent infrastructure.
If you are building something at the intersection of hardware, software, and data:
You need someone who has done this before, at scale. Let's chat.
Zeynin Juma
zeynin.juma@gmail.com