rEveryone says they care about quality. Then the deadline gets close and quality becomes "we'll test it after launch." Not on this program.

5D Web Studio is drafting a QA Lead onto the roster for a multi-year, public-sector digital program in Canada, where the compliance bar is real: accessibility audits, security reviews, multilingual releases, and stakeholders who notice everything.

How the roster works: apply, get screened hard, make the bench. When the program calls, you get called up. A call-up is a guaranteed, contiguous full-time block with a start date and a release date, paid premium, because finding the bug before the public does is worth premium.

The seat, and why it starts early.

You join four weeks before the test window opens, and those four weeks are the whole point. While the developers are still mid-sprint, you build the automated regression suite, wire it into the pipeline, and agree the exit criteria with the client in writing. So when feature complete lands, regression already runs on every build, and "holding the line under pressure" is not heroics, it is a gate reading evidence against criteria everyone signed before the pressure existed.

That is how quality survives a deadline: structurally, not emotionally.

What this seat owns

- The test strategy across five dimensions: functional, regression, multilingual, performance, and accessibility, agreed before testing starts, not improvised during it.
- An automated regression suite built by you, from zero, running in CI on every build, so the repetitive passes are run by machines and your hours go to judgment.
- Multilingual test passes across four language versions, including a non-Latin script, because a site can be linguistically perfect and still break in the interface.
- Performance and low-bandwidth testing against throttled connection profiles that match what users actually have, not office broadband. Testing on a fast connection proves nothing here.
- Accessibility as core QA: automated checks and keyboard passes inside your regression,



so the formal audit finds as little as possible. The audit itself, and the penetration test, are independent firms; your job is making their reports boring.
- The defect register, severity definitions and triage, run so cleanly that priority disputes are settled by the definitions, not by whoever argues loudest.
- User acceptance facilitation: you prepare the scripts, train the client's testers, and support them through two weeks of UAT.

You do not test on their behalf, because acceptance that was done for the client is not acceptance.

- The evidence pack that the go or no-go review reads, and launch verification during the cutover itself.

The bar, in years

- 6+ years in QA and test engineering, at least 3 leading testing on a delivery with a fixed date.
- 3+ years building test automation yourself: Playwright or Cypress suites you architected from zero and wired into CI, not cases added to someone else's harness. Be ready to talk through the structure of the last suite you built and what you deliberately chose not to automate.
- Multilingual testing you have actually done: you know what breaks when a language is added, from truncated UI to fallback logic to the sort order nobody thought about. Non-Latin scripts count double.
- Performance testing under constrained bandwidth: throttled profiles, page-weight budgets, and results a developer could act on.
- Accessibility testing beyond a scanner: you know roughly what automated tools catch and what only a keyboard and a screen reader will find, and you have logged both kinds of findings against WCAG success criteria.
- Defect discipline with a paper trail:



severity definitions and exit criteria a client actually agreed to, and a defect register that survived an argument.
- UAT you have facilitated for a real client, with scripts you wrote.
- Bug reports with numbered reproduction steps, expected versus actual, and evidence attached. If developers have ever thanked you for one, mention it.
- CMS experience is a strong plus, Drupal especially: editorial workflow bugs, cache invalidation surprises and configuration drift are their own genre.

Who makes this roster

- Builds test strategy, not just test cases. Automation-first, spreadsheet-last.
- Treats accessibility testing as core QA, not a checkbox.
- Writes bug reports so transparent that developers thank you. Occasionally.
- Holds the line under deadline pressure. Low ego, high standards.

Straight talk about the structure. On-demand contract work, not a salaried seat. Remote-first, with at least four hours of daily overlap with North American Eastern Time, because triage, UAT support and the launch window happen in the client's day. A call-up is one contiguous full-time block of roughly ten weeks, late January to the end of March 2027, subject to award, and you are released at go-live on a date named up front.

The shape of the work is honest: four weeks building automation, three weeks of full-cycle testing, two weeks of UAT, then launch. There is no lull in it, and the go or no-go review reads your evidence pack on a date that does not move. One more thing, because the compliance bar is real.

Claims are checked to a procurement standard: references who take the call, work that verifies, and an honest answer about how you use AI tools, because on this program AI use is governed, not winged.

To be considered: send your resume and one short paragraph about the best bug you ever caught, and what it would have cost if you hadn't, to [email protected], subject line "CALL ME UP - QA Lead."

No cover letters. The paragraph tells us everything.

📌 QA Lead / Test Engineer (India)
🏢 5D Web Studio | Powered by 5AIVE
📍 India