*La version française suit

Company Description Headquartered in Montreal, Detroit and Munich, Vention helps manufacturers automate their operations in record time with the only hardware and software AI-powered platform built for the factory floor. Our technology powers over 25,000 machines across 4,000 factories across 5 continents and we have the privilege to work with a significant proportion of Fortune 500 manufacturers, from space rockets, to electrical cars, to robotics.

At Vention, you’ll work alongside driven and talented people who care deeply about their craft and the impact they create. We’re a team of high achievers who grow through meaningful work, solving complex challenges, learning fast, and seeing the results of our efforts every day.

We move quickly and aim high, but we do it together with care, collaboration, and respect. Our culture celebrates diverse perspectives and supports your growth through intentional development, strong leadership, and opportunities to make a real difference.

What You’ll Do

Build and lead the Software Reliability function , a recent team dedicated to the quality of everything that ships on the machine: MachineMotion controllers, firmware, and the programming platforms. You start with two QA engineers (software and firmware) and grow the team from there.

Own the quality of embedded software:

zero critical defects in production. On the edge, a shipped bug stays shipped. Many deployed controllers are air-gapped or intermittently connected and there is no guaranteed update path. Your mandate is to stop the defect from leaving, not to patch it afterwards.

Hold the release go/no-go.

You run the CRTP and the UAT, you publish the verdict,



and you have the authority to delay a release when the quality bar isn't met. The target is zero critical or high severity bugs at the UAT gate. We treat it like a FAT.

Automate the CRTP on real hardware:

HIL rigs and jigs running nightly regression, results pushed automatically from CI into Qase.io and into per-domain Slack alert channels. Automated coverage aligned 1:1 with what is manually verified today.

Build the E2E safety net

on top of the tests development teams write, without relieving them of writing them. You define the line between unit and integration tests (devs) and E2E harnesses (your team), and you keep developers accountable for the nightly tests they break.

Make quality visible:

metrics, dashboards, and failure archaeology. Classify field escapes by root cause and by the test that would have caught them, then close those gaps.

Act as L3 support

between Commissioning and Development. Early debugging of systems in the field, a seat at the weekly support meeting with Customer Success and Commissioning, and dispatching issues to the right team.

Work across the organization:

Hardware Reliability and Conformity, Operations and production QA, Security (vulnerabilities and new systems), Firmware, Robotics, and the platform teams. Aligned at every product launch and revision.

Raise engineering practice inside your own team:

manual review,



architecture of the platform-qa project, and disciplined use of AI-assisted development. A growing volume of generated code demands a correspondingly hard quality gate.

What You Bring to the Table

8+ years in software engineering or software quality engineering, including 2+ years managing or technically leading a team.

Real edge, embedded, or industrial systems background, not a generalist web QA profile. You understand what it means to ship to a target you can't redeploy in fifteen minutes.

Hands-on expertise in hardware test automation: HIL rigs, jigs, instrumentation, long-running soak tests, reproducing intermittent failures.

Genuine technical credibility. You hold your own in a code review and in an architecture review. Python and/or TypeScript, CI/CD, real time or near real time systems.

An understanding of physical systems: robotics, motion control, PLC, industrial I/O, automation. You know the feedback loop includes hardware that is expensive and unforgiving.

Backbone. You say no to a release when the data supports it, and you explain it in a way that gets heard rather than routed around.

A talent for growing people: coaching, recruiting, giving direct and useful feedback, turning a small team into leverage for the whole organization.

Clarity in communication. You can make a quality stake land with leadership and frame a risk stake for a development team. French and English.

A bias for measurement. You would rather have a dashboard that tells the truth than an opinion about the state of quality.

What We Offer

Career pathing: Real opportunities to grow through personalized development plans, bi-an

📌 Software Reliability Team Lead (Winnipeg)
🏢 Vention
📍 Winnipeg