QA Engineer, Vivid Machines

• We care more about strong testing fundamentals and judgment than about matching a tool list. You don't need to be a deep specialist in every layer
• You do need to know how to test each one competently, and when to bring in a subject-matter expert
• 3–5 years of QA/testing experience with practical STLC knowledge
• Hands-on manual testing across at least two of web, mobile and backend/API systems
• Working knowledge of Python and at least one Python test framework, preferably pytest
• Experience writing, maintaining and enforcing regression and automated test suites, including reviewing tests written by developers
• Experience working directly with Product Owners or Managers to refine and validate acceptance criteria
• Comfort reading basic hardware/device logs or working with hardware-in-the-loop test setups
• Familiarity with bug tracking and test management tools such as Jira, TestRail or similar, and an understanding of CI/CD concepts
• Clear, structured documentation habits for test plans, defect reports and release notes
• Self-direction. You figure out what matters most from the backlog, release goals and open bugs. You check docs, logs, past tickets and trial results before escalating. You raise risks, mistakes and uncertainty early, and you can push back collaboratively when quality or clarity is at risk

Desirable

• As an Intermediate QA Engineer, you will own the end-to-end Software Testing Life Cycle across our whole product: web applications, mobile apps, backend services, and the camera hardware itself
• You'll plan tests, run them by hand, maintain regression coverage, and write Python automation
• You'll also work closely with Product Owners and Managers so acceptance criteria are clear, testable and complete before development starts
• Our product runs from a camera on a farm vehicle, through embedded firmware and a mobile app, to backend pipelines and the dashboards growers use to make decisions. You'll be the person who makes sure it all works, and keeps working, release after release
• Sharpen requirements before code is written. Work with Product during backlog refinement to make acceptance criteria clear, testable and complete on edge cases. Flag gaps early, not during test execution
• Own the STLC end to end. That covers requirement analysis, test planning, test case design, execution, defect tracking and sign-off, with test cases traceable back to the original ticket
• Test across every layer. Do functional, exploratory, integration and regression testing on web, mobile and backend. Check where hardware meets software: device behaviour, camera and sensor input, and connectivity states
• Write bug reports developers can act on immediately. Include steps, environment, logs, and expected vs. actual results
• Automate what should be automated. Build and maintain Python test suites (pytest, Playwright/Selenium, requests for APIs), integrate them into CI/CD, and steadily reduce manual regression work
• Set the quality bar for the whole team. Define end-to-end and automated test coverage standards as part of the definition of done, review developer-written tests, and push back when acceptance criteria aren't covered
• Make releases a confident decision. Run smoke and sanity testing, write go/no-go reports, look after test environments and data, and track quality metrics (defect density, coverage, pass/fail trends) over time
• Run your own week. Prioritize against sprint and release goals, investigate blockers before escalating, and keep a distributed team informed through clear written updates
• What success looks like:
• You consistently know what to work on next without needing it assigned
• Tickets enter development with clear, testable acceptance criteria
• QA-written and developer-written automated tests meet a consistent coverage bar
• Regression suites stay current and catch real issues before release
• Failures are caught, reported and resolved quickly
• Releases ship with confidence, backed by clear, traceable test evidence