Salary: $180,600 - 271,000 per year Requirements: We require a bachelors degree in Engineering, Information Systems, Computer Science, or a related discipline plus 6+ years of software engineering or related experience,…
QA Engineer jobs in San Jose, 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 649 · sorted by freshness
SRE, and product teams to ensure high-quality software releases. Leverage Cursor, Microsoft Copilot, and OpenAI tools to improve test automation productivity and test coverage. Create and maintain QA documentation, test…
Job Description Must Have Technical/Functional Skills Experience in QA automation with strong programming skills in languages such as Python, Java, or similar. Knowledge of AI/ML concepts and practical experience applyin…
findings clearly. Preferred qualifications include robotics, motion control, signal simulation, speech and audio testing, agentic test engineering, C, C++, Java, electrical engineering, and consumer electronics, automoti…
is scaling field deployments 5×, and we’re looking for a senior engineer to own the technical execution and continuous improvement of hardware... ...automation, data, and cross-functional processes that allow HW QA to sc…
Job-ID29371793Reference26-27092Salary$0.01 / hourRemote50% Remote Description As a Software Engineer, you make direct technical contributions. You execute on assigned software engineering tasks with some guidance, feedba…
QA of Semiconductor Equipment Software Semiconductor Manufacturing fundamentals domain knowledge. MES & Equipment Automation understanding to support end to end CIM automation solution. Project management tasks in accord…
Position: Network Software Test Engineer Location: San Jose, CA (Onsite) Contract 12+ Months Note: L2/L3 protocol development... ...solutions. ~ Experience with PyTest or similar open-source QA automation frameworks. ~ E…
technology with the versatility demanded by modern AI workloads.Position OverviewWe are seeking an experienced design automation engineer passionate about driving innovation at the intersection between emerging semicondu…
, scalable, reliable media solutions • Partner closely with research, development, and product teams as part of an integrated engineering effort • Work effectively in a fast‑paced environment with dynamic projects; Agile…
enterprises, 9 of the 10 largest mobile network providers, and hundreds of governments and educational organizations. As a Senior SW QA Engineer on the GigaSMART team, you will lead quality assurance efforts for advanced…
physical network hardware, external clients, servers, or network devicesWork with other testers, developers, and professional services engineers to qualify & reproduce problemsWork both independently and with senior engi…
What qa engineers earn in San Jose
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $37–$53 | $76k–$110k |
| Mid level | $53–$73 | $110k–$152k |
| Senior | $70–$96 | $145k–$200k |
Adjusted for the San Jose 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 Jose?
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.