1

Playwright Testing Jobs in Fort Lee, NJ (NOW HIRING)

Senior Frontend Engineer

Manhattan, NY · On-site

$100 - $140/hr

Modern testing tools (Vitest, Playwright, Testing Library) * Experience building for unreliable networks -- service workers, optimistic updates, retry logic, queueing, and graceful offline states.

New

... Playwright, Cypress, TestNG, JUnit, or similar. • Experience using AI/ML techniques for defect ... Testing Life Cycle (STLC). • Experience with Agile, Scrum, and DevOps methodologies. • ...

Ensure seamless content delivery, execute robust A/B and multivariate (MVT) testing campaigns and automate end-to-end quality validation using Playwright. [1] Key Responsibilities * AEM Management:

Conversational testing assistants for validation insights Technical Skills * Strong hands-on experience with: * Java, Python, JavaScript * Selenium/Playwright/ Cypress * REST Assured, Postman, Ready ...

Conversational testing assistants for validation insights Technical Skills * Strong handson experience with: * Java, Python, JavaScript * Selenium/Playwright/ Cypress * REST Assured, Postman, Ready ...

Automation Tester

Jersey City, NJ · On-site

$43 - $48/hr

Experience with Mainframe testing including validation of legacy applications and integration testing with distributed systems. Skills: * Playwright. * TypeScript. * Python. * UI Automation. * API ...

Face-to-Face (Onsite in NYC) Job Summary We are looking for an experienced Automation QA Lead with strong expertise in Playwright automation to lead testing efforts for a high-impact project with ...

Selenium or Playwright UI automation * Maven and IntelliJ IDEA * Manual functional testing * ALM or Xray * CI/CD test integration * Test planning and root-cause analysis * Fedwire or financial ...

New

Senior Frontend Engineer

Manhattan, NY · On-site

$175 - $240/hr

Author and maintain automated tests using Playwright, Jest, and React Testing Library. * Integrate with CI/CD pipelines and follow modern development workflows and Git-based source control. * Apply ...

New

Showing results 21-40

Playwright Testing information

What is Playwright testing?

Playwright testing refers to using the Playwright framework to automate and test web applications. Playwright is an open-source tool developed by Microsoft that enables developers to write end-to-end tests for web apps across multiple browsers, including Chromium, Firefox, and WebKit. It allows for reliable browser automation, simulates user interactions, and supports features like taking screenshots, generating test reports, and running tests in parallel. Playwright is popular for its speed, flexibility, and ability to handle modern web app complexities, such as single-page applications and dynamic content.

What are the key skills and qualifications needed to thrive in Playwright testing?

To thrive as a Playwright Testing Specialist, you need a solid understanding of automated web testing, JavaScript/TypeScript programming, and experience with software development life cycles. Familiarity with the Playwright framework, continuous integration tools (like Jenkins or GitHub Actions), and version control systems (such as Git) is typically required. Attention to detail, analytical thinking, and effective communication are crucial soft skills for identifying issues and collaborating with development teams. These competencies ensure reliable test automation, quicker bug detection, and smoother software releases.

What are common challenges faced by professionals using Playwright for end-to-end testing, and how can they be addressed?

One common challenge in Playwright testing is ensuring test stability, as tests can sometimes fail due to dynamic UI changes or network-related issues. To address this, testers often use Playwright's robust waiting mechanisms and selectors that are less likely to break with minor UI updates. Another challenge is maintaining test code as applications evolve; adopting a modular test structure and reusable components can help streamline updates. Collaboration with developers and QA team members is also key, as it ensures that tests align with ongoing changes in the application.

What is the difference between Playwright Testing vs QA Tester?

AspectPlaywright TestingQA Tester
Required SkillsJavaScript/TypeScript, automation scripting, web testingManual testing, test case execution, defect reporting
Work EnvironmentSoftware development teams, automation frameworksQuality assurance teams, testing labs
Industry UsageWeb application development, DevOpsSoftware quality assurance, product validation

Playwright Testing focuses on automated testing of web applications using scripting languages, often integrated into development workflows. QA Testers perform manual testing to identify bugs and ensure quality. While Playwright Testing emphasizes automation and technical skills, QA Testers focus on manual validation. Both roles are essential in software quality assurance but serve different functions within the testing lifecycle.

Is the playwright testing in demand?

Playwright testing is increasingly in demand as organizations adopt automated testing tools to improve software quality. Skills in Playwright, a popular open-source testing framework for web applications, are valued by employers, especially in roles involving front-end testing and continuous integration environments.

What is the salary of a playwright testing?

