Searches every page and blog post. Press Esc to close.

Volunteers › Career pathways › Product Development › Quality Assurance (QA) and Automated Testing
Career pathway · Quality Assurance (QA) and Automated Testing

Find the defects before customers do. Prove it with every release.

Quality Assurance (QA) and test automation engineers protect the product and the people who rely on it. You plan what to test, automate the checks that matter and give the team the confidence to release often. At an early tech startup your tests run on every change, and you leave with a test suite and results you can show.

Voluntary and fully remote. Up to three hours a day across a 60 Volunteer day term. A course certificate or a few practice test scripts are enough to begin.

Release check · build 482
Unit612 passed in 41 seconds
API148 contract checks passed
End to end36 Playwright journeys passed
Flaky1 test quarantined, ticket raised
AccessNo new accessibility issues
SpeedCheckout p95 under 800ms
Quality gate passedSafe to release
A human capital platform where people advance their careers through real, referenceable outcomes.
70,000+
Volunteers
158+
Countries
225+
Tech startups helped
6+
Years in operation
Why QA at a startup

Practice suites show skill. A live pipeline shows impact.

Hiring managers see many test scripts written against demo shops and sample apps. What stands out is a suite that guards a real product, runs on every change and has caught real defects. A Volunteer Term gives you exactly that.

1

A real product

Test the screens, APIs and data that real customers depend on.

2

Tests that run

Your checks run in the release pipeline on every change, not on your laptop only.

3

Measured results

Defects caught, coverage added and release time saved, in numbers.

The scope of the role

What a QA and automation engineer owns.

Some Volunteers lean towards test strategy and exploratory testing, others towards writing automation code. Most early tech startups need both.

Area 01

Test strategy

Decide what to test, how deeply and at which layer.

Map the risky journeys and features
Balance unit, API and end-to-end tests
Agree the quality gate for each release
Area 02

Exploratory and manual testing

Use the product the way customers do, and find what scripts miss.

Run focused test sessions on new features
Write clear, reproducible defect reports
Check accessibility and different devices
Area 03

Test automation

Turn the checks that matter into code that runs on every change.

Build end-to-end tests with Playwright or Cypress
Add API and contract tests
Run the suite in the release pipeline
Area 04

Quality insight

Show the team where quality stands and where it is slipping.

Track defects, coverage and flaky tests
Add simple performance checks
Report quality trends to the Tech Founder
How the discipline changed

From the last step before release to part of every step.

Testing has moved from a separate phase at the end of a project to a skill built into every stage of delivery. Each shift raised the bar for what a tester is expected to know.

1990 to 1999

Testing as a phase

Large projects ran in long stages. A separate test team received the finished software, followed written test cases by hand and reported defects weeks or months after the code was written.

2000 to 2009

The first automation

Unit testing tools such as JUnit spread, and Selenium arrived in 2004, letting testers drive a real browser with code. Agile teams brought testers into the sprint, and test-driven development asked developers to write the test first.

2010 to 2019

Continuous delivery

Teams began releasing daily rather than quarterly. The test pyramid put most checks at the fast unit and API layers, tests moved into the build pipeline and the SDET role, a tester who writes production-quality code, became common.

2020 to 2024

Modern tooling and shift left

Cypress and then Playwright made browser tests faster and more reliable. Quality moved earlier, into design and code review, and later, into monitoring live systems. Many teams renamed QA as quality engineering.

Today

AI joins the test team

AI assistants now draft test cases, generate automation code and repair broken selectors. At the same time, products that use AI need new kinds of testing, because their answers can vary from one run to the next.

The roles in demand today

Where QA careers are heading now.

Manual-only testing roles are shrinking. These are the profiles tech startups and larger employers are asking for most.

In demand

SDET and automation engineer

Writes and maintains the automated suite in TypeScript, Python or Java, with Playwright, Cypress or Appium, and keeps it fast and stable in the pipeline.

In demand

Quality engineer

Owns quality across the whole delivery process, from testable requirements and code review to release gates and production monitoring.

Fast growing

AI and LLM test specialist

Tests products built on AI models: accuracy, safety, bias and consistency of answers, using evaluation sets rather than single expected results.

In demand

API and contract tester

Checks the services behind every screen, so that teams can change one part of the system without breaking another.

Steady

Performance and reliability tester

Load tests key journeys, sets speed targets and helps the team find bottlenecks before customers feel them.

Growing

Accessibility tester

Makes sure products can be used by everyone, a growing legal requirement in the UK, the EU and beyond.

The next 18 months

Less script writing. More judgement.

AI agents will take on more of the repetitive test writing and upkeep. The value of a QA professional shifts towards deciding what matters, checking what the agents produce and testing the AI inside the product itself. Volunteers who build these skills now will be ready for the roles that follow.

1

Agents write, humans decide

Expect AI agents to generate and repair many routine tests. The human role becomes test strategy, risk judgement and reviewing what the agents produce.

2

Testing AI becomes standard

As more products add AI features, evaluating answers for accuracy, safety and consistency will become a normal part of every release.

3

Quality spreads across the team

Developers will own more of their own tests, while QA specialists coach the team, guard the release gate and watch quality in production.

Your QA portfolio

Leave with a test suite, not a list of courses.

Every Volunteer Term leaves you with evidence a hiring manager can open and check.

An automated suite

Tests you wrote that run in a real release pipeline.

A test strategy

The plan, risks and quality gate you agreed with the team.

Defects you found

Clear reports and the fixes they led to.

Quality numbers

Coverage, flaky tests removed and release time saved.

A Tech Founder reference

A reference from the Tech Founder you collaborated with.

Global connections

Connections with developers, designers and founders across 158+ countries.

Getting started

Start in three steps.

Three simple moves to begin building demonstrable QA and automation experience.

1

Create your profile

Sign up and link any test scripts or certificates you have, even practice projects.

2

Match with a tech startup

Apply to QA and test automation opportunities, up to three at a time.

3

Test from Day 1

Agree the outcome brief, post daily and weekly updates, and deliver from Day 1.

Guard a real product, not a demo shop.

Join a tech startup's product team for a 60 Volunteer day term. Free, fully remote and flexible.