staffingfuture.comWould welcome a developer in test (writing test automation) and/or standard developer. Looking for strong core engineering skills.Can you please confirm your top 3 skills sets required?Experience in dev…
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 266 · sorted by freshness
Ethernet standard, helping define and deliver next‑generation Ethernet semantics optimized for HPC and AI at scale. In this role, the engineer contributes directly to the product definition, implementation, and bring‑up…
Provide information to technology colleagues, internal partners, and stakeholders Required Qualifications: • 4 years of software engineering experience, or equivalent demonstrated through one or a combination of the foll…
learn how you could help make great things possible not only in your community, but around the world.In the role of Senior Mechanical Engineer (Pipe Stress), we'll count on you to:Perform pipe stress analysis and piping…
will help shape the future of healthcare while building a career grounded in purpose, growth, and impact.A Day in the LifeThis Test Engineer position is responsible for providing key technical expertise and organizationa…
SUMMARY Mortenson is currently seeking an Engineer III or IV - Wind Collection that will be responsible for supporting preliminary and detailed... ...and/or tasks consistent with engineering policies and Mortenson QA/ QC…
Description******This role is 100% remote but they will prioritize Minneapolis area This Sr. Engineer position will sit on our Advisor Marketing Practice & Promotion product team (AMPP) within the MarTech portfolio. We b…
better. Read further to learn how you could help make great things possible not only in your community, but around the world.HDR Engineering is currently seeking an Electrical/Senior Electrical Engineer to join one of th…
possible not only in your community, but around the world.HDR Engineering is currently seeking a Mechanical/Senior Mechanical Engineer to... ...documentsProvide construction contract administration as neededConduct QA/ Q…
Basic Qualifications Bachelor's degree in Electrical Engineering, or a related Science, Engineering or Mathematics field, plus a minimum of 8 years of relevant experience; or Master's degree plus a minimum of 6 years of…
stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One.Job DescriptionThe Automation Engineer tests, creates, implements and supports robotics process and desktop automatio…
Job Description Senior SDET – Quality Engineering, RBC Capital Markets, LLC, Minneapolis, MN: Provide support to Quality Engineering (QE) Manager on estimation and work allocation for the team acting as a release lead in…
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.