Principal SW Engineer

Our client is a pioneer in their industry and currently operate a planetary scale exchange platform with thousands of nodes that handles 500+ billion daily auctions and is trending towards 1 trillion daily auctions in the next ~4 years. Each auction is completed within milliseconds, across globally distributed infrastructure designed for reliability and efficiency. They have been quietly bootstrapping and growing in line with revenue for over 2 decades and have not raised money from venture capitalists. 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.

Our client has been stubbornly racking and stacking infrastructure around the world for the duration of their existence, a habit that allows for them to price themselves at the cost of electricity while their competitors are mired in rising cloud infrastructure costs. 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.

This is also not a particularly conventional job search.

The organization already has a meaningful population of highly experienced engineers. They are not looking for another senior engineer because a team has a project that needs to get delivered. Instead, there is an opportunity 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).

What that looks like could take a few forms!

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.

In reality, both role archetypes will carry elements of each but index more heavily on one way of working than the other.

For that reason, we are deliberately not prescribing the exact team or organizational home before meeting the person. 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.

The same applies to the interview process. 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.

Key responsibilities

Technical leadership: Establish technical direction for complex, high-impact engineering problems whose scope may span multiple teams, systems or product areas

Architecture: 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

Major initiatives: Where appropriate, take technical ownership of significant product or platform initiatives from ambiguous problem through architecture, execution and durable production operation

Cross-team problem solving: Move comfortably across organizational boundaries, identify problems that do not fit neatly within one team and bring the right engineers together to solve them

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

Pragmatic decision-making: 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

Organizational influence: Champion technical initiatives effectively across teams of IC engineers, engineering leaders, product stakeholders and executives without relying on reporting authority

Your know-how

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 enough breadth to enter unfamiliar systems, understand the important constraints quickly and contribute meaningfully without needing to be the pre-existing domain expert on every component

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 are comfortable entering situations where the problem, ownership boundaries and correct solution have not yet been neatly defined

You care about elegant engineering, but your lived experience has made you a pragmatist with a deep appreciation that production software ultimately exists within business, organizational and operational constraints

It’s a bonus if

You have worked on systems processing enormous transaction or event volumes under strict latency requirements

You have experience in adtech, exchanges, marketplaces, financial infrastructure or another domain where distributed systems directly mediate real-time economic activity

You have worked in environments combining privately operated infrastructure with cloud technologies

You have held roles where you functioned as a technical advisor or consultant across multiple engineering organizations rather than belonging exclusively to one product team

You have successfully influenced major architectural changes in mature systems where rewriting everything from scratch was neither realistic nor desirable