SDET — Playwright & API Automation

REQUIRED SKILLS & EXPERIENCE Must-Have (Non-Negotiable) • 5+ years in software test automation in an SDET or Automation Engineer capacity • hands-on experience writing and maintaining E2E suites — POM, fixtures, workers, parallel execution Playwright (TypeScript): • fixture patterns, conftest, parametrize, reusable client abstractions Python / pytest: • structured assertions, status/schema/payload validation, chained requests REST API testing: • query/mutation execution, schema assertion, variable injection GraphQL testing: • reading and modifying pipeline configurations, understanding stage/step structure Jenkins: • stub authoring, request matchers, response templating WireMock: • branching, PRs, resolving conflicts — clean commit hygiene expected Git: • active use of AI coding tools (e.g., Claude Code, GitHub Copilot, Cursor) to accelerate test authoring, code review, and coverage analysis — demonstrated in prior work AI-Assisted Development: Strong Preference • Experience with SOAP/WSDL service testing • Postman / Newman for collection-based API smoke verification • Familiarity with microservices environments — understanding service boundaries and dependency chains • Background in Java/Selenium — useful for reading legacy test code during context gathering • AWS environment experience (test/stage environment topology) • Strong shell scripting for local test execution and CI debugging Nice to Have • Experience with hospitality, cruise, travel, or booking platform domains • Exposure to k6 or Gatling for performance baseline assertions • Familiarity with Spring Boot microservices from a testing perspective • ISTQB or equivalent certification WORKING EXPECTATIONS Day-to-Day • Embedded within an agile squad — attend standups, sprint planning, and retrospectives • Pick up automation tickets from the sprint backlog; deliver to definition of done within sprint • Raise blockers early — dependency on dev environments, test data, or stub availability should be flagged same day • All work committed to feature branches with PR descriptions matching team convention • Weekly sync with automation lead to review output quality and align on priorities • Onboard independently — read existing code, match patterns, and ask focused questions without needing step-by-step guidance Code Quality Bar • All tests must pass consistently — no flaky tests accepted into main pipelines • Follow existing naming conventions, folder structure, and assertion patterns exactly • No framework changes or architectural decisions without prior alignment with the lead SDET • Test coverage must be traceable to Jira stories — link tickets in PR descriptions • PRs must include a brief test strategy comment explaining what is covered and why