Lead SDET & Architect for hire
Strategic Quality Engineering. Solving expensive problems before they reach production.
Why Most Test Automation Fails
Teams spend months building test suites that break every release. Tests flake. Pipelines slow to a crawl. Developers stop trusting results and begin skipping runs. Within 18 months, most automation projects collect dust.
The problem is rarely the tool. It is the architecture. Tests written without clear ownership, without CI integration, and without a plan for maintenance become technical debt faster than the code they cover. I have seen teams with 200 tests that take 6 hours to run and fail 40% of the time. That is not coverage. That is noise.
I fix this by building systems that last. Every test gets a clear owner. Every failure triggers an alert, not a shrug. And every pipeline completes fast enough to block bad code before it ships.
The cost of bad automation is invisible until it is not. A single production bug in a payment flow can cost more than a full year of test engineering. I build tests that catch those bugs before your users do.
How Engagements Work
Step 1: Audit Your Current State
We map your existing tests, pipelines, and team structure. I find the flaky tests, the slow suites, and the gaps in coverage. You get a written report with priorities ranked by risk.
Step 2: Design the Architecture
We pick the right stack for your team size and tech landscape. Playwright for web. K6 for performance. GitHub Actions for CI. Every choice ties back to speed and maintainability.
Step 3: Build and Integrate
I write the foundation tests, set up the pipelines, and wire everything into your workflow. Your team reviews every pull request so they learn the patterns as we build.
Step 4: Handoff and Scale
You get documentation, training sessions, and a clear roadmap. Most teams run their own tests within 30 days. I stay on retainer for code reviews and tough bugs.
Want to bring me in-house?
Download my resume to learn more about my experience, skills, and what I can bring to your engineering team.
Your email stays private. No spam, ever.
Automation Foundation
From $4,500
One-time setup. Architecture + Critical Path tests. We hand over a production-ready system your team can extend.
- Playwright & TypeScript Architecture
- CI/CD Pipeline Integration
- Performance Testing Baseline (K6)
- Test Data Management Strategy
- Visual Regression Setup
- Team Training & Documentation
- Flaky Test Resolution
- Code Quality & Linting Rules
Fractional QA Leadership
From $8,000 / mo
Complete 'Department as a Service'. Includes Foundation setup. Dedicated Lead SDET (+ team capacity) to scale coverage.
- QA strategy & Roadmap Planning
- Hiring & Team Building
- Vendor & Tooling Selection
- Agentic Workflow Integration
- Weekly Code Reviews & Mentorship
- Release Management Optimization
- OKR & KPI Definition
- Incident Post-Mortem Analysis
Results From Real Teams
I have led automation programs for Apple, CooperVision, Williams-Sonoma, and Fortune 500 government contractors. At CooperVision, we went from zero automation to 300+ stable tests in under a year. At Apple, I maintained test infrastructure used by millions of users. Every project follows the same pattern: audit, build, handoff, scale.
At Williams-Sonoma, I built e-commerce test automation covering payment flows, inventory checks, and checkout paths. At a Fortune 500 contractor, I brought government-grade QA processes to a team shipping daily. Each engagement starts with the same question: what is the most expensive bug you ship today, and how do we catch it tomorrow?
Read the full case studies on the work page to see specific outcomes, tech stacks, and timelines.
Common Questions
How long does a typical automation foundation take?
Most foundation projects finish in 2 to 4 weeks. Complex enterprise environments with legacy systems may take 6 weeks. The goal is always the same: a working pipeline with stable tests on day one.
Do you work with teams that use Selenium or Cypress?
Yes. I have migrated teams from Selenium to Playwright and from Cypress to TypeScript-based frameworks. The process preserves your existing coverage while replacing brittle tests with stable ones.
What if we already have tests but they are flaky?
That is the most common starting point. I run a flake audit to find the root causes: timing issues, selector fragility, environment drift, or missing test data. Then we fix the architecture so flakes stop coming back.
Do you offer ongoing support after the foundation is built?
The fractional QA leadership package includes ongoing support. I act as your Lead SDET, running weekly code reviews, mentoring juniors, and keeping your roadmap current. Most clients stay for 6 to 12 months.
What industries do you specialize in?
I have deep experience in health tech, e-commerce, government, and consumer software. The patterns are universal, but the compliance and scale requirements vary. I adapt the architecture to your domain.
How do we get started?
Fill out the contact form below. I reply within 24 hours with a short questionnaire about your team size, tech stack, and goals. If we are a fit, we schedule a 30-minute call to map the project.
If not sure, you can book an intro call to learn more about my services and get a free consultation to discuss your project.
Referral program
Know someone who needs QA Leadership? Refer them and get 10% commission on the first engagement.