I came into QA through computer science engineering, and I fell in love with the part of software most people rush past: figuring out how things actually break. My first role was a QA internship on a multi-tenant healthcare SaaS platform, where I wrote 140 test cases and found 91 defects before release. That taught me early that in regulated, high-trust systems, quality isn't optional.
At Kode Creators I moved into an SDET role, building a Selenium and Playwright framework from scratch. It cut regression time by 65% and automated 80% of critical flows. I also got involved before development started, in sprint planning and requirements review, where we caught 25+ gaps before anyone wrote code.
What makes me different is that I cross the line between tester and builder. I've built a payment authorization API with transaction auditing, a fraud-detection pipeline, and CI/CD with monitoring on AWS, so I understand how systems fail from the inside. That's why I'm drawn to security-focused QA. Testing IAM and auditing is about thinking like someone trying to break trust, and I enjoy that. I also finished my MSc in Computing Science in Dublin, so I'm used to learning new tools quickly, and I'm keen to go deep on Ignition.
No employment history.
No education history.