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 modern, modular operating layer, connecting telcos, retailers, and OEMs into one flow across channels and markets. 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.
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. 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.



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. 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. You are accountable for architectural quality across the platform, and you support the teams who are accountable for delivering it. 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. Luna — our next-generation POS: a Flutter application backed by an in-house design system and code generators it is built from. 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. 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, and how data migrates without loss. It deserves the same design rigour as anything net new. Architecture, distributed Help teams make and document valuable architectural decisions in their own domains — pairing on the design, testing the tradeoffs, and improving the ADR rather than authoring all of them yourself. Be a strong contributor at our weekly architecture advisory forum, where leads bring their ADRs for feedback. We have a substantial body of ADRs spread across many repositories; Identify the cross-cutting concerns early — the ones that sit between teams and are therefore easy to leave unowned: contract and versioning conventions, identity and permissions, tenancy and data isolation, observability, and migration sequencing. Bring options and evidence to genuinely contentious decisions and help the group converge. Where the answer is not yet knowable, run the spike and write it up — our spikes are first‑class documents that the ADRs they inform are built on. Raise the standard of our design reviews: better questions, clearer writing, and less ceremony. Hands-on engineering Embed with a team or a project for a period at

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