Salary: $81,000 - 121,000 per year Requirements: We want a bachelors degree in Computer Science, Data Science, Mathematics, or a related discipline, or equivalent professional experience. We need at least 7 years of soft…
QA Engineer jobs in San Francisco, CA
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 614 · sorted by freshness
Salary: $155,000 - 210,000 per year Requirements: We are looking for a bachelors degree in Computer Science, Data Science, Math, or a related field, or equivalent industry experience. We need at least 7 years of software…
longer be accepting applications. Thank you Join the WeVote Movement WeVote has several open volunteering positions for QA Automation Engineers to help strengthen American Democracy via our Web and Mobile applications. T…
Manager, Site Reliability Engineer (Hybrid in South San Francisco)About the RoleWe are seeking an experienced and hands-on Site Reliability Engineering (SRE) Manager to lead our Site Operations and infrastructure initiat…
biotech and pharmaceutical companies to design, execute, and manage complex scientific manufacturing processes at scale. Our workflow engine is the foundational layer — a system that lets scientists and operators model t…
your Full Copy Sandbox into a production-like environment for true scale validation.Our mission: make any developer a performance engineer through a low-code, intuitive test automation experience.The RoleWe're looking fo…
future of AI software delivery — and we’re looking for exceptional talent to help us move even faster.Position SummaryForward Deployed Engineers work embedded inside enterprise engineering teams to design and build AI-na…
: ANA United StatesWork Type: HybridDate Posted: 2026-08-28Arcadis is the world's leading company delivering sustainable design, engineering, and consultancy solutions for natural and built assets.We are more than 34,000…
Job Overview We are seeking an experienced Quality Assurance Engineer to join our team. The successful candidate will have a strong background in software testing, excellent analytical and problem-solving skills, and the…
fraud/abuse (Radar), payment optimizations (AuthBoost), Disputes, Authentication, and merchant analytics. We’re a mix of machine engineering engineers and full-stack software engineers impacting ~every Stripe transaction…
games, and live sports to more places around the world across a wider range of consumer experiences and devices. As a Staff QA Engineer in the Dolby Cinema QA group, you will provide senior test leadership for next-gener…
Primary.Health is the engine behind your COVID-19 testing and vaccination programs. Our web-based platform provides government agencies... ...state databases, easing the reporting process. JOB TITLE: QA Engineer JOB TYPE…
What qa engineers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $37–$54 | $77k–$112k |
| Mid level | $54–$74 | $112k–$154k |
| Senior | $71–$98 | $147k–$203k |
Adjusted for the San Francisco 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 San Francisco?
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.