business develops cardiac mapping and ablation technologies used to treat patients with abnormal heart rhythms. The Principal Systems Engineer will serve as a recognized technical leader connecting customer and clinical…
QA Engineer jobs in Minneapolis, MN
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 439 · sorted by freshness
Job Description: BS degree in electronics / electromechanical with 5 years experience in hvac , electromechanical troubleshooting and test plan development and execution UL/ul555 certification and testing experience Expe…
Details: Stefanini Group is hiring! Stefanini is looking for an Python Engineer for Minneapolis MN/New York NY/Kansa City MO. For quick Apply please reach out to Prakhar Goel: / W2 Candidates Only! The Business Automatio…
Technical/Functional Skills 1. Possess good Experience in Engineering Converting Automation Solutions like Roll loading automation, Auto-splicing, Buffering, Web Tension Control, material replenishment, inspection etc. 2…
About the Opportunity Ace IT Careers is recruiting for an Entry-Level QA Tester opportunity focused on evaluating the functionality, usability, and performance of mobile applications. This position is suitable for recent…
Responsibilities: All aspects of Quality Assurance for mechanical, plumbing, and controls systems, amongst others. Read and understand engineering drawings including; wiring, architecture, and sequences. Capable of sugge…
Arrangement: On-site Relocation: Relocation assistance available for qualified candidates Search: Nationwide Director of Engineering – Electrical, Controls & Industrial Automation A growing industrial manufacturer is see…
A client of Innova Solutions is immediately hiring for a Senior QA Engineer Position type: Full-time Contract Duration: 12 months Location: Minneapolis MN As a Senior QA Engineer you will: Youll become the guardian of qu…
innovation and customer experience drive every decision. Join us and help shape the future of sleep wellness. Senior Supplier Quality Engineer Sleep Number is seeking an experienced Senior Supplier Quality Engineer (Sr.…
Job Description Job Description The Sr Software Test Engineer leads verification, validation, and quality efforts for embedded software and autonomous robotic systems. This hands-on role develops automated test framework…
Here, you’ll be supported in progressing – whatever your ambitions. About the role: This Principal Software Design Quality Engineer position will support active implantable medical devices. This position serves as a lead…
Quality Engineer or Sr. Quality Engineer based on experience to join a tenured team located commuting distance of the greater Minneapolis, MN area. What is Offered to You! ~ Competitive Salary ~ Bonus Potential ~401K wit…
What qa engineers earn in Minneapolis
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 Minneapolis 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 Minneapolis?
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.