Where QA engineer roles are actually advertised

Why the big boards feel dead

If you're a QA engineer scrolling LinkedIn or Indeed and getting nothing back, the boards aren't lying to you about volume — they're lying to you about who's actually reading the applications. Generic boards attract generic volume. A posting for "QA Engineer" or "SDET" on a mass board can pull in hundreds of applicants within days, many of whom aren't testers at all, because the title reads as entry-level to people outside the field. Hiring managers respond to this by either ignoring the inbound and going elsewhere, or outsourcing the first pass to an ATS keyword filter that's hunting for exact strings — Selenium, Cypress, Playwright, Postman, JMeter, k6, TestRail, Xray, ISTQB — and discarding anything that doesn't match closely enough. Your CV can be correct and still get filtered because it says "automated testing frameworks" instead of naming the three tools the advert named.

This matters for where you look, not just how you write. If a company is confident it'll get flooded on a public board, it has less reason to post there in the first place for roles it actually cares about filling quickly — which pushes a meaningful share of QA hiring towards channels with a narrower, more self-selecting audience.

Where roles actually surface

A few channels carry a disproportionate amount of genuine QA hiring:

Company careers pages, direct. Mid-size and large engineering organisations increasingly post to their own site first and only mirror to aggregators later, if at all. If there's a specific company you want, check their careers page directly rather than relying on a board to surface it — some postings never make it onto Indeed or LinkedIn, especially internal transfers dressed up as "open" roles to satisfy HR process.

Ministry of Testing's community job board. This is worth knowing about specifically because it's a testing-only space — the people posting there are hiring testers, not filling a generic "engineer" quota, and the postings tend to be more precise about tooling, domain (fintech, healthcare, gaming), and whether the role is manual, automation-heavy, or a hybrid SDET position.

Automation and tooling vendor ecosystems. Companies building on Cypress, Playwright, BrowserStack, Sauce Labs, or similar sometimes surface roles through vendor community Slack channels, forums, or partner directories, because a candidate who already knows the stack is worth more to them than one sourced blind. This is patchy and vendor-dependent, but worth checking if you specialise in a particular framework.

Regulated-industry and domain-specific channels. QA roles in medical devices, aviation, financial services, or automotive often require domain knowledge — FDA 21 CFR Part 11 validation experience, ISO 13485, ISO 26262, or specific regulatory testing history — that a general board can't screen for. These roles more often go through specialist recruiters or industry-specific job boards (clinical systems, fintech compliance, embedded/automotive) because the pool of qualified people is small enough that broadcasting to a general audience wastes everyone's time.

Conference and community channels. EuroSTAR, TestBash, and similar testing conferences sometimes carry sponsor job boards or informal hiring conversations around the event. This is a small channel, but if you're already ISTQB-certified or active in a testing community, it's low-cost to check what's posted around conference dates.

The role agencies actually play

Recruitment agencies matter more for QA than for some adjacent engineering roles, for a specific reason: automation testing sits in an awkward space between "engineer" and "tester" in a lot of hiring managers' heads, and agencies that specialise in QA/test hiring have built pipelines that route around that confusion. Agencies like those focused on tech and QA specifically (the names vary by region — in the UK you'll see specialist tech recruiters running dedicated QA/SDET desks; in the US, staffing firms with tech divisions do the same) tend to hold a rolling set of roles that never get publicly posted because the client has an exclusive arrangement with them, at least for the first few weeks of the search.

What this means practically: a recruiter you've spoken to once, a year ago, might resurface with a role that never existed on any board, because their client asked them to fill it quietly. This isn't networking advice in the vague sense — it's a mechanical fact about how exclusivity agreements work. Being in two or three specialist recruiters' active files, with an up-to-date sense of what you do (manual, automation, performance, security testing, mobile QA with Appium, API testing with Postman/Rest Assured) is closer to being on a shortlist than to "networking."

The trade-off is that agency-sourced roles often come with less transparency about the client until later in the process, and agencies are paid by the employer, which shapes whose interests they're optimising for. That doesn't make them useless — it means treat what they tell you about the role as a starting point to verify, not a final answer.

Internal movement and adjacent titles

A significant amount of QA hiring doesn't look like hiring at all from the outside. Companies frequently move existing engineers into QA/SDET roles internally, particularly at organisations shifting from manual to automated testing, where an internal developer or support engineer who's shown aptitude with scripting gets moved sideways rather than the company running an external search. Conversely, QA engineers at growing companies often get pulled into DevOps, SRE, or release engineering internally as those functions form — meaning the "QA role" you're trying to break into somewhere might already have been filled from within before it ever reached a board.

This cuts both ways for your search. It means some roles genuinely never appear externally, which isn't something you can fix by searching harder. It also means titles are unreliable signals: "Software Engineer in Test," "SDET," "Quality Engineer," "Test Automation Engineer," and plain "QA Engineer" often describe near-identical jobs at different companies, and a search that only uses one term will miss postings using another. If you're not searching "SDET" alongside "QA engineer," you're missing a real slice of the market — SDET roles frequently ask for more coding ability (data structures, CI/CD pipeline integration, writing test infrastructure rather than just test cases) and pay differently, but plenty of postings use it as a straight synonym.

Timing and seasonality

QA hiring tends to lag development hiring rather than move with it. When a company decides to build a new product or feature set, it usually hires developers first and only opens QA requisitions once there's something to test — meaning QA postings often appear a sprint or two, or a quarter, after the initial engineering hiring wave for a given project. If you track a company's engineering job page and see a burst of backend and frontend postings, a QA posting following a few weeks later is a common pattern, not a coincidence.

Budget cycles matter too. Many companies finalise headcount at the start of a fiscal year, which for a lot of organisations means January, and again around September for those on a different cycle or doing mid-year planning. Hiring commonly slows in the run-up to major holiday periods (late November through December in the UK and US) as approvals stall, then picks up again in the new year. This isn't unique to QA, but it interacts with QA's lag-behind-dev pattern in a specific way: a Q4 slowdown in developer hiring often produces a visible dip in QA postings in Q1, a quarter later than you'd expect just from watching the calendar.

What to do with this

Check company careers pages directly for two or three organisations you actually want, rather than relying only on aggregators. Search Ministry of Testing's job board alongside general boards, and search "SDET" as a separate term from "QA engineer" — they're not always the same search. Get on the active list of a specialist tech/QA recruiter rather than a generalist one, and ask them directly what's exclusive to them right now. If you work in a regulated domain, look for recruiters or boards specific to that industry rather than general tech ones. And if the mechanics above — reading adverts closely enough to catch the ISTQB requirement or the specific automation stack buried in paragraph four, matching your one real work history against each one honestly — are the part that's eating your time rather than teaching you anything, that's the specific problem jobmarket.pro is built to take off your hands: it reads each advert in full, tells you where your profile fits and where it doesn't, and drafts the application from your actual history.