Quality Engineer, Test Automation Engineer, QA Automation, and SDET-aligned roles.
Professional StoryFrom functional QA to AI-assisted quality engineering.I combine hands-on testing, automation, system analysis, and AI-assisted engineering to become productive quickly in unfamiliar codebases and domains without compromising validation, traceability, or delivery evidence.Read the full career storyCollapse story
Consulting delivery across research, banking, retail customer experience, and energy.
Contributed roughly 37% of automated system test coverage at Judo Bank.
Sole QA ownership across journeys, routing, integrations, records, and case lifecycles.
I began my testing career with Planit in 2022, building foundations in functional testing, requirements analysis, defect management, SQL-based validation, and end-to-end business process testing. Consulting engagements then took me across healthcare research, banking and financial services, retail customer experience, Salesforce CRM, and energy and utilities.
At Judo Bank, I moved from system and integration testing into API-first automation. I worked across onboarding, payments, term deposits, statements, account lifecycles, ERP integrations, mobile applications, APIs, data stores, and connected platforms. Using Python, Behave, PyTest, reusable endpoint abstractions, and GitHub Actions, I personally automated 186 of 500 planned system tests and later 42 of 200 planned end-to-end tests.
That work also developed my delivery and leadership skills. I mentored and onboarded 3-4 offshore testers into the automation framework, helping with test creation, debugging, and execution. My automation contribution and delivery throughput were recognised with Planit's Super Nova Award.
At MECCA, I acted as the sole QA resource for a migration to Salesforce Embedded Messaging. I owned planning, design, execution, regression, evidence, and reporting, and authored 213 test cases across customer journeys, routing, AU/NZ queues, Salesforce records, integrations, and case lifecycles. I also built a Playwright and TypeScript framework to explore repeatable chat-workflow automation.
My current AEMO engagement brings that experience into energy and utilities. I perform functional, integration, system, exploratory, API, data, and UI testing across enterprise applications while contributing to C#/.NET automation and framework modernisation. In one unfamiliar validation-service domain, I used scripting and AI-assisted analysis to map files, processing rules, outputs, and database relationships, then validated the findings through controlled tests and Oracle data traceability.
AI assistance is part of how I engineer, not a substitute for engineering judgement. I use coding agents and structured context to understand existing codebases, identify framework patterns, find where changes belong, draft queries and test assets, and iterate quickly. I validate suggestions through read-only investigation where appropriate, controlled changes, test execution, evidence review, and defect analysis.
I am strongest when the system or domain is unfamiliar. I do not position myself as a syntax-memorisation specialist or a deep expert in every language I touch. I bring test thinking, rapid system comprehension, practical automation, and the judgement to use modern tools safely across Python, C#/.NET, Playwright, TypeScript, Selenium, Cypress, Postman/Newman, BDD tooling, and CI pipelines.
Outside client work, I maintain public automation frameworks and a private Ubuntu homelab. These projects let me keep developing in browser and API automation, AI-assisted tooling, CI, service virtualisation, dashboards, Docker-based operations, observability, and recovery planning.
