Job Description & Details
This is a hands-on technical coaching role where you will spearhead the rollout of Playwright and MCP (Model Context Protocol) for an enterprise testing transformation. Instead of just writing test scripts, you'll act as the bridge between the core Testing COE and a diverse crowd of non-technical stakeholders like Scrum Masters and Product Owners, helping them adopt AI-assisted testing workflows. If you enjoy mentoring engineers, architecting automation standards, and living on the bleeding edge of AI-driven QA, this is a rare opportunity to shape how an entire organization tests software.
What You'll Actually Be Doing
You will spend your days partnering with the internal Testing COE to drive the adoption of Playwright and MCP right as it goes live. Your time will be split between refining automation suite designs, troubleshooting complex failure modes, and building hands-on labs and enablement content. You aren't just building tests here; you are building the curriculum and repeatable paths that allow non-developers to review, validate, and build comfort with AI-generated test suites without needing to become full-stack coding experts.
The Core Tech Stack
Playwright and MCP are non-negotiable bread and butter for this role, and you need deep, production-level familiarity with how modern automation tooling interacts with AI and LLMs. Beyond that, having a solid grasp of the Atlassian ecosystem and Google Cloud Platform will help you navigate the existing infrastructure smoothly and integrate your coaching seamlessly into their current deployment pipelines.
Interview Expectations
Expect the hiring team to test your deep architectural understanding of Playwright alongside your ability to troubleshoot asynchronous code execution and flaky tests on the fly. They will likely present a scenario where an AI-generated test suite fails intermittently due to DOM changes and ask you to walk through how you would configure MCP and Playwright to resolve it. They are secretly looking for both your raw technical chops and your communication style—can you explain complex test automation concepts clearly to a non-technical Scrum Master without talking down to them?
Application Advice
Make sure your resume leans heavily into your concrete Playwright automation experience, specifically highlighting any instances where you built training materials, mentored teams, or coached non-QA roles. Ensure keywords like 'Playwright', 'MCP', 'Test Automation Strategy', and 'Enablement' are prominent so you breeze past the ATS filters. Frame your past work not just in terms of scripts written, but in terms of engineering culture and quality metrics improved.