Job title : QA Engineer location: Phoenix, AZ Required EX- AMEX profiles MUST SKILLS : # Playwright # Karate # UI- Manual Required Skills ~5+ years of experience in Software Quality Assurance. ~ Strong...
QA Engineer jobs in Phoenix, AZ
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.
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.
Open qa engineer roles
12 shown of 394 · sorted by freshness
Senior QA Automation Engineer (Karate & Cucumber) Location: Phoenix, AZ (Onsite) Employment Type: W2 Job Overview We are looking for a Senior QA Automation Engineer specializing in API and BDD test automation using Karat…
Test Automation Engineer - Remote Bright Vision Technologies is a technology consulting and software development company delivering... ..., test reliability, and time-to-feedback. ~ Mentor junior QA engineers and uphold…
Job Description Job Description Overview The QA/QC Engineer will be responsible for developing, implementing, and managing quality assurance and quality control programs for the construction of Chemical Distribution Syst…
QA Engineer Manual & Functional Testing Focused (NOT A REMTOTE POSITION) About the Role Invessio is building the infrastructure for modern investment management. Quality here isn't a final gate. It's baked in from day on…
Rinvio is hiring a Mission Critical QA/QC Engineer / Manager for quality management for data center and mission-critical MEP construction in the Phoenix, AZ market. Pay: $190,000-$230,000/year, based on experience Locati…
Job Description Job Description Job Title: Salesforce QA Automation Engineer Job ID: 12972-(Hybrid/Local) Client: AZDES - DTS Closing: 7/29/2026 @ 4:00 PM Need Local AZ residents only. Hybrid. First 2-3 days on site then…
Job Description Job Description Salesforce QA Automation Engineer – Hybrid (Mostly Remote) – Phoenix, AZ – $71/hr W2 Location : Phoenix, AZ (Hybrid: first 2-3 days onsite, then about once a month) Type: 6-Month Contract…
Candidates ~ Employers ~ Pricing ~ About Us ~ Register Free ~ Login ~ Post a Job Info Back to Free Job Search DevOps & QA Engineer Triumph Tech, LLC ~ Phoenix, Arizona, United States ~1d ago Job Description Job Descripti…
Job Description Job Description QA Engineer - Manual & Automation (50/50) Release Management / QA Experience: 6+ Years Job Type: Contractual Work Type: Onsite, Phoenix, AZ Release management and quality assurance roles f…
Job Description Job Description Benefits: Onsite Competitive salary Opportunity for advancement Automation Test Engineer (Selenium + Java + GCP) Location: Phoenix, AZ (Day 1 Onsite) Duration: Long Term Contract Interview…
Job Description Job Description Benefits: ~401(k) Mobile QA Automation Engineer / SDET Atlanta, GA / New York, NY / Phoenix, AZ - Day 1 Onsite We are looking for a strong QA Automation Engineer / SDET to support testing…
What qa engineers earn in Phoenix
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $27–$39 | $56k–$82k |
| Mid level | $39–$54 | $82k–$112k |
| Senior | $51–$71 | $107k–$148k |
Adjusted for the Phoenix market from national ranges.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For qa engineers specifically — generic advice costs you here
Quantify your impact in defects: escape rate reduced, critical bugs caught pre-release, regression time cut.
Name your automation stack and the size of suites you built or maintained, such as number of tests or coverage of critical flows.
Show progression from manual to automation if that is your path — it is the expected trajectory and worth making explicit.
Mention the domains you tested (payments, healthcare, mobile) since domain risk knowledge transfers.
Include CI/CD integration work; a suite that runs on every pull request is worth more than one run by hand.
Where this role goes
Typical progression
Applying for qa engineer jobs in Phoenix?
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.