Job Description: Sr. Embedded Software Test Engineer As a Sr. Embedded Software Test Engineer, you will be responsible for developing and executing comprehensive test plans and test strategies for embedded software, firm…
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 508 · sorted by freshness
skills are a requirement due to the high level of interaction with engineering teams, management, and other organizations within Apple... ...Bachelors Degree in Computer Science or equivalent experience in QA Additional…
The Document Cloud Mobile team is looking for a Software Quality Engineer to play a key role in ensuring the high quality of our Acrobat... ...application on iOS. This role involves collaborating closely with our QA and…
farm to ensure uninterrupted operation , assist in debug of basic PCB or chip issues , document observations and report results to engineers Work closely and actively with engineers and technicians to collect required da…
way we do things. And we will be 100% committed to helping you reach your full potential. Job Description SUMMARY Engineer to perform Radio Frequency (RF) Over the Air (OTA) Antenna testing on mobile products with techno…
SDET Engineer - Cupertino, CA (Local Only) Fully onsite 5 days per week Candidate must be local and ready to start immediately. Reason for Opening / Business Driver : Integration and verification of third-party partner A…
job summary: Senior Embedded Software QA Engineer Looking for an opportunity to apply your hardware/software validation skills to high-impact products? We're seeking an experienced Embedded Software QA Engineer for a 6-m…
Job Title: Mobile QA / Android Test Engineer Location: Cupertino, CA - onsite Duration: Longterm contract position Client: Infosys/Apple Key Responsibilities: We are seeking a Test Engineer to design and develop integrat…
pre-compliance measurements, analyze test data against target regulatory limits, and document formal results to support internal engineering evaluations. External Lab Collaboration: Partner directly with third-party accr…
Job Title: Test Engineer (EPD II) Ingrasys Technology USA, Inc San Jose, CA & Sunnyvale, CA What to Expect This position is responsible for developing, modifying, and maintaining all test software and hardware systems to…
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…
the next generation of Ethernet NIC solutions for AI/ML and High performance computing applications. We are looking for excellent QA engineers to join the NIC product team. As a Software QA Engineer, you will be responsi…
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.