Senior Software Development Engineer in Test (SDET)

We are looking for a Senior SDET who designs quality into the system and proves it in code. You own quality, reliability, and performance through test architecture and automation you write, review, and maintain. You use AI as a force multiplier, and you stay accountable for the engineering judgment behind everything those systems produce.

You design the test strategy and the frameworks behind it. You write clean, reusable automation with meaningful assertions, review peers’ test and application code for correctness and coverage, and shift quality left so risk and coverage are defined before development starts. You establish best-in-class practices for how this team builds, reviews, and ships tested software. You advocate for quality, act before you are asked, and challenge weak design, thin coverage, or “this is how we’ve always done it” when it puts the customer at risk. You adapt to a fast-paced engineering culture: changing priorities, short cycles, and delivery without lowering the quality bar.

Key Responsibilities

• Code, review, and pull requests
• Write strong, hands-on automation in JavaScript/TypeScript and Node.js: clean, reusable test code with meaningful assertions, held to the same standard as product code.
• Design, build, and maintain E2E tests (Cypress, WebDriverIO) and API tests (Karate).
• Review peers’ test and application code for correctness and coverage, not just style. Hold the line on merges that skip the quality bar.
• Raise small, reviewable pull requests and own the path from branch through review, CI, and merge. Use required checks, coverage expectations, and review standards as the team’s quality contract.
• Keep tests requirement-traced from design through automation. CI and release results are the source of truth for pass/fail.

Architecture, frameworks, and CI

• Design test architecture for distributed, service-based systems. Identify risk and test at the right layer: prove rules and data in API tests, and use UI or mobile only when that surface is the proof.
• Apply design thinking in planning and solution design. Treat testability, observability, and failure modes as part of the design, and surface untestable designs, missing contracts, and customer risk before code is written.
• Design or significantly extend automation frameworks for web, mobile, and API testing, including reusable components, environment configuration, and test data management, so suites run reliably and other engineers can extend them.
• Own automation in CI/CD: triage flaky tests, control execution time, keep quality gates meaningful, and drive failing jobs and defects to close.

Shift-left quality and ownership

• Get involved early in design and requirements. Identify risk and define test coverage before development starts, and partner with developers on testability.
• Work from specifications and scenarios. Map every acceptance criterion to API, Web, and/or Mobile, or mark it not applicable with evidence.
• Establish and uphold best-in-class practices: test coding standards, review checklists, framework patterns, defect hygiene, and release-readiness criteria the team follows.
• Own team quality outcomes—architecture, coverage, automation standards, pull-request gates, and release readiness—and speak up on risk, gaps, and untestable stories when scope or timelines move.

AI, with engineering accountability

• Use AI agents to design cases, implement automation, and raise reviewable pull requests that extend existing frameworks. Apply prompt engineering and RAG so output is grounded in specifications, existing tests, architecture, and standards.
• Review and correct agent output in the same pull-request workflow as human-written code. Stop when evidence is missing. Treat pipeline proof and human review as the bar for calling AI-assisted work done. Protect secrets and customer data in prompts and retrieval.

Required Skills

• 7–8+ years in Quality Engineering or as an SDET, with a record of writing, designing, and reviewing automation code.
• Strong hands-on automation coding in at least one modern language, with depth in JavaScript/TypeScript and Node.js. You write clean, reusable test code with meaningful assertions.
• Hands-on Cypress, WebDriverIO, and Karate.
• Proven experience designing or significantly extending automation frameworks for web, mobile, and API testing, including reusable components, environment configuration, and test data management.
• Understanding of distributed and service-based systems, used to identify risk and test at the right layer.
• Ownership of automation in CI/CD: flaky-test triage, execution-time control, and quality gates.
• Code review and pull-request workflow experience: reviewing peers’ test and application code for correctness and coverage, raising reviewable pull requests, and using CI gates to protect main.
• Shift-left practice: early involvement in design and requirements, coverage defined before development starts, and partnership with developers on testability.
• Experience establishing best-in-class testing practices that other engineers adopt.
• Practical use of AI coding agents, with prompt engineering and retrieval-backed (RAG) workflows, and the judgment to accept, revise, or stop generated work.
• Proactive quality-advocate posture, Agile/Scrum experience, and the ability to deliver quality under changing priorities.
• Strong analysis, troubleshooting, and cross-team collaboration.

Nice to Have

• Performance and load tools alongside CI/CD integration of automated tests.
• Spec-driven or agentic workflows; evaluating the quality of RAG or conversational AI features.
• Experience defining engineering standards, review guidelines, or test architecture used by more than one team.