Quality & Testing Leader

I build and lead QA teams that change how organizations think about quality through automation frameworks, practical processes, and growing people who understand that quality isn't just finding bugs.

Over 15 years in QA, working across manual testing, automation, and building QA functions from scratch. Joining teams early to shape how they test as the product grows.

What I Do

I work in three phases. First is learning the product, the team, how features get tested, and where gaps exist. Second is stabilizing by mapping risk and making sure critical paths have coverage so you're not hoping everything works. Third is enabling through better feedback loops, clearer acceptance criteria, and QA practices that help teams move faster.

How I Approach Testing

Quality isn't just a QA responsibility. You can't test it in at the end. Everyone plays a part from the start. My job is enabling the team by asking "how can this work?" and "what are the risks?" Becoming an expert in the product and how it's used, then focusing testing where the risk actually lives because not everything needs the same attention.

Getting involved early matters. Pairing with developers during development means faster feedback and fewer surprises later. Problems caught early are cheaper and easier to fix.

I use automation for regression safety and fast CI/CD feedback. But I also do exploratory testing because that's where you find the problems you didn't think to test for. You need both.

Simple metrics and clear reporting help teams make decisions. I don't believe in vanity metrics or tracking things for the sake of it. Good reporting shows what's actually happening with quality so releasing becomes less guesswork and communication gets easier.

Experience

Built QA functions from scratch and grown teams from manual testing to automation. Worked on mainframe systems, web applications, and API services in regulated industries where quality standards matter.

Joined organizations where QA involvement was minimal and rebuilt quality foundations. That meant owning quality across the product, setting up lightweight processes, getting test coverage in place, and building automation that actually helped. All while working directly with engineering and product.

Technical Expertise

I work across UI automation, API testing, framework design, and performance testing. Here are the technologies I use:

Test Automation

  • Playwright

    E2E Testing Framework

    Playwright

    I use Playwright for cross-browser end-to-end testing, taking advantage of its automatic waiting and parallel execution to keep test suites fast and reliable.

  • Cypress

    Frontend Testing

    Cypress

    I build Cypress tests for complex UI interactions, using its real-time reloading and debugging capabilities to quickly identify and fix issues during test development.

  • Python

    Automation Language

    Python

    I write Python for API testing, test frameworks, and data analysis. I rely on pytest for test structure and requests for API interactions, and use it to build custom test utilities that teams actually want to use.

  • Postman

    API Testing

    Postman

    I use Postman for exploratory API testing and creating collections that development teams can use for manual testing. When tests need to run in CI/CD, I convert them to code-based solutions.

Performance Testing

  • Apache JMeter

    Load Testing

    Apache JMeter

    I design JMeter scripts to simulate realistic load patterns and identify performance bottlenecks. I focus on creating reusable test plans that can be easily adjusted as system architecture evolves.

  • BlazeMeter

    Cloud Performance Testing

    BlazeMeter

    I use BlazeMeter to run large-scale load tests from multiple geographic locations, getting real-time metrics on how systems perform under production-like traffic conditions.

Infrastructure & DevOps

  • Docker

    Containerization

    Docker

    I use Docker to package test environments so they run identically on developer machines, CI/CD pipelines, and cloud infrastructure. This eliminates 'works on my machine' problems.

CI/CD & Version Control

  • CircleCI

    Continuous Integration

    CircleCI

    I configure CircleCI pipelines to run tests on every commit, using parallel execution and caching to keep feedback fast. Tests run automatically, and failures block deployment.

  • Git

    Version Control

    Git

    I manage test code in Git alongside application code, using branches for test development and pull requests for code review. This keeps testing integrated with the development workflow.

  • VS Code

    Code Editor

    VS Code

    I write test code in VS Code, using extensions for Python, JavaScript, and test frameworks. The integrated debugger makes it easy to step through test failures and understand what went wrong.

Certifications

  • ISTQB Foundation Level
  • IBM Back-End Development Professional Certificate
  • Meta Back-End Developer Specialist

Philosophy

I build testing tools I'd actually want to use. Privacy first because your test data shouldn't leave your machine. Maintainable because you'll be updating it in six months. Practical because if it doesn't solve a real problem, why build it?

Example: every pairwise testing tool I found cost hundreds per month, sent data to third parties, or had terrible UX. So I built the N-wise Test Generator. Free, runs in your browser, designed around how I actually work.

Let's Connect

Feel free to reach out via email, check out my work on GitHub, or connect with me on LinkedIn.