We are interested in candidates with curiosity about prompt engineering, context engineering, and evaluating AI-enabled products. We... ...and AI product tests, recording findings, and helping improve QA processes. We pe…
QA Engineer jobs in Charlotte, NC
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 378 · sorted by freshness
you ready to become a gamechanger and take the next big step in your leadership journey? As Sr Quality & Operational Excellence Engineering Manager at Honeywell, you will shape how quality and operational excellence come…
Job-ID29004217Reference26-21883Glider Assessment required prior to submission. Glider name: Senior Engineer_ Relay_Transmission. Please remember to push candidate to MSP in Glider. Remember to review genuineness verifica…
support economic vitality, public safety, sustainable and resilient communities and quality of life. We bring together planners, engineers, architects, construction management staff, environmental, strategic communicatio…
contingent resource assignment, you may: Consult on complex initiatives with broad impact and large-scale planning for Software Engineering. Review and analyze complex multi-faceted, larger scale or longer-term Software…
part of an inclusive, adaptable, and forward-thinking organization, apply now.We are currently seeking a Observability & Evaluation Engineer to join our team in Charlotte, North Carolina (US-NC), United States (US).Job D…
stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One.Job DescriptionThe Automation Engineer tests, creates, implements and supports robotics process and desktop automatio…
for collaboration, governance, and business discussions. Drive continuous improvement in performance testing and performance engineering practices. Required Skills ~10+ years of experience in performance testing/performa…
We are seeking an experienced Automation Developer to build and enhance automation solutions supporting IBM MQ Queue Manager migration . The role will focus on Python-based automation, API integration, workflow orchestra…
QA Engineer Charlotte, NC 6 Months Contract Role Overview QA Engineer to support end-to-end testing, test planning, and cross-team coordination across the phases of an ERP migration program, including in-person participa…
Job Summary We are seeking a Senior SRE / DevSecOps Engineer with strong experience in Kubernetes, AWS, container platforms, observability, infrastructure automation, and AI-assisted troubleshooting. The role will focus…
Senior Data Quality Assurance Engineer (Informatica, Tableau, QlikView, Quality Center, Data Strategies, Data Delivery, Hadoop) in Charlotte... ...of end users and downstream dependencies -Ensure the QA and application p…
What qa engineers earn in Charlotte
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $26–$38 | $54k–$78k |
| Mid level | $38–$52 | $78k–$108k |
| Senior | $50–$68 | $103k–$142k |
Adjusted for the Charlotte 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 Charlotte?
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.