How you'll make an impact

• The 3 Amigos: Actively participate in “3 Amigos” sessions with Product and Engineering to define clear, testable success criteria before a single line of code is written.
• Quality Gates: Help us establish and manage practical quality gates that prevent regressions without slowing down delivery.
• Value-Driven Automation: Guide our test automation efforts. You don’t need to write every script, but you will direct the “what” and “why,” ensuring automation focuses on high-risk business logic.
• The Signal in the Noise: Lead the triage of test results. You’ll distinguish between Test Failures, Technical Application Failures, and Failures Against Business Logic, ensuring the team spends time fixing what actually matters.
• Hands-on Verification: Move beyond generic test plans. You’ll focus on exploratory and functional testing that challenges the system’s logic and resilience.
• Practical Metrics: Establish lean, testing-specific metrics that help us understand our risk and velocity, avoiding “reports for the sake of reports.”
• Continuous Feedback: Collaborate directly with DevOps and Dev to integrate testing into our daily flow, advocating for “Shift Left” principles.

‍

What we're looking for

Required

• ‍The Gatekeeper Mindset: Proven experience in a senior testing role where you were responsible for final quality sign-off and risk assessment.
• Logic over Documentation: You prefer participating in a design session to writing a 50-page test approach that no one will read.
• Automation Translation: Strong affinity for test automation. You understand how frameworks (Python, Jenkins, etc.) work well enough to guide an automator toward delivering real business value.
• Analytical Triage: The ability to look at 100 failed tests and quickly filter the critical business logic breaks from the minor environment blips.
• Collaborative Spirit: Experience working in Agile/DevOps environments where you aren’t a silo, but a partner to developers and product owners.
• Communication: The ability to explain why a release is or isn’t ready in terms of business risk, not just technical jargon.

Nice to have

• Experience with Python or JavaScript for when you want to dive into the code yourself.
• Performance Insight: Familiarity with tools like k6 to help us understand our scale limits.
• Shift-Left Experience: A track record of moving testing “up the stream” to the requirements phase.
• Technical Debugging: Ability to look at logs (OpenTelemetry, CloudWatch) to help developers narrow down root causes.