Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Job Description
We are looking for a talented Software Automation QA Engineer to join our Storage team at NVIDIA. This role sits within the QA organization with a primary focus on validating Storage and Networking solutions that power NVIDIA's industry-leading products. The ideal candidate is QA and also automation-first in mindset, brings deep experience building robust test infrastructure for software, hardware and system-level environments, and thrives in a fast-moving engineering environment where quality and innovation go hand in hand.
What you'll be doing:
Design and develop scalable, reusable automation infrastructure and frameworks in Python/pytest — building systems that are stable, maintainable, and accelerate test coverage across teams
Own the automation lifecycle: from framework architecture and test development through scheduling, CI/CD integration, reporting, and failure analysis
Integrate test suites into Jenkins and GitLab CI/CD pipelines, enabling continuous validation across software releases
Develop AI-based internal tools to streamline team workflows — including automated failure triage, log analysis, test generation, and productivity tooling that reduces manual overhead
Review architectural designs and feature requirements, then translate them into comprehensive test plans covering functional, regression, performance, and security scopes
Identify, report, and help root-cause bugs found in hardware drivers, firmware interfaces, and system-level components; validate fixes delivered by R&D and track resolution to closure
Define lab topologies and setup configurations to ensure broad product coverage across Storage and Networking environments
Publish detailed test reports and contribute to data-driven quality decisions
What we need to see:
B.A. / B.Sc. in Computer Science, Electrical Engineering, or equivalent practical experience
2+ years of hands-on experience in Software QA Automation
2+ years of experience building and maintaining automation infrastructures using Python and PyTest.
2+ years of hands-on experience with Linux systems and Networking environments
Proven experience with CI/CD pipelines — Jenkins and/or GitLab CI
Hands-on experience testing hardware or system-level software (drivers, firmware, embedded systems, or similar)
Knowledge of Storage environments and protocols
Strong written and spoken English; clear communicator with a collaborative mindset
Ways to stand out from the crowd:
Demonstrated experience developing and deploying AI-based tools that improve engineering or QA team productivity
An AI-first mindset — proactively using AI to accelerate test generation, failure analysis, and framework development
Experience with Storage and Virtualization technologies (KVM)
Hands-on experience with traffic and I/O tools (FIO, DD, etc.)
Familiarity with Test-Driven Development (TDD) practices
NVIDIA is widely considered one of the technology world's most desirable employers. We have some of the most forward-thinking and hardworking people in the world working for us. If you're creative, automation-driven, and eager to work at the intersection of hardware and software quality — we want to hear from you.
NVIDIA is committed to fostering a diverse work environment and proud to be an equal opportunity employer. We do not discriminate on the basis of race, religion, color, national origin, gender, gender expression, sexual orientation, age, marital status, veteran status, disability status, or any other characteristic protected by law.
Audit details(provenance, verification trail, raw fields)
Core fields
nvidia:JR2025771Provenance
wd5|nvidia|NVIDIAExternalCareerSiteVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
LLM enrichment
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
