and willingness to work in-office up to five days per week as business needs necessitate Our direct client has an opening for a QA Tester 5087 This position is up to 12 months, with the option of extension, and is locate…
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 314 · sorted by freshness
DescriptionJob DescriptionOverview\nJob Title: AI Test Automation Engineer - RegrelloLocation: Hybrid - Phoenix, AZ\nJob Type: Independent... ...Length: 12+ Months \n \nWe are seeking a highly motivated QA/ Test Automati…
Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed a…
Responsibilities Design, develop, and maintain automated test frameworks using Playwright, Selenium, Java, and Cucumber. Create and execute functional, integration, regression, and end-to-end testing across multiple appl…
quality issues complaints validations and other projects to the QA Manager and/or other interested parties. Performs all duties associated... ...Duties and Responsibilities Support site Quality Engineers/ Quality Special…
collaborative candidates who want to impact the world in a positive way. To learn more visit: Job Summary: We are looking for a Test Engineer to join our team. In this role, you will develop and execute test plans on clo…
Job Description Job Description Aerospace Software Test Engineer! Job Description This role focuses on verifying and validating safetycritical embedded software for aircraft and avionics subsystems. You will develop and…
supply chains and delivering unmatched quality and reliability to customers. Role Purpose Corning is seeking a Supplier Quality Engineer to support supplier quality and incoming material performance within our Solar Modu…
S. supply chains and delivering unmatched quality and reliability to customers. Role Purpose Corning is seeking a Quality Engineer to support product and process quality within our Solar Modular manufacturing operation.…
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…
Arrow's Phoenix Integration facility has an exciting opportunity to join the team as a Quality Engineer. In this role you will collaborate across multiple departments to ensure consistent and sustainable quality results.…
Roles & Responsibilities We are seeking an experienced QA Automation Engineer to join our technology team and help drive quality across modern web applications and APIs. The ideal candidate will have strong hands-on expe…
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.