Skip to content
Portrait

About

How I got into testing

I started as a tester intern at a small consultancy and worked my way up to a full-time role. As our test cases multiplied, running regression tests before every release took more and more of the team’s time. I proposed Cypress as a way to automate them, and once we adopted it, our regression cycle dropped from two days to half a day.

That was my first experience with test automation, and I’ve been building on it ever since. Today I work as a quality engineer, and I care most about tests that people actually trust: stable, meaningful, and fast enough to give feedback while it still matters.

What I’ve worked with

I’ve tested web applications in insurance, e-commerce, hospitality and HR tech, covering regression, integration, smoke and system testing. My day-to-day tools are Selenium with Java, TestNG and Cucumber (BDD), and Playwright with Node.js, plus Python and SQL when a task needs them. I also test APIs, and on one e-commerce project I verified data directly in AWS (S3, DynamoDB, Step Functions and Lambda). Pipelines run on Jenkins, GitLab CI and TeamCity, and I’ve maintained Jenkins servers and pipelines myself.

On my current insurance project, our regression suite has stayed above 88% stable for the past 15 months.

Certifications

I hold a software testing certificate covering testing methodologies, principles and techniques, and a Test Automation University certificate in automation testing.

How I work

I start by learning your goals and what you want out of the task. Then I lay out the options and the trade-offs so you can choose the path. If I hit a setback, I tell you what the problem is and whether I need anything from you to move forward, rather than going quiet.

Many of my clients are in different time zones, so I respect everyone’s time. I collect the questions and results that need your input and handle them in my own working hours. When our hours overlap, I flag what needs your attention and give a short walkthrough of about five minutes so it’s easy to follow. I send regular status updates in plain language to product owners and managers, and I work in fluent English. I’m happy to work hourly or on a project basis, and I value transparency, respect and clear communication.

Let’s talk

If your tests are slow, flaky or not covering what matters, I’d like to hear about it. You can also find me on LinkedIn.