Playwright testing is a specialized skill within software quality assurance, and salaries for professionals in this area typically range from $70,000 to $120,000 annually, depending on experience, location, and company size. Entry-level roles may start lower, while experienced testers with automation skills can earn higher wages.
Infographic showing various Playwright Testing job openings in Fort Lee, NJ as of August 2026, with employment types broken down into 64% Full Time, and 36% Contract. Highlights an 74% In-person, and 26% Remote job distribution.

Senior Frontend Engineer

landa

Manhattan, NY • On-site

$100 - $140/hr

Other

Posted yesterday

New


Job description

About the Role

We are looking for a Senior Frontend Engineer who wants to own the web surfaces that members and operators interact with every day. This is a senior individual contributor role ideal for someone with 3 to 5+ years of experience who cares deeply about UI quality, performance on real-world devices and networks, and the craft of shipping product.

You will own the frontend architecture across three Next.js applications: our member onboarding flow, our BYOD enrollment experience, and our internal admin surfaces. You will work alongside the Head of Engineering, product, design, and operations to translate company goals into interfaces that work reliably for low-income Americans on Medicaid and Medicare, many of whom rely on us as their primary connection to the internet.

As one of our first in-house senior engineers, you will help shape engineering practices, frontend architecture, and the hiring bar as we grow.

This is a role for someone ready for meaningful scope, autonomy, and impact in a mission-driven company.

What You'll DoBuild and ship
  • Contribute hands‑on across our three Next.js frontends (member onboarding, BYOD enrollment, admin) while establishing long‑term engineering foundations.
  • Own development across our core frontend stack:
  • Next.js (App Router, server components, middleware) and React
  • TypeScript across the application and shared library layer
  • Sanity CMS for content‑driven UI
  • Auth0 for member and operator authentication
  • Build offline‑resilient experiences that hold up on poor or intermittent connectivity — service workers, optimistic updates, retry logic, and graceful degradation are first‑class concerns, not polish at the end.
Design and own
  • Drive the architecture of our shared component library so changes propagate cleanly across all three apps.
  • Set the standard for performance, accessibility (WCAG 2.1 AA), and UX polish — loading states, error handling, and edge cases are part of the definition of done.
  • Author architecture decision records and component guidelines as you go — we believe institutional knowledge belongs in the repo, not in people's heads.
Collaborate and execute
  • Partner with product, design, and operations to turn goals into actionable roadmaps.
  • Work alongside our backend engineers to design the contracts between frontend and API — you will have a voice in how data flows reach the client.
  • Drive UX and engineering decisions that balance speed with the kind of quality our members deserve.
Strategize and improve
  • Set the bar for code review, testing discipline, frontend observability, and release practices as the team grows.
  • Improve developer experience across the frontend codebases — linting, formatting, CI/CD, and tooling are part of the role.
  • Identify opportunities to streamline how we ship features without compromising reliability.
About YouExperience and skills
  • 3–5+ years building and owning production web applications, with a portfolio of work you can walk us through end to end.
  • Deep React and Next.js experience — you have opinions about hooks, server components, routing, middleware, and SSR/ISR patterns, and you can defend them. You know when to reach for a server component and when a client component is the right call.
  • Strong TypeScript fundamentals — types serve the design, not the other way around.
  • Proficiency with:
  • React, Next.js (App Router), and modern React patterns
  • TypeScript across application and shared library code
  • Shared component libraries and monorepo tooling (Turborepo, Nx, pnpm workspaces, or similar)
  • Tailwind, CSS‑in‑JS, or modern CSS architecture patterns
  • Modern testing tools (Vitest, Playwright, Testing Library)
  • Experience building for unreliable networks — service workers, optimistic updates, retry logic, queueing, and graceful offline states.
  • Coding standards as a default, not a phase‑two — opinionated about linting, formatting, PR review culture, and automated testing.
  • Accessibility as a first‑class concern — WCAG 2.1 AA is a launch criterion, not a backlog item.
  • Nice to have: Sanity CMS or headless CMS rendering, Datadog for frontend observability, Auth0 on the frontend, Figma‑to‑code fluency, full‑stack experience (NestJS, Node.js, Next.js API routes), healthcare or regulated‑data environments (HIPAA, SOC 2).
Ways of working
  • Ownership‑first mindset — you treat the surfaces you build as yours. You see it, you own it, you ship it.
  • Ability to balance speed and long‑term quality — ship behind flags, measure cycle time, and don't stall releases out of fear.
  • Radical candor — direct, specific feedback on PRs and design reviews. Kind but never vague.
  • Outcomes over output — you measure success by member impact, not tickets closed.
  • Excellent communicator with both technical and non‑technical teammates.
Traits we love
  • Scrappy, resourceful, and motivated to build quickly.
  • Curious, humble, and eager to learn.
  • Passionate about serving underserved communities and improving healthcare access through technology.
  • Member first, always — every UX decision gets filtered through the question: does this make a member's next interaction with us easier or harder?
#J-18808-Ljbffr