their dreams. At Ford, you can build more than vehicles. Come build what matters.In this position... The ADAS Software Update Systems Engineer owns the system design, specification, and analysis of software update/OTA (o…
QA Engineer jobs in Detroit, MI
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 159 · sorted by freshness
Job DescriptionThe RoleThe Automation Integration Engineer is a member of the HR Technology team and responsible for designing, building, and implementing intelligent plugins and automations that enhance our enterprise w…
software architecture, writing code, testing for quality and deploying the software to meet customer requirements. Full-stack software engineering roles, who can develop all components of software including user interfac…
Job DescriptionThe RoleGeneral Motors is seeking a Principal Software Engineer to shape and scale the engineering platforms that build, test, integrate, validate, and deliver embedded software for software-defined vehicl…
Job DescriptionThe Role: General Motors is seeking a software engineering leader to modernize and scale the build systems that support software-defined vehicles. This role will help lead the transition from a legacy Make…
Job DescriptionAs a Virtual Analysis Engineer in GM’s Body Manufacturing Product Interface organization, you will help ensure vehicle designs are manufacturable, robust, and aligned with Body Manufacturing Requirements (…
Job DescriptionJob DescriptionGeneral Motors is seeking a technically strong and highly motivated Design Release Engineer (DRE) to lead the development and launch of external microphone hardware and associated components…
candidate is expected to report to Austin, TX or Warren, MI three times per week, at minimum.The RoleAs a Mobile Senior Software Engineer, your focus will be on creating cutting-edge mobile applications that provide an e…
determined, innovative individuals who will join our team to help move us forward and achieve our mission. The RoleAs a Software Engineering - Site Reliability Engineer (SRE) on the Connectivity team, you will drive the…
assignment in support of DTE’s emergency response to storms or other events that impact service to our customers.Job Summary Senior level engineer responsible for planning and conducting intermediate to more complex engi…
Nothing” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed an…
webhooks, and event-driven integrations.Experience operating large-scale GPU clusters, including capacity management, reliability engineering, change management, and performance validation for AI training, inference, HPC…
What qa engineers earn in Detroit
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 Detroit 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 Detroit?
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.