Salary range is:

$119,030.52 - $147,000.00

This position is bonus and/or commission eligible.

CCC Intelligent Solutions Inc. (CCC) is a leading cloud platform for the multi-trillion-dollar insurance economy, creating intelligent experiences for insurers, repairers, automakers, part suppliers, and more. At CCC, we’re making life just work by empowering more than 35,000 businesses with industry-leading technology to get drivers back on the road and to health quickly and seamlessly. We’re pushing boundaries with innovative AI solutions that simplify and enhance the claims and repair journey. Through purposeful innovation and the strength of its connections, CCC technologies empower the people and industry relied upon to keep lives moving forward when it matters most. Learn more about CCC at www.cccis.com.

 

The Role

We are seeking a hands-on Lead SDET with strong Developer Experience (DevEx) capabilities to directly own our automated testing frameworks and quality signals across a multi-repository environment with a mix of legacy and modern applications and integration interfaces.

You will own:
• our Playwright (TypeScript) E2E framework for UI and end-to-end flows
• our API testing strategy and enablement to reduce over-reliance on UI E2E
• the enablement patterns (templates, standards, documentation) that make automated testing easy to adopt across many repos

This is a testing-focused DevEx role (not SRE/DevOps). You’ll partner with internal DevOps/SRE for environment needs and pipeline integration points, and we use Azure Application Insights for observability and triage.

Environment
• Many repositories (UI, APIs, integration/interface services), mixed maturity (legacy + new)
• Tech: .NET Core / C#, Angular, TypeScript
• CI/CD: Azure DevOps Pipelines (YAML)
• Observability: Azure Application Insights
• Database: MS SQL Server 2019 (coordinate with DBA partners as needed)

What You’ll Own (Primary Outcomes)
• A scalable, maintainable automation ecosystem:
• Playwright E2E (TypeScript) with shared packages/templates
• API testing patterns/frameworks (language/tooling appropriate to stack)
• Reduced manual regression, reduced flaky tests, fewer “false red” CI runs, and faster triage.
• A clear, pragmatic test strategy that keeps E2E focused on high-value journeys and pushes appropriate coverage into lower-level tests.
• Documentation, onboarding materials, and support practices that make it easy for engineers and QA to contribute tests consistently.

 

Key Responsibilities:

• Hands-On Playwright Test Development + Framework Ownership
  • Write and maintain Playwright automation tests (TypeScript) for critical user journeys and end-to-end workflows.
  • Build and maintain the Playwright framework and supporting code, including:
  • shared fixtures, configuration, and environment handling (per-env URLs, auth, feature flags where applicable)
  • reusable TypeScript helper classes/utilities (e.g., API clients, data builders, page/component helpers)
  • shared resources (test data files, seeds, file assets, mocks/stubs where appropriate)
  • standards for test organization (structure, naming, tagging) and maintainable patterns
  • Provide a “golden path” starter kit usable across repos:
  • templates, examples, contribution guidelines, code review checklist

• API Testing Enablement (Shift Coverage Down the Stack)
  • Define and enable practical API-level testing patterns to reduce E2E scope and improve signal:
  • service-level smoke tests and regression suites where they provide high value
  • guidance on integration tests vs full end-to-end tests
  • test data and environment configuration standards for repeatable runs
  • Provide reusable libraries/helpers for common API testing needs (auth, correlation IDs, fixtures).

• Flaky Test Reduction & Quality Signal Health
  • Establish and operate a measurable flake reduction program:
    • define flake rate; track and publish trends, top offenders, and root causes
    • implement preventive patterns (test isolation, deterministic waits, stable selectors)

• CI Enablement (Partner with DevOps; Focus on Signal, Not Ownership of the Platform)
  • Partner with DevOps to ensure Playwright and API test execution is fast, reliable, and well-reported in Azure DevOps:
    • define required pipeline stages/checks and quality gates for PR vs nightly runs
    • standardize artifacts (HTML reports, screenshots, videos, traces) and failure ergonomics
    • recommend