Job Description & Details
This is a hands-on SDET role focused on building out integration automation frameworks for safety-critical systems and vehicle fleets. If you like the idea of moving away from tedious manual regression cycles and instead architecting robust mocking frameworks and Playwright test suites, this gig in Foster City is worth a serious look.
What You'll Actually Be Doing
Expect to spend a good chunk of your week designing backend mocking frameworks so the team can decouple mobile app testing dependencies. You'll be knee-deep in writing, maintaining, and expanding Playwright automation scripts while partnering closely with developers and product managers. Beyond standard software testing, you'll also dive into vehicle mission testing, analyzing validation outcomes, and occasionally triaging defects across staging, development, and production.
The Core Tech Stack
You'll need strong programming fundamentals in Python, Java, Kotlin, or Swift—Python and Playwright being especially critical for the automation frameworks here. Because this role touches validation and system integration, you should be comfortable navigating AWS cloud apps, containerization with Docker and Kubernetes, CI/CD pipelines, and version control via Git. Familiarity with PyTest and API testing methodologies will be your bread and butter on a daily basis.
Interview Expectations
Be ready for them to test your system design chops regarding test architecture, particularly how you would architect a scalable mocking framework from scratch for asynchronous backend services. They want to see that you understand the trade-offs between speed and test reliability. Secondly, expect a live coding or debugging scenario involving Playwright or asynchronous test execution where they will evaluate how you handle flaky tests and edge cases in a complex CI/CD pipeline.
Application Advice
To get past the ATS, make sure your resume explicitly highlights your experience with Playwright, API testing, and building automated frameworks from the ground up rather than just maintaining them. Emphasize any past work involving Docker, Kubernetes, or CI/CD pipelines to show you can handle the infrastructure side of modern QA. Tie your metrics back to test coverage improvements and reduced manual testing hours.