Senior Staff Developer, Architecture in Regina

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 modern, 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’ve been passionate about helping the leading brands in telecom to grow by providing best-in-class software, services, and expertise that enables them to adapt and thrive. Our solutions power $17BN in sales annually, handling nearly 53 million 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.

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.
• 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.

What You'll Be Doing: Architecture, distributed. Help teams make and document good 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. Your role there is to make the proposal sharper and the discussion better, not to hand down a verdict. Keep our decision record connected. Identify the cross-cutting concerns early — the ones that sit between teams and are therefore easy to leave unowned. Bring options and evidence to genuinely contentious decisions and help the group converge. 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 a time, carrying real work and leaving the codebase and the team better than you found them. Build the reference implementation for a new architectural pattern, then stay with it. Take on the difficult diagnostic work: performance, data integrity, cross-service failures, and the issues that span several teams without clearly belonging to any of them. Do the prototyping and research that de-risks a direction before we commit a roadmap to it, and write up what you learned either way.

Working across teams. Partner with engineering leaders, product, and other senior engineers on sequencing. Make sure the constraints that only surface in real customer environments reach the teams designing for them. Help other engineers develop as architectural thinkers.

What We're Looking For: The profile we have in mind is a senior or staff-level engineer with an architectural bent — someone who has consistently operated well beyond their own codebase without stepping away from it. Substantial experience building and running production software, including time at a senior, staff, or principal level of responsibility. A track record of owning work end to end, from design through shipped and operated production code. Real depth in more than one layer of the stack. Comfort with systems that are modelled rather than merely built. Experience with versioned contracts between parties who ship on their own schedule. Familiarity with distributed data and its tradeoffs. Experience with a large, long-lived system carrying legacy that cannot simply be removed. Strong technical writing. Practical fluency with AI-assisted engineering.

What We Offer: Begin your journey with a competitive starting salary! Enjoy peace of mind with a comprehensive benefits package for you and your entire family. Embrace work-life harmony with a flexible hybrid working environment, generous vacation and trusted sick leave program. Invest in your future with our RRSP/401K/PF and Share Ownership plans. We care about your family, offering maternity, adoption, and paternity leave salary top ups as well as ten “New Baby Days” for all parents welcoming a new child into their life. Enjoy a “Cultural Day” off annually to celebrate a day of religious or cultural significance. Give back with up to 6 days of paid time off annually for volunteering or personal learning. We believe in the value of taking time to refresh, re-energize, and reflect on your career journey. Employees are granted a seven-week sabbatical after every seven years of employment!

If you’re interested in a career with iQmetrix, please submit your resume and cover letter. We are an equal opportunity employer. We do not discriminate based on race, faith, colour, cultural background, gender, sexual orientation, age, marital status, or disability status. We thank all applicants for their interest, however, only those selected for an interview will be contacted.