Senior QA Engineer Performance & Scalability

About this role

We're looking for a Senior QA Engineer, Performance & Scalability who doesn't wait to be told what to test. You'll own performance and scalability across our platform, 30+ microservices, event-driven flows, and the legacy dependencies that come with a real production system at scale. This isn't a "run a load test before release" role. This is a role where you make performance a first-class concern from day one, where you define the thresholds that decide pass or fail, and where you hold the bar when something is degrading and nobody yet knows why.

You'll be the performance voice in every room you walk into, design discussions, architecture reviews, incident retrospectives. When latency spikes, you're already halfway through the trace. When a new service is being scoped, performance is already in the delivery plan because you put it there. What you can expect to be doing: Own Performance from Day One - You embed performance thinking into the delivery plan before code is written, not as an afterthought before release.

You make performance testing a natural part of how teams build and ship — not a gate they hit at the end. Define What Good Looks Like - You own the thresholds, metrics, and SLOs that govern pass or fail. You decide what a breach means, you set the budgets (latency, error rate, throughput), and you make those signals objective enough that a pipeline can act on them without a human reading graphs. Test Services in Isolation, at Production Scale - You design and build performance tests for individual services, stubbing downstream and third-party dependencies so each journey is tested on its own merits.

You map load to real production traffic to find where things bend and where they break. Lead Performance in CI - You integrate performance testing into CI/CD so regressions are caught automatically, early, and fast. You own the fail-fast signals and keep them trustworthy. Build Reusable, Scalable Assets - You build performance tests as code, reusable components, templates, and utilities that scale across teams and services.

You handle data seeding and test setup so runs are repeatable and realistic. Diagnose, Don't Just Report - You root-cause regressions across the stack, reading logs and tracing requests through distributed systems to find the source yourself rather than waiting for someone to hand it to you. Reach Out and Drive Outcomes - You engage the right stakeholders, engineering, platform, product - to turn findings into fixes. You don't file a report and walk away; you drive the outcome.