Quality Assurance Engineer

Nectir

2d•$54,000 - $152,000•Remote

About The Position

Nectir is seeking a Quality Assurance Engineer to enhance its QA processes and scale its automation efforts. This role involves building automation to significantly reduce manual QA turnaround time, collaborating closely with the current QA engineer, and reporting to engineering leadership. The position is expected to evolve towards software reliability engineering over time. The ideal candidate will have an engineering background, experience with test automation in production environments, strong communication skills, and a product-first mindset.

Requirements

An engineering background; you've written and shipped code, not just executed test cases.
Experience building and maintaining test automation (Playwright, Cypress, Selenium, or similar) in a real production environment.
Comfortable pushing back, including with senior engineers, when a process or PR isn't ready to ship.
Product-first instincts: you ask "what are we actually trying to achieve" before reaching for a technical or infrastructure solution.
Comfortable working with a significant overlap with US business hours.

Nice To Haves

Experience with release engineering, phased rollouts, or canary deployments.
Experience evaluating or standing up UI regression testing tools.
Interest in growing into a broader software reliability engineering role over time.
Background at a small, fast-moving team where you wore more than one hat.

Responsibilities

Evaluate and implement automated testing tools (e.g., Playwright-based frameworks, UI regression tools like Meticulous) to cut QA turnaround time.
Write and maintain test scripts and automated checks.
Take ownership of high-volume, repetitive QA work, such as dependency/package upgrade PRs.
Own visibility into the open PR queue, tracking PR aging and identifying bottlenecks.
Build a clear handoff process between Development and QA.
Proactively request necessary information from developers for QA.
Help design phased, contained release rollouts to limit the impact of bad deploys.
Grow into owning more of the release/rollout process as the role expands into SRE.