Job Description The Quality Engineer supports Comecer Project Managers in the management of the orders from a quality point of view throughout the project including design reviews, FAT, SAT, IQ, OQ and some aspects of PQ…
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 142 · sorted by freshness
ATS Company: Comecer
Start or transition your career into Software Quality Assurance. Ace IT Careers is currently identifying candidates for QA Software Tester opportunities with employers and staffing partners across the United States . Thi…
Sr. Civil Engineer Sr. Civil Engineer For over four decades, Schmidt Associates has built our entire approach on the idea of Servant Leadership. As servant leaders, our design team seeks to deeply understand our clients…
Position: OT Automation Engineer Location: Indiana Duration: Long Term Job Overview We are seeking an experienced OT Automation Engineer to support automation, controls, and manufacturing technology projects in a regulat…
– whatever your ambitions. About the role: Boston Scientific was recognized by Forbes as one of the Best Workplaces for Engineers in 2026, reflecting a culture where engineers do meaningful work. Boston Scientific was re…
Specific Information 1223 West Morris Street, Indianapolis, IN - Pharma Services Group Discover Impactful Work: The Quality Engineer is responsible for providing oversight for commissioning and qualification activities a…
SENIOR AUTOMATION ENGINEER ABOUT US Matrix Technologies, Inc. has been a leading provider of engineering, automation, and systems integration services since 1980. Guided by "The Matrix Way," we value teamwork, collaborat…
view the total compensation package. A Day in the Life: The essential functions of this role are as follows: Develop engineering policies and plans projects concerned with unique or controversial problems which have a si…
Senior Automation Engineer – DeltaV | Pharmaceutical Manufacturing | Remote Location: Remote (Travel to Indianapolis, IN approximately one week per month) About the Opportunity We are seeking an experienced Senior Automa…
and facility renovations. As a Construction Quality Assurance Engineer, you will operate as part of a team that delivers new and modified... ...Quality Assurance teams with implementing the project-specific QA/ QC plan.…
IFP Automation is seeking a Sales Engineer focused on new account acquisition and gross margin growth within an assigned territory. This is a performance-driven role for a true hunter who wants to build a territory, win…
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.