Apply Now
Location: Phoenix, Arizona (AZ)
Contract Type: C2C
Posted: 1 month ago
Closed Date: 11/17/2025
Skills: Java, JUnit, Maven; BDD with Cucumber/Gherkin.Jenkins, GitHub Actions; GitHub for collaboration.
Visa Type: GreenCard, USC

Role: QA Technical Lead

Location: Phoenix AZ (Only Locals)

Contract to Hire


Only USC and GC


What You’ll Do

• Own the quality platform: Set strategy, architecture, and standards for automation—Java today, with pragmatic evolution to modern UI/API automation where it improves reliability.

• Embed quality early: Drive PR-level tests, contract/API checks, and CI/CD quality gates for rapid, trusted developer feedback.

• Apply AI where it counts: Use AI/LLM-assisted test generation, self-healing locators, flake triage, and test-impact analysis to reduce toil and raise signal.

• Simplify the SDLC: With DevOps, streamline pipelines, test data management, environment provisioning, and release guardrails for faster flow.

• Solve hard problems with architects: Tackle cross-cutting issues (auth, data, performance, flakiness) and retire tech debt with durable solutions.

• Build the right tests: Expand reliable web/UI, API, and integration coverage; harden environments and test data.

• Coach and elevate: Mentor QA engineers, review automation code, and set standards for readability, reliability, and maintainability.

• Measure what matters: Stand up live dashboards (coverage, pass/fail, flakiness, MTTR) to inform decisions and continuously raise the bar.

• Own root cause: Lead deep-dive debugging across test and prod, driving prevention—not just fixes.

 

Your Toolbox (What We Use & Value)

• Languages/Frameworks: Java, JUnit, Maven; BDD with Cucumber/Gherkin.

• Automation: Selenium WebDriver (today); informed experience with Playwright (Java/TypeScript) a plus.

• CI/CD & SCM: Jenkins, GitHub Actions; GitHub for collaboration.

• Observability & Metrics: Grafana (quality and performance dashboards).

• Backend/Platform context: Spring Boot/Spring Security; Oracle DB; FileNet/content systems.

• Scripting: PowerShell or similar for utilities.

• Quality practices: Testing pyramid, risk-based design, code reviews, and environment parity.

 

Where We’re Headed (And Where You’ll Lead)

• GitHub-native CI/CD: Standardize on GitHub pipelines for frequent, automated deployments—define branch strategy, environment promotions, and reusable workflows that make shipping safe by default.

• Reliable testing for high velocity: Build a strategy that scales with cadence—PR checks, contract/API tests, fast UI smoke suites, test-impact analysis, deterministic data & ephemeral envs, parallelization, and rigorous flake control.

• AI-assisted, data-driven quality: Apply LLM-assisted test generation/self-healing and enforce quality gates backed by live dashboards (coverage, flakiness, MTTR, DORA) to boost signal and confidence.

• Framework evolution (tool-agnostic): Evaluate and pilot modern UI/API automation options against clear criteria (reliability, speed, parity, maintainability, ROI) and recommend phased adoption that protects delivery.