Senior Quality Engineer
Relay
- Location
- Toronto, ON
- Employment
- Full Time
- Work model
- Remote
- Level
- Senior
- Salary
- $157.5k/yr
- Posted
- 2h ago
Skills
About this role
Relay is a digital banking platform that gives self-made business owners the tools and know-how to be great with money—bringing clarity, confidence, and control to every dollar earned, so they can turn hard work into lasting success. We do this by replacing financial guesswork with real visibility, transforming cash flow from a constant source of stress into a clear signal owners can use to run stronger, more resilient businesses. You'll join Core Banking , the team building the resilient banking infrastructure that Relay's customers and internal teams depend on — ACH and wire transfers, local and international, and everything that keeps money moving securely and predictably. Core and Risk Engineering are tied at the hip, and you'll be embedded across both. The team's north star is simple: scalable, reliable, on time, under budget — measured in escaped defects, test flakiness and duration, incident count, and uptime. Your mission is to scale quality operations and build the tooling, frameworks and CI pipelines for a distributed system that make it easy to scale quality and increase development velocity across every engineering team at Relay. This is not a role where you write UI tests against someone else's system. You will have the same leverage as a developer.
What You'll Be Doing
Own the quality roadmap for Risk Engineering and build the quality engineering frameworks for Core Banking systems, including ACH and domestic and international wire transfers. Build and improve our CI infrastructure , including the migration to ministack — testing lambdas and microservices in CI with local implementations of Wiremock, Localstack and PSQL. You'll be measured on the same numbers the team is: escaped defects, test flakiness and duration, incident count, uptime. Drive shift-left across the teams you're embedded in — attending sprint ceremonies and getting developers writing tests as part of their deliverables, not as a handoff to QA. Find and remove the bottlenecks in quality operations , diagnosing pain points across Core Banking and Risk and championing the solutions. Build tools that improve developer experience , with minimal dependency on third parties. Mentor junior quality engineers and contribute to the direction and larger-scale initiatives of the Quality Engineering team. Tell the quality story with data — gathering defect and quality data from across our systems and presenting it to engineering leadership and executives. Roughly 75% of your week is hands-on building. The other 25% is influence: ceremonies, mentorship, evangelism, and getting teams to adopt what you've built.
Who You Are
You have built quality engineering systems from the ground up, hands on — frameworks, test suites and CI systems, not just tests written against someone else's harness. You have tested distributed systems , not only UIs. Services, lambdas, microservices, real-time applications — you understand what makes them hard to test and you've done it in CI. You understand and care deeply about system architecture - you have an in depth understanding of how a distributed system is architected - how systems communicate, how scaleability and resilience is built into a system and how to design tests for these complex systems instead of treating them like a black box. You can influence and persuade development teams to adopt quality practices. You've changed how a team works, not just what you shipped. You debug from first principles , using code, logs and traces to get to genuine root cause. You can gather quality and defect data from multiple sources and present it to a wide audience , including executives, and make the numbers mean something. You are AI-fluent in practice — using AI tools daily, comfortable with how agents work and with the systems underneath them, and able to critique AI output rather than accept it blindly. You thrive in agile teams that move quickly and you're comfortable with ambiguity and abstract requirements.