Their independence from external stakeholders, enabling it to chart its course, maintain a long-term perspective and build an enduring, sustainable business that currently employs ~600 team members globally. At this scale, engineering is not simply a function supporting the business. The quality of the underlying systems, architectural decisions and engineering practices directly shapes the economics and capabilities of the exchange. Engineers work on globally distributed, latency-sensitive systems where seemingly modest technical decisions can become meaningful when multiplied across hundreds of billions of transactions. This long-term, somewhat contrarian, thinking puts them in a position to offer stability and career longevity evidenced by robust benefits that include RRSP matching. They are not looking for another senior engineer because a team has a project that needs to get delivered. Instead, there is an prospect to add a small number of principal-level engineers capable of elevating the practice of software engineering itself (including engineers who are already operating at a very high level). You may become the technical leader behind a significant product or platform initiative, taking responsibility for architecture and technical direction across a challenge that’s scope extends well beyond a single team. You may operate more like an internal coach/consultant, moving across teams to help senior engineers reason through difficult systems problems, challenge assumptions, improve designs and establish better ways of working. There are several engineering organizations where someone of this calibre could create meaningful leverage, and the eventual fit will depend on your technical strengths, interests and where those capabilities can have the greatest impact.



Rather than moving every candidate through an identical funnel, conversations are likely to be shaped around the individual and will involve senior engineering leadership (including VP and C-level stakeholders) early and often. Technical leadership: Establish technical direction for complex, high-impact engineering problems whose scope may span multiple teams, systems or product areas Design, critique and evolve large-scale distributed systems while making thoughtful trade-offs across performance, reliability, maintainability, complexity and long-term organizational needs Engineering leverage: Improve the effectiveness of other senior engineers through design reviews, technical consultation, pairing, mentorship and direct involvement in especially difficult problems Where appropriate, take technical ownership of significant product or platform initiatives from ambiguous problem through architecture, execution and durable production operation Engineering practice: Identify opportunities to improve architecture, coding practices, technical decision-making, system design and the mechanisms through which engineering knowledge spreads across the organization Balance architectural ambition with the realities of operating mature systems at enormous scale (aka recognizing when the sophisticated answer is appropriate and when the boring answer is better) Hands-on engineering:



Remain sufficiently close to code and production systems to ground architectural decisions in reality and contribute directly when doing so provides the greatest leverage Champion technical initiatives effectively across teams of IC engineers, engineering leaders, product stakeholders and executives without relying on reporting authority You have operated successfully at Principal, Senior Principal or an equivalent level of technical scope (regardless of what your company happened to call the role) You have deep experience designing and operating complex backend or distributed systems where performance, reliability, throughput and architectural quality genuinely matter You have led consequential technical work whose success required coordinating and influencing engineers across multiple teams You have a strong grasp of systems fundamentals and can reason deeply about concurrency, distributed state, networking, data movement, performance, failure modes and the trade-offs inherent in large-scale software You have a history of making other engineers better (including people who do not need basic mentorship and may themselves be technical leaders) You can move between strategic architecture and implementation detail without treating either as beneath or above you You have strong technical judgment and know that influence at this level comes as much from asking good questions, building trust and changing minds as it does from being technically correct You can communicate complicated technical ideas clearly to audiences ranging from deeply specialized engineers to executives You care about elegant engineering, but your lived experience has made you a pragmatist with a deep appreciation that production software ultimately exists within

📌 PRINCIPAL, TECHNOLOGY ENGINEERING (Canada)
🏢 HRB
📍 Canada