[Hiring] Test Engineer @Ent

Role Description

This role owns end-to-end quality for new features as they ship: translating product intent into runnable coverage, building the frameworks that coverage runs on, and producing the test evidence that says whether each feature is ready to ship. The work spans the operator portal, the backend platform, and the endpoint agent, and includes making the team’s automated and AI-generated test scenarios trustworthy enough to gate a release.

What You’ll Achieve

• Own end-to-end testing for new features, from acceptance criteria through a runnable suite that gates the release.
• Review new requirements before they are built: turn underspecified ones into concrete pass/fail coverage, and surface what is not testable early.
• Architect and maintain the operator-facing end-to-end frameworks and fixtures — real-browser suites that run in parallel and gate CI.
• Cover the full journey across portal, platform, and endpoint agent — including the APIs and contracts between them, so an upstream break shows up before a consumer hits it.
• Curate the team’s automated and AI-generated test scenarios into trusted, runnable coverage.
• For the features you own, report what is tested, failing, and at risk — then close the gaps.

Qualifications

• 5+ years in software test, SDET, or quality engineering, with strong end-to-end and API coverage across UI, service, and integration layers.
• Built a browser end-to-end framework from scratch and integrated it into CI, owning the framework itself and not only the tests that run on it.
• Proficiency in Python and/or TypeScript, with Playwright (or an equivalent such as Selenium) driving parallelized suites.
• API and contract testing (Pytest, OpenAPI-driven; Postman or similar a plus), with the judgment to anticipate schema-drift risk.
• A record of turning ambiguous requirements into concrete, gating coverage.
• Sound judgment on the test pyramid — where end-to-end coverage earns its cost, and where it belongs at a cheaper, more stable layer.
• Clear communication in a distributed team, and the ability to drive adoption of shared test tooling.

Requirements

• Experience bringing AI- or LLM-generated test artifacts into a trusted workflow.
• Containerized test environments (Docker), and cloud familiarity — AWS, Azure, or GCP.
• CI experience with GitHub Actions, or a comparable system such as Jenkins or GitLab CI.
• Virtualization and provisioning for test environments — Packer, QEMU/KVM, or VMware.
• Load and performance testing.
• Security or data-protection product background.

Benefits

• Distributed workplace.
• Own a piece of the journey.
• We’ve got you covered.
• Take the time you need.
• Family matters.
• Live well.
• Set up your space.