Unless specifically stated otherwise this role is On-Site at the location detailed in the job post. The Manufacturing Software Test Engineer (MSTE) is responsible for developing and executing the strategy for production…
QA Engineer jobs in Kansas City, MO
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
9 shown of 226 · sorted by freshness
, and the Clowder mobile app. Together, we help our clients achieve great things.About our positionThe Software Quality Assurance Engineer (SQAE) tests the work of one or more product specifications at a time, attached t…
to view the mission vision and values that guide our work. Are you ready to do work that matters Summary The Chemical Engineer III role is a professional level position performing complex engineering functions on assigne…
role youll work on fast-paced projects from initial programming through system commissioning collaborating with Project Managers Engineers Technicians and customers to deliver high-performing building automation solution…
job summary: Randstad Digital is seeking an experienced QA Developer for an exciting opportunity in Kansas City, MO. This role... ...Bachelor's degree in computer science, Information Technology, Engineering, or related…
highlights and more. Ready to join us? Your Role We're seeking an experienced, automation-focused Senior Quality Assurance Engineer to join our North American Sports product team. This team develops insightful analytics…
Quality Engineer – Drive Quality Excellence for New Data Center Start-Ups! Location: Kansas City, Mo Travel Required | Multiple Locations Are you a detail-oriented Quality Engineer who enjoys solving problems, improving…
Rinvio is hiring a Mission Critical QA/QC Engineer / Manager for quality management for data center and mission-critical MEP construction in the Kansas City, MO market. Pay: $190,000-$230,000/year, based on experience Lo…
Our client is seeking an experienced Quality Engineer to ensure that plastic injection molded components meet all customer, internal, and regulatory requirements. This role supports production, engineering, and suppliers…
What qa engineers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$36 | $52k–$75k |
| Mid level | $36–$50 | $75k–$103k |
| Senior | $48–$65 | $99k–$136k |
Adjusted for the Kansas City 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 Kansas City?
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.