> Markdown version of [/jobs/ext/2569607-test-automation-engineer-ni-veristand](https://www.wearedevelopers.com/jobs/ext/2569607-test-automation-engineer-ni-veristand). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Test Automation Engineer - NI VeriStand - **Company:** Redrouthu's Inc - **Location:** United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Testing (Software), Abstraction Layers, Application Programming Interfaces (APIs), JIRA, Automation of Tests, Microsoft Azure, Software Bug Management, CAN Bus, Code Review, Continuous Integration, Software Debugging, Firmware, Python (Programming Language), LabVIEW, Object-Oriented Software Development, Software Tools, Reverse Engineering, RS-232, Simulink, Software Engineering, Universal Asynchronous Receiver/Transmitter, Jama (Software), Data Logging, Teststand, Scripting, Hardware Testing, Git, System-level Testing, Pytest, Gitlab-ci, Polarion, Software Version Control, Jenkins - **Published:** August 28, 2026 - **Apply:** https://www.dice.com/job-detail/e2670a4c-c17d-4fb0-9a84-a3c977475d50 ## About the Role * 5+ years embedded systems, firmware, or system-level test engineering on physical hardware * NI VeriStand hands-on: system definition (.nivssdf), Real-Time Sequences (.nivsseq), stimulus profiles, workspace/screen configuration, custom devices; deploying to NI real-time targets * NI hardware: PXI/PXIe chassis, real-time controllers, DAQ modules, signal conditioning; configuration in NI MAX * Python: production-quality - OOP design, pytest or comparable, fixtures, hardware abstraction, structured logging and reporting * NI Python APIs: nidaqmx, nixnet, pyvisa, or demonstrable equivalent instrument-control work in Python * Electronics: reads schematics fluently, confident probing live PCBAs, proficient with scope, DMM, logic analyzer, bench supplies, electronic loads * Protocols: CAN and CAN FD, I C, SPI, UART/RS-232/RS-485 - at debugging level, not just familiarity * HIL concepts: closed-loop simulation, plant models, signal conditioning, fault insertion, real-time determinism * Tooling: Git; Jira, Azure DevOps, Polarion, or Jama, * Medical device experience under design controls - ISO 13485, IEC 62304, ISO 14971, FDA QMSR / 21 CFR Part 820 * Test method validation (TMV) and software tool validation in a regulated environment * LabVIEW and NI TestStand - especially for interpreting legacy custom devices and sequence orchestration * Simulink or model-based plant simulation feeding VeriStand * Electromechanical test: motor control, actuators, load cells, position/force sensing, battery systems * IEC 60601-1 and 60601-1-2 familiarity * CI/CD for hardware test (Jenkins, GitLab CI) and automated test reporting, This is not a fit for a general software test engineer with scripting experience. The differentiator is instrument and circuit-board fluency combined with software engineering discipline, someone who can probe a signal to explain why a migrated test behaves differently, then write clean reviewable Python to fix it. Technical screen should cover VeriStand architecture, CAN bus debugging, and practical Python instrument-control exercise. ## Description Analysis & reverse engineering * Analyze the existing VeriStand library: system definition files, Real-Time Sequences, stimulus profiles, workspace configurations, custom devices and document functional intent, signal mapping, and coverage of each test * Reconstruct test intent where documentation is thin or original authors are unavailable * Produce a migration inventory and sequencing plan covering dependencies, complexity, and priority Migration & Development * Port VeriStand test logic into the Python framework, maintaining functional equivalence with the legacy implementation * Build and extend Python hardware-abstraction layers over the NI stack - nidaqmx (DAQ, analog/digital I/O), nixnet (CAN/CAN FD), pyvisa (instrument and serial control) and over PXI chassis and real-time targets * Implement reusable fixtures, drivers, and utilities so the migrated suite is maintainable, not a one-for-one transliteration * Integrate migrated tests into version control and automated execution Verification of the migration * Design and execute an equivalence strategy: run legacy VeriStand and migrated Python tests against the same device under test and reconcile results * Investigate discrepancies, distinguishing genuine defects from timing, resolution, or signal-conditioning differences between environments * Document equivalence evidence to a standard suitable for design-control review Bench & hardware work * Bring up and maintain HIL benches: PXI chassis, NI modules, signal conditioning, wiring harnesses, load banks, simulated sensors and actuators * Debug at signal level with oscilloscopes, logic analyzers, multimeters, protocol analyzers * Support fault-insertion and boundary-condition testing on electromechanical subsystems Documentation & quality * Maintain traceability from migrated tests to source requirements and test protocols * Support test-tool validation and produce documentation consistent with design-control and DHF expectations * Participate in peer code review, protocol review, and defect triage ## Related Videos - [Testing .NET applications a Tool box for every developer](https://www.wearedevelopers.com/videos/704-testing-net-applications-a-tool-box-for-every-developer) - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Continuous testing - run automated tests for every change!](https://www.wearedevelopers.com/videos/190-continuous-testing-run-automated-tests-for-every-change) - [Collaboration Quantified: Lessons from Open Source Developer Networks](https://www.wearedevelopers.com/videos/1422-collaboration-quantified-lessons-from-open-source-developer-networks) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) ## Related Articles - [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [How to create a test plan for software testing](https://www.wearedevelopers.com/magazine/56-how-to-create-a-test-plan-for-software-testing) - [Should senior developers refuse interview coding challenges?](https://www.wearedevelopers.com/magazine/29-should-senior-developers-refuse-interview-coding-challenges) - [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development) - [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning)