$90 - $175 per hour
Role Title: QA Engineer Role Type: Contractor Location: Remote micro1 is engaging QA Engineers to contribute expertise in software quality evaluation for a customer's high-volume project. In this role, you'll apply your…
Engineering & IT · Remote
Remote QA Engineer jobs
QA engineers make sure software works before users find out it does not. The role blends manual exploratory testing with automated test suites and close collaboration with developers.
7,833
Open roles today
$26–$70/hr
Typical pay range
$95k
Median, full-time
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open qa engineer roles
5 shown of 7,833 · sorted by freshness
giving individuals, communities, and countries the tools to take control of their financial destinies. About the Role: The Senior QA Engineer is responsible for ensuring the quality and reliability of the company's softw…
ABOUT YOU We are looking for a Senior QA Engineer with strong Web3 experience to join our engineering team. You are meticulous, technically sharp, and deeply curious about decentralized technologies. You understand the n…
Cuban. About the Role We’re looking for a versatile Quality Engineer to help deliver reliable, high-quality experiences across a... ...testing coverage. Who you are: ~4-5 years of experience as a QA Engineer ~ Experience…
across versions, verify fixes, and make sure critical flows work before they reach users. About the Role : We’re looking for a QA Engineer to own manual and automated testing for pod releases. This is primarily a hands-o…
02
What qa engineers earn remotely
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $26–$38 | $55k–$80k |
| Mid level | $38–$53 | $80k–$110k |
| Senior | $50–$70 | $105k–$145k |
National ranges — remote pay usually tracks the employer's base market.
03
What employers ask for
The skills these listings keep naming
Test planning and case designAutomation (Selenium, Playwright)API testing (Postman)A scripting language (Python, JS)Bug reporting and triageSQL for data verificationCI integration of test suitesExploratory testingAttention to detail
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
How would you test a login form?
Go beyond happy path: invalid inputs, security cases, lockouts, accessibility, and different devices. Structure your answer into categories so it sounds systematic.
What do you automate, and what do you test manually?
Automate the repeatable and regression-prone; explore manually where human judgment finds new bugs. Showing you know automation has a maintenance cost is the senior move.
Walk me through a great bug report you have written.
Reproduction steps, expected versus actual, environment, evidence, and severity. Emphasize that a good report saves a developer an hour.
A developer says your bug is not a bug. What do you do?
Show that you argue from the user's perspective and the spec, escalate with data if needed, and keep the relationship collaborative.
How do you decide what to test when time is short before a release?
Risk-based prioritization: critical paths, recent changes, and areas with bug history. Naming the tradeoff explicitly is what they want to hear.
How do you keep an automated test suite from becoming flaky?
Talk about stable selectors, proper waits, isolated test data, and quarantining flaky tests instead of ignoring red builds.
05
Resume tips that move the needle
For qa engineers specifically — generic advice costs you here
01
Quantify your impact in defects: escape rate reduced, critical bugs caught pre-release, regression time cut.
02
Name your automation stack and the size of suites you built or maintained, such as number of tests or coverage of critical flows.
03
Show progression from manual to automation if that is your path — it is the expected trajectory and worth making explicit.
04
Mention the domains you tested (payments, healthcare, mobile) since domain risk knowledge transfers.
05
Include CI/CD integration work; a suite that runs on every pull request is worth more than one run by hand.
06
Where this role goes
Typical progression
01
QA Analyst
02
QA Engineer
03
Senior QA Engineer
04
QA Lead
05
Head of Quality
Ten quiet minutes a day
Applying for qa engineer jobs remotely?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.