Search

SDET - UI QA with Automation & Trading

PublishedPublished: 6/14/2022
Technology
|

Job Description

Role: SDET – UI QA with Automation & Trading

\n

Location: NYC, NY (Hybrid/Onsite)

\n

Duration: Long-Term Contract

\n


\n

Responsibilities

\n

    \n
  • Co-architect and co-own, with the Backend SDET, a unified testing framework covering all testing areas:
  • \n

  • Shared foundations: Fixtures, test data, configuration, environments, and reporting shared across UI, API, Kafka, database, and performance suites.
  • \n

  • Cross-layer scenarios: A single scenario can span multiple layers. For example, a test places an order in the UI and then validates the resulting event and database record.
  • \n

  • One quality view: Results from every suite feed into a single view of release quality.
  • \n

  • Design, build, and maintain end-to-end and component tests using Playwright and TypeScript for trading and analytics workflows.
  • \n

  • Extend the shared test toolkit, including page objects, fixtures, and mocks of desktop-container APIs.
  • \n

  • Build front-end testing harnesses for real-time data using mocked WebSocket and REST responses, controlled test data, and deterministic replay of streaming updates.
  • \n

  • Cover UI failure scenarios, including disconnects and reconnects, expired sessions, permission failures, bursty feeds, and stale data.
  • \n

  • Own front-end performance testing:
  • \n

  • Startup and responsiveness: Measure application startup and time-to-first-data, and ensure UI responsiveness under high update rates.
  • \n

  • Grid behavior at scale: Measure rendering and scrolling performance of grids with tens of thousands of rows.
  • \n

  • Container resources: Track memory growth, leaks in long-running desktop sessions, and CPU usage per window.
  • \n

  • Regression gates: Establish performance budgets that fail CI when regressions occur.
  • \n

  • Build and maintain isolated, on-demand test environments on Linux and AWS:
  • \n

  • Lifecycle: Environments are created per branch or test run, initialized with seeded data and a known state, and automatically torn down.
  • \n

  • Isolation: Ensure test runs do not interfere with each other or shared environments.
  • \n

  • Validate front-end/back-end contracts and payload schemas.
  • \n

  • Run UI test suites in CI/CD, including sharded parallel runs, scheduled regressions, and pull-request reporting.
  • \n

  • Make failures diagnosable through Playwright traces, screenshots, videos, and correlation with telemetry.
  • \n

  • Work with UI engineers, business analysts, and traders to automate critical workflows and define QA acceptance criteria.
  • \n

  • Use AI-assisted tools where helpful for writing, maintaining, and triaging tests.
  • \n

\n

Qualifications

\n

    \n
  • 5+ years of UI test automation experience, including designing or significantly extending an automation framework.
  • \n

  • Strong TypeScript/JavaScript and Node.js skills, with substantial hands-on Playwright experience. Strong Cypress or Selenium experience with willingness to transition to Playwright is also acceptable.
  • \n

  • Working Python skills (pytest, Playwright for Python) for test tooling, data setup, backend checks within UI scenarios, and contributions to the shared framework.
  • \n

  • Experience testing React applications with complex data grids (AG Grid or similar), dynamic forms, and heavy client-side state.
  • \n

  • Experience mocking browser network traffic (REST and WebSocket) and testing authentication flows.
  • \n

  • Front-end performance testing experience:
  • \n

  • Profiling: Chrome DevTools Performance and Memory panels, Lighthouse, and browser Performance APIs.
  • \n

  • Diagnosis: Identifying long tasks, layout thrashing, and memory leaks.
  • \n

  • Budgets: Setting performance budgets and enforcing them in CI.
  • \n

  • CI/CD experience with Azure DevOps (preferred), Jenkins, or GitHub Actions, along with Git.
  • \n

  • Experience building isolated test environments:
  • \n

  • Linux: Command-line proficiency, shell scripting, processes, networking, and log troubleshooting.
  • \n

  • Docker: Hands-on experience with Docker and Docker Compose.
  • \n

  • AWS: EC2, ECS or EKS, S3, IAM, VPC, and CloudWatch.
  • \n

  • Infrastructure as Code: Terraform, CloudFormation, or CDK.
  • \n

  • Strong reliability practices, including isolated tests, deterministic waits instead of sleeps, controlled retries, and flaky-test troubleshooting.
  • \n

  • Experience with test reporting and traceability tools (Playwright Reports, Allure, Azure Test Plans, or TestRail).
  • \n

  • Clear communication and good documentation skills.
  • \n

\n


Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...