What We do: iQmetrix is a global provider of Interconnected Commerce software solutions for telecom retail. Interconnected Commerce is an AI-native telecom commerce platform that acts as a system of intelligence. It replaces fragmented legacy stacks with a contemporary, modular operating layer, connecting telcos, retailers, and OEMs into one flow across channels and markets. The result is less complexity, lower cost, and the speed to move ahead.

For 26 years,we’vebeen passionate about helping the leading brands in telecom to grow by providing best-in-class software, services, andexpertisethat enables them to adapt and thrive.Our solutions power $17BN in sales annually, handlingnearly 53million invoices and more than 28 million activations, and are used by more than 370,000 telecom retail professionals across almost 1,000 clients. iQmetrix is a privately held software-as-a-service (SaaS) company with employees in Canada, the U.S., India, and Europe. For more information, please visit www.iqmetrix.com.

About the Role We are hiring a Principal Engineer, Architecture. This is a senior individual contributor role for someone who is still happiest with their hands on the keyboard, and who thinks in systems while they build.

iQmetrix runs a large, long-lived platform: a retail management system that stores have depended on for years, a next-generation POS and commerce surface, an extension platform our partners build on, and a wide network of services underneath all of it. Keeping that coherent while it changes underneath us is real engineering work, not a diagramming exercise. It needs someone close enough to the code to see where the seams are pulling apart, and willing to do something about it.

You will work as a peer alongside our existing architects,



sharing responsibility for stewarding technical direction across our solutions rather than dividing the org into territories. Architectural ownership at iQmetrix is distributed: teams own the decisions in their domain, write them down as ADRs, and bring them to our weekly architecture advisory forum for challenge and feedback. This role exists to improve how those decisions get made, recorded, and connected across teams — not to make them on everyone's behalf.

How the Role Works This is a role defined by contribution and influence rather than authority. You will spend your time close to the work: writing code, reviewing designs, pairing with teams on the decisions in front of them, and connecting problems that turn out to be the same problem in three different places.

The expectation is depth. You will go deep with a team or on a problem for a stretch at a time, long enough to be genuinely useful, rather than maintaining a thin presence everywhere at once. Where you focus is a conversation you will have regularly with your lead and with engineering leadership.

You write code that ships. Not only reference implementations and prototypes — production work in real repositories, reviewed like anyone else's. Credibility in this role comes from having built the thing.

You are accountable for architectural quality across the platform, and you support the teams who are accountable for delivering it.





You work up and down the stack. Some of this work is deep in a service or an event pipeline; some of it is a customer's security review or an integration question raised by a delivery team.

What You'll Work On The systems you will spend your time in:

Luna — our next-generation POS: a Flutter application backed by an in-house design system and code generators it is built from.

Luna.API — the .NET event-sourced backend behind it, built on Cosmos DB with bounded contexts for orders, tender, payments, repair, and cash management, and a layered architecture enforced in CI.

Hub — our back-office solution, built in React and TypeScript, where customers run the operational side of their business.

The module platform — independently owned modules, written by our teams and by external ones, uploaded to a registry, assigned by company and location, and executed at runtime inside a module engine against a versioned TypeScript SDK. We have committed to backwards compatibility across major SDK versions for authors we do not control, and the system is now being scaled across more domains and more solutions. If contract design is your thing, this is the deep end.

The established service estate — SSO, Entities, CRM, Catalogs and their peers. Newer than RQ, but with years of accumulated dependencies, their own aging assumptions, and real questions about where each one is headed.

RQ — the retail management system a large part of our customer base still runs their business on. Moving off it well is one of the more consequential architectural problems in front of us: what the target state is for each capability, how the two worlds coexist while customers move,

📌 Sr. Staff Developer, Architecture (Regina)
🏢 iQmetrix
📍 Regina