powers and advances the entire company by building and maintaining world-class technology capabilities and platforms. The Reliability Engineering team is the engineering-first function that owns the stability, observabil…
QA Engineer jobs in Indianapolis, IN
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 169 · sorted by freshness
We are looking for a Systems Engineer to support and enhance core enterprise infrastructure in Indianapolis, Indiana. This Long-term Contract position is ideal for a detail-oriented candidate with strong experience with…
Position Summary Lead Cloud Infrastructure Engineer II - Workplace Engineering/M365 AI & Engineering helps organizations build, deploy, and operate integrated solutions across software, data, AI, networks, and hybrid clo…
Job Description:NVH Test Engineer* Collaborate with Innovative 3Mers Around the WorldChoosing where to start and grow your career has a major impact on your professional and personal life, so it’s equally important you k…
organization offering tremendous career growth potential. Job Title: QA Automation Developer Location: 100% Remote (U.S.) Position... ...defects, create regression tests, and mentor junior QA engineers. Required Qualific…
tremendous career growth potential. Job Title: Software Quality Engineer Location: 100% Remote (U.S.) Position Type: Full-time,... ...Engineering, or a related technical discipline. ~6+ years of QA automation experience.…
with integrity, respect, responsibility, and professionalism.Vertex, located in Indianapolis, IN, is seeking a Senior Electrical Engineer I to support development, integration, and sustainment of ground‑based electronic…
Infinite Potential. And it’s your chance to really shine and contribute to one of the world’s most recognized brands and a beacon for engineering excellence.Position SummaryAn exciting opening for a Joining & Additive Ma…
DescriptionAt HDR, we specialize in engineering, architecture, environmental and construction services. While we are most well-known for adding... ...and cost opinions and writing technical documentsPerforming QA/ QC rev…
Position Summary AI & Engineering/ EaaS - DevOps Engineer IIIBuild and scale modern DevOps capabilities that help clients accelerate delivery, improve reliability, and modernize engineering operations. As a Senior Consul…
nation’s safety and security. Make an impact by using your expertise to protect our country from threats. Job Description TEST ENGINEER PRINCIPAL Transform technology into opportunity as a Test Engineer Principal at GDIT…
growth within our inclusive, team-oriented culture. Check out our Adjutant Solutions Group - Adjutant Solutions Group LLC website. QA Engineer Role Summary The Quality Assurance Engineer provides Quality Assurance suppor…
What qa engineers earn in Indianapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$36 | $51k–$74k |
| Mid level | $36–$49 | $74k–$102k |
| Senior | $47–$65 | $98k–$135k |
Adjusted for the Indianapolis 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 Indianapolis?
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.