Skip to content
JobreachGet started

How to cold email for a QA or software testing job

A QA post asks whether you find problems before users do. Lead with proof of exactly that: a bug you found and how you reported it, or a test suite you built, how often it runs, and what it has caught.

Updated

What QA and testing posts ask for

Titles range from manual tester to SDET, and the posts move along the same line, from testing by hand to writing code:

  • Testing basics: test cases and plans, the kinds of testing (functional, regression, smoke) and the life of a bug.
  • A clear bug report: the steps to repeat it, what should have happened, what did, with screenshots or logs.
  • A tracker such as Jira, and sometimes a test management tool such as TestRail or Zephyr.
  • Automation for most roles beyond manual testing: Selenium or Playwright with Java, Python or TypeScript; Cypress for web apps; Appium for mobile.
  • API testing with Postman or REST Assured, and enough SQL to check the data behind a screen.
  • For SDET roles: real programming, a framework you design, and tests that run in CI on every change.
  • Sometimes performance testing with JMeter or k6, or the ISTQB Foundation certificate, which service companies often ask for.

Your proof as a fresher

As a fresher, show that you find problems and write them up well:

  • Bugs you found and reported in real software: an open-source project’s issue tracker or an app you use. Link the issue.
  • An automation framework on GitHub for an open-source app: page objects, data-driven tests, a report, and a CI run on every push.
  • API tests for a public API in Postman or REST Assured, with checks for errors, not only for success.
  • An internship where your tests ran on a real release. Say what they caught.

Test a real product, not only a practice site. A bug in software people use, written up well, is the best sample of your work you can send.

Your proof if you are switching in

Coming from support, operations, a BPO or development? You have been finding problems already. Lead with the ones you caught:

  • From customer support: the issues you reproduced and handed to engineering, and how you described them so they got fixed.
  • From operations or a domain role (banking, insurance, healthcare): how the system should behave, which is half of testing it. Name the domain.
  • From development: the tests you write, and any framework or CI checks you set up for your team.
  • From manual to automation testing: the manual cases you automated, and the time each release saves now.

Domain knowledge counts for a lot in testing. Someone from banking operations writing to a fintech about a QA role should say so in the first lines.

Your proof in two sentences

Sentence one: what you test, with which tools, and how often it runs. Sentence two: what you found or caught, and what changed because of it.

Fresher

I wrote a Playwright and TypeScript test suite for an open-source invoicing app, 120 checks that run on every pull request through GitHub Actions. It caught a rounding error in tax totals on discounted invoices, which I reported with the steps to repeat it, and the maintainers fixed it in the next release.

Switching from manual testing

For two years I tested a bank’s mobile app by hand, and I have since automated our regression pack in Selenium with Java, about 300 cases. It now runs every night, and a full regression that took our team four days takes a few hours.

Both are made-up examples. The numbers in yours must be your own, and ones you can explain in an interview.

An example email

Divya, a QA lead at a health-tech startup, posts for a QA automation engineer, 0 to 2 years, Selenium or Playwright and API testing, with an address for resumes. Aman finished his B.Sc. in Computer Science this year. This is the whole email.

To
divya@carenest.example
Subject
QA Automation Engineer (Playwright, API testing): Aman Verma, B.Sc. 2026

Hi Divya,

I saw your post today for the QA Automation Engineer role at Carenest. I finished my B.Sc. in Computer Science this year, and testing is the work I have chosen: I like finding the case nobody thought of.

I built a Playwright test suite for an open-source clinic booking app, with UI tests and API tests in Postman, running on every pull request. It found a bug where two patients could book the same slot if they confirmed within a second of each other; I reported it with the steps to repeat it, and the maintainers fixed it.

Bookings are at the centre of what Carenest does, which is why your post stood out to me. My resume is attached, and the suite and the bug report are linked on my GitHub below.

Aman Verma
+91 98xxx xxxxx
github.com/amanverma-example

A made-up example: Aman, Divya and Carenest are fictional. Every claim in the email comes from Aman’s own resume.

What makes it work:

  • One real bug, in the kind of feature Carenest depends on, says more than a list of testing types.
  • The tools in the post, Playwright and API testing, are inside the proof.
  • The bug report is linked, so Divya can see how he writes one: the skill she is hiring for.
  • It is short enough to read on a phone between test runs.

The subject line

The role title as the post writes it, the tool or kind of testing it names first, your name and your stage.

  • QA Automation Engineer (Playwright, API testing): Aman Verma, B.Sc. 2026
  • Software Tester (Manual): Priya Shetty, BCA 2026, ISTQB Foundation
  • SDET: Karthik Rao, 3 years in testing, Selenium and Java

Avoid subjects like “Job application” or “Resume”. The person who posted may have several openings, and the role first tells them which one.

Mistakes to avoid

  • “I have strong attention to detail.” Show one bug you found instead.
  • Every testing type you know, listed. The resume has room for them; the email needs one proof.
  • An automation project that only clicks through a practice site’s login page. Test something with real flows and real edge cases.
  • Typos in the email. In a QA application, the reader notices every one.
  • Calling yourself an SDET when you have only recorded tests. Use the title the post uses and your work supports.
  • Testing a live site in ways its owners didn’t allow. Report through the project’s own tracker.

And the ones that hurt in every role: a guessed address, a generic resume, and an email longer than a phone screen. More in how to email a recruiter about a LinkedIn hiring post.

Where QA and testing posts appear

  • LinkedIn posts by QA leads and engineering managers at product startups, especially in fintech, health-tech and e-commerce.
  • Other titles for the same work: software tester, QA analyst, test engineer, automation test engineer, SDET.
  • IT services and testing companies’ careers pages, which hire freshers for testing in batches.
  • Company job boards on Greenhouse, Lever and Ashby, under engineering or quality.

A LinkedIn post search to start from (search Posts, Date posted Past 24 hours):

QA and testing posts for freshers

(QA OR "test engineer" OR SDET) ("send your" OR "share your") fresher NOT Lahore

4 of 5 ORs, ANDs and NOTs

If posts from Karachi crowd the results too, add NOT Karachi (five operators). Interns can search ("QA intern" OR "software testing intern") instead of the titles, without fresher. LinkedIn finds nothing at all once a search has more than five ORs, ANDs and NOTs: see how to find hiring posts on LinkedIn. If there is no reply in about a week, follow up once.

Guides for other roles

All of them, with what to lead with for each: cold email by role.