I am Lee Humeniuk, and QueueOne is one person on purpose.
I build and rescue the integrations and platforms that have to survive production, from Edmonton, Alberta — on site where that helps, and remote across Canada.
The ten-year version
I started where most integration people start: inside enterprise programs, making systems agree with each other that had no intention of doing so. Salesforce and ERP, MuleSoft and Azure Service Bus, and the reservation systems behind a major Canadian airline, where a 25+ API micro-service architecture carried a 1,000 req/sec SLA. Somewhere in there I led working groups of up to ten engineers inside a programme of more than fifty people.
That work teaches a specific discipline — idempotency, back-pressure, reconciliation — and it turns out to be exactly what smaller companies need and almost never get. So the second half of the decade has been product: a consumer app I co-founded and built that has been live for three years, a local business whose operating platform I built from nothing and still maintain, an investor platform launched with its first cohort, and my own product now in beta.
QueueOne is where those two halves meet. The enterprise rigour, applied at a scale where one senior person is the whole team rather than the coordination overhead on top of one.
Why solo is the offer
A consultancy sells you a pitch team and staffs you a delivery team. I am the same person in both meetings. That has real limits — I am one calendar, and I will tell you when a piece of work needs more people than I am — and one substantial advantage: nothing is lost in the translation between the person who understood the problem and the person who writes the code, because there is no translation.
It is also why the delivery model matters. The context that would normally live in a team's heads lives in the repository instead, in a form that both I and the agents I work with read before touching anything. That is the part worth showing.
What I am actually good at
There is always someone with deeper expertise in any single technology than me, and on a large enough team that person should be making that call. What I do is sit between the technology and the people paying for it, and be genuinely fluent in both — which is rarer than depth, and it is what most projects fail for want of.
In practice that means the questions come before the code. What breaks when this does not work, and who gets the phone call. What the business has actually promised someone. Which of the things you are asking for is load-bearing and which is a preference nobody would miss. I have run my own products, so I have made these calls with my own money on the other side of them, and I flag the ones that will cost you later.
It also means I will disagree with you out loud, early, and then commit to whatever we decide. I have taken an engagement on terms I already suspected would not work rather than have the awkward conversation at the start — it went how you would expect, and I will not do it again. That story is on the process page, because it explains more about how I work than anything I could claim about myself.
Education
MacEwan University — BSc Computer Science, 2010–2015.
Recognition and community
- 500 Global, 1st Canadian Cohort — with a regulated fintech I co-founded
- Collision Conference, Alpha Booth — What's The Deal
- University of Alberta Student DevCon — speaker
- Edmonton Unlimited, Experts on Demand — contracted technical expert
- Canada Learning Code — volunteer
Working in Edmonton, or anywhere in Canada.
If you are local, I will come to you — there is still no substitute for standing in front of the same whiteboard. If you are not, none of this work has needed a shared postcode in years.