How to write a QA CV that gets remote interviews
By the QAAnywhere team · Published November 8, 2026
What a remote QA CV has to do
A CV for a remote role is read quickly, often first by screening software and then by a recruiter or hiring manager who spends a minute or two on it. Nobody can meet you in the office or see your work. The CV has to answer three questions fast:
- Can this person legally work where the role is based?
- Do they have the specific skills this listing asks for?
- Is there evidence they did real work with those skills, and that it mattered?
Everything below serves those three questions.
Start with the basics recruiters filter on
At the top, under your name:
- Your location and work authorisation, plainly: "Based in Lisbon, Portugal. EU citizen." Most remote QA roles are limited to particular countries (on QAAnywhere at the start of November, 184 of 261 roles named a single country), so recruiters check this first. If you will need visa sponsorship, do not hide it; it saves both sides time.
- Time zone and overlap, if it helps: "CET; comfortable with 4 hours of overlap with US Eastern."
- Contact details and links: email, LinkedIn, and a GitHub or portfolio link if you have public test projects.
Leave out photos, date of birth and marital status unless the country's norms require them.
A summary written for the role
Three or four lines that say what you are and what you are good at, in the listing's terms:
QA automation engineer with 6 years in fintech. Builds and maintains Playwright (TypeScript) and REST Assured suites running in GitHub Actions. Strong in API and exploratory testing; led the test strategy for a payments platform handling 2 million transactions a month.
Avoid generic adjectives ("passionate", "detail-oriented") that every CV uses. Specifics do the work.
Skills: grouped, honest, matching the listing
Group skills so they can be scanned:
- Automation: Playwright (TypeScript), Selenium (Java), REST Assured, pytest
- CI/CD and tooling: GitHub Actions, Jenkins, Docker, Git
- Testing: API testing, exploratory testing, test strategy, performance testing (k6)
- Other: SQL, Jira, TestRail, Agile/Scrum
Order matters. The tools named most in remote QA listings at the time of writing were Playwright, Selenium, Postman, REST Assured and Cypress; if you have them, put them first. Only list tools you could discuss in an interview. A long list of tools you touched once invites questions you cannot answer.
Use the listing's own words where they are true for you. If a listing says "Playwright with TypeScript", write exactly that. Screening software and busy recruiters both match on terms.
Experience: outcomes, not duties
The biggest difference between weak and strong QA CVs is here. Weak CVs list duties: "Wrote test cases. Executed regression testing. Logged bugs in Jira." Every tester does that.
Strong CVs show results with numbers you can explain:
- "Automated 450 regression checks with Playwright; release testing time from 3 days to 4 hours."
- "Introduced API contract checks that caught 12 breaking changes before release in the first quarter."
- "Reduced flaky test rate from 9% to under 1% by fixing test data isolation."
- "Found an authorisation bug that let users view other customers' invoices; fixed before launch."
A useful formula: what you did, with which tool, and what changed because of it. Three to five bullet points per role is enough; older roles can have one or two.
Show remote-ready habits
Remote employers look for evidence you work well without someone beside you. Among QA listings with a full description on QAAnywhere, 39 of 99 mentioned communication and 56 mentioned documentation. Show these in your bullets:
- "Wrote the team's test strategy and onboarding guide for new testers."
- "Ran release sign-off for a team across three time zones using written checklists."
- "Recorded short bug walkthroughs that cut back-and-forth with developers."
If you have worked remotely before, say so in the role line: "Senior QA Engineer, Acme (fully remote)".
Projects and certifications
If you are changing careers or moving into automation, a public project is often the most persuasive part of your CV: a repository with a small, well-organised test suite running in CI, and a README explaining your approach. Link it near the top.
Certifications such as ISTQB can help in some markets and with some employers, but they came up rarely in remote listings (2 of 99 described roles). Treat them as a supporting detail, not the headline.
Length and format
- One page for up to about five years of experience, two pages at most for senior roles.
- A simple, single-column layout. Fancy templates with columns, icons and skill bars often break screening software and annoy readers.
- Send a PDF unless the employer asks otherwise, named sensibly:
Firstname-Lastname-QA-Engineer.pdf. - Check spelling carefully. A typo on a tester's CV is noticed.
Tailor every application
Keep a master CV with everything, then spend ten minutes per application:
- Read the listing and mark the five skills it stresses most.
- Make sure each one appears in your summary or skills, and in at least one experience bullet, if it is true.
- Move the most relevant role or project higher.
- Remove anything that distracts from this role.
Ten tailored applications usually produce more interviews than fifty identical ones.
A short cover note
Many remote applications have a box for a message. Use three or four sentences: the role and why this company; the one or two experiences most relevant to the listing, with a result; and a link to your public test project. Mention your location and time zone if the listing is particular about them. A specific note shows you read the listing, which many applicants do not.
Common mistakes
- Hiding the location, so the recruiter has to guess whether you can be hired.
- Listing every tool ever used, with no evidence of depth.
- Describing duties instead of results.
- A summary that could describe any tester.
- No links, so there is nothing to verify.
The roles below are the newest on the board. Each listing shows where you can work from, so check that before tailoring your CV for it.