fun working together and take pride in our contributions to the nation’s safety.We are recruiting for junior, mid-level, and senior engineers with a background in Software Engineering to support our team. This position c…
QA Engineer jobs in Denver, CO
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 500 · sorted by freshness
Position: Staff, Hardware Test Engineer (Test Engineer, Staff)) Location: 8100 Shaffer Parkway Unit #100 Littleton, CO Job Id: 3040 # of Openings: 1 Through continuous innovation and operational...
assume sponsorship for employment visas for this position, now or in the future.The OpportunityLendingTree is looking for a Software Engineer to join our Insurance technology team and help build, enhance, and support web…
Connected Communities—helping local governments and school districts centralize data and streamline their operations. As a CloudOps Engineer, you will play a critical role in designing, building, and maintaining the high…
DescriptionParticipates in design, development and implementation of systems engineering activities, to include OS technical support, systems programming, and data center capabilities. Responsible for components of compl…
we can innovate, invest, inspire and integrate our capabilities to transform the future.Being a valued member of the Mechanisms Engineering organization, your responsibilities may include some of the following:• Lead the…
Per year (GS 14)Dates: Open 09/22/2026 to 09/29/2026Schedule: Full-timeWork type: PermanentRelocation: FalsePosition ID: CBVL-26-13069539-IMP-BDADocument ID: 885633000Grade: GS 14Job category: Civil Engineering (0810)Hir…
throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world?We believe building engineering is more than systems and structures, it’s about powering progress and enabli…
We are seeking a hands-on SDET / Wireless Automation Engineer III to design, develop, and maintain automation across infrastructure and engineering environments. The ideal candidate will have strong expertise in Ansible,…
through research and development, technology innovation or solution engineering, our team members play vital roles in connecting consumers with... ...multidisciplinary engineering teams. By establishing efficient QA stra…
Hiring: W2 Candidates Only Job Description: We are looking for a QA Automation Engineer to design, develop, and execute automated testing solutions for enterprise applications. The candidate will work closely with develo…
without incurring the high cost and risk of independent authorization. Position Summary The OpenFLIS team is seeking a Software Engineer with strong .NET and Angular skills to develop and maintain OpenFLIS's microservice…
What qa engineers earn in Denver
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $29–$42 | $61k–$88k |
| Mid level | $42–$58 | $88k–$121k |
| Senior | $56–$77 | $116k–$160k |
Adjusted for the Denver 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 Denver?
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.