Total Experience: 8+ Years

Position: Contract SDET Playwright & API Automation

Contract: 12+ Months

Roles and Responsibility:

We are looking for a contract Senior SDET to augment our Digital Engineering automation team on a time-sensitive initiative. The contractor will contribute immediately to expanding Playwright UI automation and Python/pytest API coverage across our digital commerce platform. This is a hands-on, high-output engagement we need someone who can read the codebase, understand our standards, and ship tested, maintainable automation from week one.

The ideal contractor has done this before in a similar environment, brings proven patterns rather than syntax knowledge, and actively leverages AI-assisted development tools to accelerate delivery without sacrificing quality.

SCOPE OF WORK

Primary Deliverables

- Implement end-to-end Playwright (TypeScript) test suites for assigned user journeys committed, reviewed, and running clean in CI
- Expand Python/pytest API test coverage across assigned service domains REST, GraphQL, and/or SOAP as applicable
- Integrate all new tests into existing Jenkins pipelines with correct tier tagging (smoke / sanity / functional)
- Write and maintain WireMock stubs required to support current test scenarios
- Participate in PR reviews — apply and adhere to existing automation standards
- Document any new patterns or deviations introduced, for handoff to the permanent team

AI-Assisted Delivery (Required)

- Use AI coding assistants (Claude Code, GitHub Copilot, Cursor, or equivalent) as a standard part of the development workflow — not optional
- Apply AI tools to accelerate test scaffolding, fixture generation, assertion patterns, and WireMock stub authoring
- Use AI-assisted code review to catch issues before PR submission — reduce back-and-forth review cycles
- Leverage AI for coverage gap analysis — identify untested paths and prioritize based on risk




- All AI-generated code must be reviewed, understood, and validated by the contractor before committing — quality ownership remains with the individual

Out of Scope

- Framework architecture redesign — follow existing standards, do not rebuild
- Infrastructure or CI pipeline changes outside of test job configuration
- Jira project administration or test management tool configuration
- Hiring, interviews, or team management activities

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

Communication

- Primary channel: Slack — responsive during working hours
- Escalate scope questions early — do not interpret ambiguous requirements alone

Regards,

Aditi Agnihotri

[email protected]

📌 Contract SDET Playwright & API Automation (Noida)
🏢 FCS Software Solutions
📍 Noida