About
Quality engineering with a product mindset
Automation-first quality engineering for distributed, high-scale platforms. I lead test strategy and architecture, embed CI/CD quality gates, and grow QE maturity through mentoring and cross-team enablement. Deep experience with Playwright-heavy E2E, API and contract testing, pipeline design (GitLab, TeamCity, Jenkins), and AWS/Docker-backed test environments.
How I work
Themes that show up across squads, platforms, and delivery models.
- Distributed systems and high-scale platforms — design tests that stay trustworthy as surface area grows.
- Automation-first quality — invest in frameworks, contracts, and data so humans focus on risk, not repetition.
- CI/CD as a feedback product — pipelines, gates, and observability that developers actually trust.
- Mentoring and enablement — documentation, pairing, and thin vertical slices so quality skills spread.
- Contract testing and service virtualisation — keep integrations honest without brittle end-to-end-only safety nets.
Away from the keyboard
A little context beyond roles and pipelines — the sort of balance that keeps the work sustainable.
I reset with strength training and early-morning walks around Brisbane; a clear head makes triaging flakiness and pipeline noise far less taxing.
Travel is mostly long weekends and family trips — coastal drives, good coffee, and planning the next hike instead of the next release train.
Food-wise I lean toward simple home cooking and exploring the city's small restaurants; it's a low-stakes way to be curious, which carries over into how I explore new tools and practices at work.
Fitness
Gym, walking, staying consistent rather than heroic.
Travel
Regional trips, outdoors, travelling light.
Food
Cooking at home and discovering neighbourhood spots.
Why this site exists
This is a live resume and a deliberately product-shaped portfolio: narrative pages for positioning, a QE showcase for how I think about strategy and architecture, and a sample CI dashboard that previews how I like observability to feel — clear status, dense but readable tables, and honest labelling when data is illustrative.
Phase two can wire real integrations (data stores, chat, eval harnesses). Phase one optimises for clarity, credibility, and a visitor experience that mirrors internal quality platforms I have helped build.