Testing Lead

About the Role

We're all-in on agentic engineering, which means a lot of our code is written with AI coding agents. That raises the stakes on quality enormously, and it changes what a great SDET does. This is not a role that quietly writes CI tests behind the team. You are the gate: you define what "done and correct" actually means, you own acceptance testing, and you are the human backstop that decides whether AI-generated work is genuinely ready for production. You are validating both code quality and functional correctness, at the speed agentic delivery moves.

You'll work inside a Monks delivery team, alongside clients, product, and engineers, setting the quality bar and defending it. Tools like Claude Code and Codex are part of our everyday workflow, and we want someone excited to shape how quality works in that kind of team, not just keep up with it.

Who You Are

• A quality gatekeeper, not a ticket-taker: you own whether something ships, and you take that seriously.
• Skeptical by instinct: you go looking for the failure everyone else assumed away.
• A systems thinker: you hold both "is it built well" and "does it do the right thing" at once.
• A clear communicator: you can define "correct" so a client, an engineer, and an agent all understand it.

What You'll Do

• Own the quality gate for human and AI-generated code: acceptance testing, functional correctness, and regression coverage.
• Define acceptance criteria and what "done and correct" means, together with product and clients.
• Design and maintain automated test suites and frameworks across web, API, and end-to-end flows.
• Integrate testing into CI/CD and into the agentic development workflow itself.
• Push quality practices upstream so engineers and agents produce better work in the first place.
• Investigate failures and drive them to root cause.

What You Bring

• 8+ years in SDET, QA, or test automation, including ownership of test strategy.
• Strong coding ability (TypeScript / JavaScript and/or Python).
• Fluency with modern test frameworks. We are not prescriptive about which; examples include Playwright, Cypress, Vitest or Jest, and pytest.
• Real experience defining acceptance testing and functional validation, not only unit-level CI checks.
• Comfort reviewing and gating other people's and agents' output.
• Strong English communication skills.
• Comfortable in a fast-paced, agile consulting environment.

Extra Credit

• You've tested AI or LLM systems, or other non-deterministic output.
• Performance, load, or security testing experience.
• BDD experience (e.g. Gherkin).
• Depth with CI tooling and pipelines.
• You've built evaluation or quality frameworks from scratch.

#LI-SC1 

 #LI-Remote