ZipRecruiter

Log In

1

Software Developer In Test Jobs in Seattle, WA (NOW HIRING)

Hirekeyz Inc

Software Developer in Test (SDET)

Seattle, WA · On-site

$57 - $73.50/hr

Software Developer in Test (SDET) Location: Seattle, WA Job Type: Contract We are seeking a hands-on Test Automation Engineer to drive the next evolution of frontend test coverage across our Micro ...

Stoke Space

Software Developer Engineer in Test

Kent, WA · On-site

$97K - $145K/yr

Software Development Engineer In Test Kent, Washington At Stoke, we believe a thriving space economy will enable a vibrant, sustainable, and equitable future here on Earth. That is why we're building ...

Stoke Space

Software Developer Engineer in Test

Kent, WA

$97K - $145K/yr

We're seeking a Software Development Engineer in Test to evolve our flagship software platform, Boltline, which enables teams to build and validate advanced hardware with complete traceability. As a ...

Concord IT Systems

SDET with Java

Seattle, WA · On-site

Position Title * SDET with Java Position Responsibilities SDET with Java Seattle WA (need candidate ... been a java developer in the past. Primary Skill Core Java Secondary Skill Oracle SQL / PLSQL ...

Damco

SDET with React

Redmond, WA · On-site

$56 - $72.25/hr

SDET With React We have one role the client is asking us to look for, and it is an SDET, with React experience. Here is the Key Job Responsibilities * Lead the design and development of quality ...

Logic20/20

Software Development Engineer in Test

Seattle, WA · On-site

$57 - $73.50/hr

Software Development Engineer In Test Logic20/20 is one of Seattle's fastest growing full service ... senior developer/ senior programmer building C# applications on a.NET platform * Specific ...

Kaav Inc.

SDET with Java

Seattle, WA · On-site

Role: SDET with Java Location ... Seattle, WA Hybrid role from Day 1 Look for someone who has been a java developer in the past.

Omni Inclusive

SDET

Bellevue, WA · On-site

$56.50 - $72.75/hr

Lead SDET Mandatory skills: API Testing, SDET, Selenium * Collaborating with the development and QA teams to understand project requirements and test objectives. * Writing and maintaining automated ...

2Morrow Inc

Software Development Engineer In Test

Kirkland, WA · On-site

$56.75 - $73.25/hr

Software Development Engineer In Test (SDET) Have you found your passion in software design, development, and testing; someone excited to upgrade your technical skills within the constantly changing ...

krg technology inc

SDET

Redmond, WA · On-site

$56 - $72.25/hr

NET, SQL as SDET. - GOOD EXPERIENCE IN Dev/Test DRIVEN DEVELOPMENT AND AGILE PROJECT EXPERIENCE. - Write Solid code using development methodologies Work in a collaborative, team environment ...

Socure Inc

Software Development Engineer in Test

Seattle, WA · On-site

$57 - $73.50/hr

About the Role We are seeking a Senior SDET to support the next evolution of quality engineering by combining automated functional validation, production health monitoring, and AI-driven failure ...

VBeyond

SDET

Seattle, WA · On-site

$57 - $73.50/hr

Job Title: SDET Location: Vancouver, Canada or Seattle, WA (Onsite/Hybrid) Type: Contract Mandate : Python , automation, Java and Selenium, Data background , Kafka , AWS Key Responsibilities * Design ...

next page

Showing results 1-20

All JobsSoftware Developer In Test JobsSoftware Developer In Test Jobs in Seattle, WA

Software Developer In Test information

See Seattle, WA salary details

$13

$62

$84

How much do software developer in test jobs pay per hour?

As of Jul 8, 2026, the average hourly pay for software developer in test in Seattle, WA is $62.36, according to ZipRecruiter salary data. Most workers in this role earn between $54.76 and $70.62 per hour, depending on experience, location, and employer.

Is SDET a good career?

A Software Development Engineer in Test (SDET) is a valuable role that combines software development and testing skills, often involving automation tools like Selenium or JUnit. It offers strong job growth, competitive salaries, and opportunities to work on quality assurance and testing frameworks in various industries. Success in this career typically requires programming knowledge, attention to detail, and continuous learning of testing methodologies.

Will AI take SDET jobs?

AI can automate certain testing tasks performed by Software Developers in Test (SDET), such as test case generation and execution, but it is unlikely to fully replace the role. SDETs will continue to be essential for designing complex test strategies, analyzing results, and maintaining automation frameworks, especially as they require programming skills and critical thinking. AI tools serve as complements that enhance productivity rather than substitutes for skilled testers.

What are the key skills and qualifications needed to thrive as a Software Developer In Test, and why are they important?

To thrive as a Software Developer In Test, you need strong programming skills, knowledge of testing methodologies, and typically a degree in computer science or a related field. Familiarity with automation frameworks (such as Selenium or Cypress), continuous integration tools, and version control systems is crucial. Attention to detail, analytical thinking, and effective communication set outstanding SDETs apart. These competencies ensure the creation of robust, reliable software and foster productive collaboration between development and QA teams.

Is SDET still in demand?

Software Development Engineers in Test (SDETs) are in strong demand due to the increasing emphasis on automated testing, quality assurance, and continuous integration in software development. SDETs with skills in programming, test automation tools, and CI/CD pipelines are particularly sought after across various industries.

What are Software Developers in Test?

Software Developers in Test (SDETs) are professionals who specialize in both software development and quality assurance. They design, develop, and maintain automated testing frameworks and tests to ensure the functionality, reliability, and performance of software products. SDETs work closely with development teams to identify potential issues early in the development cycle and ensure high-quality releases. Their role often involves writing code for automated tests, creating testing tools, and sometimes contributing to the product codebase itself.

What is a software developer in test?

A software developer in test (SDET) is a role that combines software development and quality assurance, focusing on designing, developing, and maintaining automated tests to ensure software quality. SDETs often have programming skills and work with testing tools and frameworks to improve testing efficiency and coverage.

How does a Software Developer in Test typically collaborate with development and QA teams during the software lifecycle?

A Software Developer in Test (SDET) works closely with both development and QA teams throughout the software development lifecycle. They participate in planning and design discussions to understand feature requirements and ensure testability, write and maintain automated test scripts, and review code for quality and test coverage. SDETs often act as a bridge, facilitating communication between developers and testers to identify defects early and improve the efficiency of the testing process. This collaborative approach helps deliver robust and reliable software while fostering a culture of quality across teams.

What is the difference between Software Developer In Test vs QA Engineer?

AspectSoftware Developer In TestQA Engineer
CredentialsProgramming skills, testing frameworks, sometimes certifications like ISTQBTesting certifications, quality assurance training, sometimes programming knowledge
Work EnvironmentCollaborates closely with developers, involved in automation and scriptingFocuses on manual and automated testing, quality process management
Industry UsageCommon in agile, DevOps teams, software development companiesUsed across various industries, including software, manufacturing, and healthcare
Search & Comparison IntentOften compared for automation and development skillsCompared for testing methodologies and quality assurance roles

The main difference is that a Software Developer In Test primarily develops automated tests and collaborates with developers, while a QA Engineer focuses on overall quality assurance, including manual testing and process improvement. Both roles require testing knowledge, but the Developer In Test emphasizes scripting and automation skills.

What are the most commonly searched types of Software Developer In Test jobs in Seattle, WA? The most popular types of Software Developer In Test jobs in Seattle, WA are:
What are popular job titles related to Software Developer In Test jobs in Seattle, WA? For Software Developer In Test jobs in Seattle, WA, the most frequently searched job titles are:
What job categories do people searching Software Developer In Test jobs in Seattle, WA look for? The top searched job categories for Software Developer In Test jobs in Seattle, WA are:
Software Developer In Test jobs near you
Infographic showing various Software Developer In Test job openings in Seattle, WA as of July 2026, with employment types broken down into 81% Full Time, 8% Part Time, 1% Temporary, and 10% Contract. Highlights an 81% Physical, 4% Hybrid, and 15% Remote job distribution, with an average salary of $129,701 per year, or $62.4 per hour.

Software Developer in Test (SDET)

Hirekeyz Inc

Seattle, WA • On-site

$57 - $73.50/hr

Contractor

Posted 12 days ago

Job description

Role:  Software Developer in Test (SDET)

Location:  Seattle, WA

Job Type: Contract

Job Description:

We are seeking a hands-on Test Automation Engineer to drive the next evolution of frontend test coverage across our Micro Frontend (MFE) React ecosystem. You’ll be embedded in a product engineering team, working in close partnership with developers, QEs, and SDETs to deliver scalable, reliable, and developer-owned automated testing aligned with our testing trophy strategy.

This role is part of a strategic shift from a QA-led to a developer-owned testing model, emphasizing integration-first, user-centric, and automation-first practices.

Key Responsibilities

Build and maintain Playwright-based E2E and smoke tests for critical guest journeys (e.g., browse, add-to-bag, checkout).

Develop robust integration tests using React Testing Library, Jest, and our internal @lululemon/mwa-testing harness.

Drive test colocation and naming conventions to support auditability, execution traceability, and analytics.

Use Mock Service Worker (MSW) and shared data fakers for API mocking and dynamic data setup.

Ensure tests are aligned with TestRail test cases, partnering with QEs to translate manual test intent into code.

Contribute to test strategy discussions: define when and how to use unit, component, integration, or E2E tests.

Help sunset low-value Cypress tests and replace them with performant, reliable tests.

Integrate tests into GitLab CI/CD, including trace/video capture and visual regression workflows.

Collaborate with developers and QE to increase test coverage, reduce test flakiness, and shift left testing practices.

Must-Have Skills:

3–5 years frontend testing or development experience

Strong proficiency with React, TypeScript, and MFE architecture

Experience with Cypress or Playwright for E2E testing in CI/CD environments

Solid understanding of React Testing Library, Jest, and mocking frameworks like MSW

GitLab CI/CD experience, especially in configuring test jobs and managing test artifacts

Familiarity with AWS services relevant to frontend pipelines or test artifact storage (e.g., S3, CloudFront)

Working knowledge of TestRail or other test case management platforms

Nice-to-Have:

Experience with @testing-library/react-hooks, Storybook, or Visual Regression Testing

Prior exposure to Cypress, with the ability to help decommission and port to Playwright

Awareness of observability practices (e.g., logging, monitoring, flakiness tracking)

Comfort working in agile product teams with shared code ownership and DevOps practices

Success Metrics

90%+ integration coverage on critical flows

<5 minute integration suite runtime

<1% flakiness on E2E Playwright suite

50%+ reduction in manual story testing time