Quality Engineer
Contract: 12 months to start, with the expectation of extending into a multi-year engagement
Work Arrangement: Hybrid, 3 days per week in the office
Location: South Burnaby’s Glenlyon industrial/business district
About the Role
We're looking for an engineer who treats quality as an engineering discipline, not simply a testing activity.
A quality strategy isn't measured by how many tests exist, but by the confidence, speed, and actionable feedback they deliver.
You'll join a value-stream team building scalable, automated verification across the software development lifecycle. This is a hands-on engineering role where you'll write code, modernize testing frameworks, build reusable developer tooling, and make quality signals first-class artifacts in our CI/CD pipelines.
Much of the work involves designing verification mechanisms for distributed systems, event-driven architectures, and Salesforce. You'll build component and integration testing that runs against real applications in isolated, containerized environments, validating API contracts, Kafka producers and consumers, and critical service behavior before it reaches production.
We want someone who does more than write tests. You improve the systems, tooling, and practices that allow teams to ship with confidence.
What You'll Do
Design automated verification frameworks for APIs, microservices, distributed systems, event-driven architectures, and Salesforce systems.
Build infrastructure to run component tests against real applications in isolated containers with stubbed dependencies.
Validate API contracts, service behavior, and asynchronous messaging workflows, including Kafka producers and consumers.
Develop reusable testing utilities and patterns that are easy to adopt and hard to misuse.
Integrate verification into PR, merge, release, and deployment pipelines. We deploy every 15 minutes and to production as soon as we can.
Determine where each quality signal belongs in the delivery lifecycle, balancing confidence, speed, maintainability, and cost.
Modernize testing platforms and reduce maintenance overhead across repositories.
Treat CI/CD pipelines as engineering products, with a focus on performance, reliability, resource efficiency, and developer experience.
Strengthen verification strategies across unit, component, contract, integration, end-to-end, performance, security, mutation, resilience, and accessibility testing.
Turn production incidents, operational data, and recurring defects into preventive verification capabilities.
Partner with engineers to improve testability, observability, reliability, and maintainability.
Use AI-assisted development tools responsibly, without compromising rigor or accountability.
Required Skills
Strong software engineering fundamentals and proven hands-on coding experience.
Professional experience with TypeScript and Node.js, along with automated testing frameworks such as Vitest and Playwright or similar browser automation tools. BDD experience preferred.
Experience building verification solutions for APIs, microservices, and distributed systems.
Experience designing reusable testing frameworks, utilities, and developer tooling.
Experience with Docker, Docker Compose, and Kubernetes-based applications.
Experience with event-driven architectures and messaging platforms such as Kafka.
Experience integrating verification and quality gates into CI/CD pipelines.
Solid understanding of:
Test pyramid and testing quadrants
Shift-left and risk-based testing
Test isolation and determinism
Appropriate use of test doubles
Fast feedback loops
Nice to Have
Experience with trunk-based development, daily deployments, true CI with merges every 15 minutes, and true CD where you don't control when an environment receives a build.
Experience with Grafana k6 or other performance engineering tools.
Consumer-driven contract testing, such as Pact.
Experience with mutation testing tools and techniques.
Experience improving CI/CD performance and resource efficiency.
Experience using observability data to investigate reliability or performance issues.
Experience working across multiple programming languages.
Experience building internal developer platforms or engineering enablement tooling.
Experience collaborating with SRE, platform, or security teams.
You'll Thrive Here If You
Improve quality through automation and tooling, rather than relying on process documents or manual testing.
Enjoy building reusable capabilities that help engineers write better tests with less effort.
Treat flaky tests as engineering problems and failures as signals worth acting on.
Believe developer experience is part of quality engineering.
Know which test type fits which risk and push verification earlier and closer to the code.
Move comfortably between application code, test frameworks, CI/CD automation, tooling, and operational troubleshooting.
See correctness, reliability, security, performance, accessibility, maintainability, and operability as dimensions of quality.
What Success Looks Like
Verification is a first-class delivery artifact: automated, repeatable, deterministic, and machine-executable.
Engineers receive fast, reliable, meaningful feedback within their existing workflow.
Testing happens earlier and closer to the code, providing confidence without creating unnecessary maintenance overhead.
Quality practices are consistently adopted across repositories, with standards codified and enforced through tooling.
Pipelines surface the right signals at the right stages, allowing teams to deploy confidently.
Incidents and recurring defects result in stronger preventive controls.
Quality improvements make delivery safer without slowing the team down.
