Cover letter example · field
QA Engineer Cover Letter Example
Testing is hard to show on paper, because the best result is a problem that never happened. A QA letter therefore needs measures that stand in for the missing bugs: defects that escaped to production, the time a regression pass takes, how often the team can release. This example uses all three, and it shows a tester who is involved before the code is written, not only after.
The example letter
The situation: Marta Kowalczyk has six years of testing experience and works on a payments app at a company in Kraków. After hearing an engineer from a mobile banking software company speak at a local meetup, she is applying for its QA engineer role.
The writer, recipient and organisations in this letter are invented for illustration.
Marta Kowalczyk
marta.kowalczyk@example.com | +1 555 0196 | Kraków, Poland
12 October 2026
Ewa Lewandowska Head of Quality Oakhaven Digital
Dear Ms Lewandowska,
I am applying for the QA Engineer (Mobile and API) role on your careers page. I have tested web and mobile software for six years, the last three at Northgate Payments on a payments app used by about 200,000 people. I heard Tomasz Wrona describe your contract testing set-up at the Kraków testers' meetup in September, which prompted me to look at your vacancies.
My work is split roughly evenly between exploratory testing and automation. I write web tests in Playwright with TypeScript, API tests in Postman and Appium tests for the Android and iOS apps, all running in GitHub Actions on every pull request. I take part in refinement so that acceptance criteria are testable before work starts, write bug reports a developer can reproduce first time, and own the release checklist and a regression suite of about 620 cases in TestRail. I hold the ISTQB Foundation certificate.
When I joined, a full regression before each fortnightly release took three testers two days by hand, and bugs still reached production: customers reported 14 in my first six months. I automated the 180 most stable, highest-risk checks, cut the manual pass to half a day of targeted exploratory sessions and added API-level tests for payment states the interface could not reach. Customer-reported defects fell to 3 in the latest six months, and we now release every week.
Tomasz described testers pairing with developers on consumer-driven contract tests between the app and each credit union's core banking API, and testers deciding whether a release is safe. At Northgate, integration failures with partner banks are our most expensive bugs, and we still catch them late. I want to learn how you catch them early, and in return I can bring experience of testing payments on poor mobile connections, which your job description lists as a gap.
I live in Kraków, can work from your office three days a week as the advert asks, and have a one-month notice period. I would be glad to do a practical test or pair on a testing session. Thank you for considering my application.
Yours sincerely,
Marta Kowalczyk
Open this letter in the builder Start an empty letter
Paragraph by paragraph
- Opening
- Gives the exact role title, six years of experience and the product she tests, with its size ("used by about 200,000 people"). It ends by saying she heard Tomasz Wrona describe the company's contract testing at a meetup in September. That is not a referral and she does not present it as one, but it tells the reader this application has a specific cause.
- Experience
- States the balance of her work, "split roughly evenly between exploratory testing and automation", which a QA hiring manager will want to know early. Tools are named with their use: Playwright for web, Postman for APIs, Appium for the apps, running "on every pull request". Taking part in refinement "so that acceptance criteria are testable before work starts" shows she prevents defects as well as finding them, and the 620-case suite gives her responsibility a size.
- Achievement
- Starts with an honest baseline: three testers, two days, and still 14 customer-reported bugs in six months. It then explains a decision, automating "the 180 most stable, highest-risk checks" instead of everything, which shows judgement about what is worth automating. The outcomes are the measures a team cares about: customer-reported defects down to 3 in six months, and releases moved from fortnightly to weekly.
- Why this employer
- Builds on the meetup talk in detail: testers pairing with developers on consumer-driven contract tests, and testers deciding whether a release is safe. She admits a weakness at her current company ("we still catch them late") and presents the move as wanting to learn how it is done well. She then offers something back: experience of testing payments on poor mobile connections, which the job description lists as a gap.
- Closing
- Confirms the three office days the advert asks for and her notice period, then offers "a practical test or pair on a testing session". For a tester, volunteering to be observed at work is a confident way to finish, and it suits a company she has just described as pairing testers with developers.
How to adapt it
- State your split between scripted, exploratory and automated testing honestly, and name each tool with what you test with it.
- Use quality measures your team already tracks: escaped defects, regression time, flaky test rate, release frequency, time to reproduce a bug. Give a before and after figure with the period it covers.
- Include one decision about what not to test or not to automate, and why. It shows a grasp of risk that a list of tools cannot.
- Mention where you work in the process: refinement, test planning, release sign-off, production monitoring. A QA letter is stronger when it shows involvement before code is written.
- Find out how the company tests (talks, posts, the job description) and connect one of its practices to a problem you have met.
Mistakes to avoid
- Listing every testing tool and certificate with no account of what was tested, at what scale or with what effect on releases.
- Quoting the number of test cases written or bugs raised as the achievement. Volume says little; what reached customers and how fast the team can release say more.
- Presenting automation as the goal and manual testing as something to escape, when most teams need both and want to hear how you choose between them.
- Describing QA as the last gate that developers hand work to, which suggests you wait for builds instead of shaping requirements and testability.
Questions and answers
Can I apply for QA engineer roles with only manual testing experience?
Yes, though read each advert closely, because expectations differ. Show the depth of your exploratory testing, bug reporting and domain knowledge, and say what automation you are learning and have tried, even on a small scale. Be exact about your level, since overstated coding skill shows at the first practical exercise.
Should I mention ISTQB or other testing certificates in the letter?
One short sentence is enough, as in this example. A certificate shows shared vocabulary and commitment, and some employers ask for it by name. It supports your evidence but does not replace a description of real products you have tested.
What numbers can a tester use if the team does not track defects formally?
Count what you can reconstruct honestly: production incidents in the issue tracker over a period, the hours a regression pass takes, how many checks run on each build, or how many releases went out in a quarter. If a figure is an estimate, say so.
Is it acceptable to mention weaknesses in my current team's testing?
In moderation, yes. Naming a problem you want to learn to solve, as this letter does with integration failures found late, shows self-awareness. Keep it factual, avoid blaming colleagues and do not reveal confidential details about incidents or customers.