Director of Verification

EBSCO Industries IncHoover, AL
Onsite

About The Position

At Moultrie, our cameras are in the field around the clock — in tree stands, on fence posts, deep in the woods — and our users trust them to work every single time. The Director of Verification is the person accountable for that promise. This is a senior technical leadership role with two core functions: a firmware verification organization responsible for validating every major camera subsystem before it ships, and a fleet management group responsible for monitoring the health of cameras already in the field and catching defects before users feel them. This role requires someone who can operate at the strategy level and still engage at the technical depth needed to direct a team of senior engineers across complex, multi-subsystem firmware verification. The north star for this function is clear: automate as much as possible, extend test coverage continuously, increase reliability, and reduce cycle time. If you’ve built verification programs at scale, know how to translate design changes into test plans, and understand what it takes to catch a problem in a CI pipeline before it reaches a camera in someone’s field — this role was built for you.

Requirements

  • 12+ years of experience in firmware verification, systems test engineering, or a related discipline for connected hardware or consumer electronics products.
  • 4+ years directly leading verification or test engineering teams, including senior individual contributors and sub-teams with distinct functional ownership. Experience managing both a pre-release verification function and a post-release monitoring or sustaining function is a strong signal.
  • Deep technical understanding of firmware verification across multiple subsystems — enough to evaluate test plans, identify coverage gaps, challenge the team’s approach, and recognize when a result doesn’t tell the full story.
  • Hands-on experience building or scaling test automation programs for embedded or firmware-based products, including CI pipeline integration and hardware-in-the-loop test infrastructure.
  • Proven track record of building the process that translates design changes into updated verification plans — and holding teams accountable to it across a full development program.
  • Experience with cellular IoT firmware verification is a strong plus — particularly LTE-M/NB-IoT, MQTT, retry logic, and connectivity edge cases.
  • Experience owning verification milestones within a structured hardware development program (EVT → DVT → PVT → MP), including phase gate ownership, open issue tracking, and release readiness assessment.
  • Familiarity with fleet monitoring concepts for connected devices — including telemetry analysis, anomaly detection, and the operational discipline of managing a large deployed device population.
  • Clear, direct communicator who translates verification risk into decisions at the program and executive level, and gives the team unambiguous direction.
  • Bachelor’s degree in Electrical Engineering, Computer Engineering, Computer Science, or a related field — or equivalent hands-on experience.

Nice To Haves

  • Background in one or more of Moultrie’s core subsystem domains: PIR/detection systems, cellular connectivity, image quality, or low-power embedded design.
  • Experience building or operating fleet monitoring infrastructure for IoT or connected hardware products at scale.
  • Familiarity with cellular certification processes — FCC, PTCRB, carrier acceptance — and the verification work that supports them.
  • Experience managing verification through hardware revisions and component changes in a production product, including re-verification scoping and execution.
  • Familiarity with DFMEA, PFMEA, or other structured risk management frameworks applied to hardware and firmware verification.

Responsibilities

  • Lead and develop firmware verification and fleet management teams
  • Set priorities, standards, and clear direction tied to product quality
  • Build an automation-first verification culture
  • Represent verification in design/program reviews
  • Own release risk decisions and tradeoffs
  • Align verification milestones with development phases
  • Own end-to-end verification across subsystems with focus on: Functional, Performance, Stability
  • Drive automation of all repeatable tests
  • Translate design changes into updated test plans
  • Integrate verification into CI pipelines (HIL testing, automation, reporting)
  • Track and expand test coverage across subsystems
  • Ensure test reliability and maintainability
  • Lead real-world validation across environments and use cases
  • Complement lab testing with field insights
  • Feed field failures back into automated test coverage
  • Align field validation with release milestones
  • Monitor deployed devices to detect issues before users do
  • Build dashboards and alerting for system health
  • Define escalation and response protocols
  • Feed field issues directly into verification improvements
  • Maintain a closed-loop feedback system between field and pre-release testing
  • Report fleet health trends and risks to leadership
  • Standardize verification plans, test reports, and defect tracking
  • Define metrics for verification and fleet health
  • Continuously improve processes based on learnings
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service