00 employees generated CHF 11.20 billion in sales in 2025. Job Description Sika is looking for an experienced Quality Engineer to join its growing team. In Grandview for our Automotive and Industry team. The Customer Qua…
Engineering & IT · Kansas City, MO
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.
206
Open roles today
$25–$65/hr
Typical pay range
$89k
Median, full-time
1
Fresh in this list
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.
01
Open qa engineer roles
5 shown of 206 · sorted by freshness
$190k - $230k
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…
CRB is a leading provider of sustainable Engineering, Architecture, Construction and Consulting solutions to the global life sciences and food and beverage industries. Our employees provide best-in-class solutions that d…
Operations Engineer - Precast Concrete GPAC has partnered with an industry leader in precast concrete , recognized for structural excellence, construction innovation, and a commitment to sustainability. We are seeking an…
$90k - $115k
This privately-owned company is rapidly growing and seeking an Automations Controls Engineer to design clear, complete and accurately working products and systems using CAD, rough or detailed sketches, and/or notes. For…
02
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.
03
What employers ask for
The skills these listings keep naming
Test planning and case designAutomation (Selenium, Playwright)API testing (Postman)A scripting language (Python, JS)Bug reporting and triageSQL for data verificationCI integration of test suitesExploratory testingAttention to detail
04
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.
05
Resume tips that move the needle
For qa engineers specifically — generic advice costs you here
01
Quantify your impact in defects: escape rate reduced, critical bugs caught pre-release, regression time cut.
02
Name your automation stack and the size of suites you built or maintained, such as number of tests or coverage of critical flows.
03
Show progression from manual to automation if that is your path — it is the expected trajectory and worth making explicit.
04
Mention the domains you tested (payments, healthcare, mobile) since domain risk knowledge transfers.
05
Include CI/CD integration work; a suite that runs on every pull request is worth more than one run by hand.
06
Where this role goes
Typical progression
01
QA Analyst
02
QA Engineer
03
Senior QA Engineer
04
QA Lead
05
Head of Quality
Ten quiet minutes a day
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.