Our Breakpoint 2026 speaker spotlight series continues with Keith Klain, Director of Quality Engineering at KPMG. Keith brings something the testing industry doesn't get enough of these days: 25+ years of pattern recognition. He's seen which "next big things" actually delivered, which ones quietly disappeared, and what it costs to bet on the wrong one.
Most of his career has been inside the world's largest financial institutions, where the cost of a bad release isn't just downtime — it's regulatory exposure. He writes about the industry at qualityremarks.com, tracking the people and ideas actually shaping how testing gets done versus how vendors say it should. At Breakpoint 2026, he's presenting "The Death of Test Engineering", a session that, in his own words, comes from "20+ years of pent-up frustration."
After 25 years leading QE at major financial institutions, what does the work actually look like, and what's kept it interesting?
The work looks exactly the same as anywhere else that builds and deploys software, but I think one of the primary differences is the operational structure and oversight that comes with enterprise technology. When you get into certain types of financial services organisations, the context is just different than other industries because the exposure to regulatory and market moving consequences are higher.
As well, there is a corporate structure you have to deal with when despite not being able to conduct business without technology, it's not your primary product. So a lot of times you have to navigate business structures and operations that are counterintuitive to running a tech team, but are vital to building and supporting the business.
It can be very stressful at times, but I think that's one of the things that keeps it interesting and feeling you've very connected to global events, politics, etc. keep it fresh and current and I'd probably be bored working in any other industry!
Can you give us a sneak peek into your Breakpoint session? What's the one thing you want everyone to walk away with?
Aside from unloading on the test automation industrial complex for 20+ years of pent up frustration, my talk is a challenge to one of the biggest assumptions in our industry: that test automation means more/better testing and higher quality. I'll also lay out how the old model of test engineering built on script production, regression sprawl, and maintenance-heavy automation has lost relevance in an AI-driven world.
Hopefully you'll walk away with some ideas on how we got here and a clear message: don't build your future around writing more tests, build it around understanding risk, failure, and system behaviour. The people who stay relevant won't be the ones producing the most test scripts. They'll be the ones who can ask better questions, model what matters, detect problems earlier, and explain why systems fail.
What's a belief you had about AI in testing a year ago that you've since changed your mind on?
What has changed for me is the full realization of just how powerful the cognitive surrender to AI has been from people I used to respect in this business. I think I underestimated the power of anthropomorphism with GenAI and that it's pretty much treated like magic. It has created a mania and FOMO that is nothing like I've seen before, so my belief that systems thinking, risk management, and oversight could counteract that has been completely changed.
What hasn't changed it that most of my pessimistic views about AI in testing have pretty much been validated, specifically how bad actors (consultants and vendors) in our industry are cynically just hyping AI as some evolutionary next step for quality. If you've been around this business long enough, you see the familiar patterns from people who clearly don't understand testing, don't care about testers, or have to live with the consequences of their quality decisions.
To be clear, a tester's JOB is to be skeptical about things in order to get an objective view about progress, quality, and most importantly risk. So it's getting pretty boring listening to the usual suspects drone on about how questioning the value of AI in testing and looking at risk is just being negative or acting like some kind of Luddite.
What are some of the best tech-focused newsletters, blogs, or podcasts you'd recommend?
I'm a pretty heavy consumer of everything testing industry related and am very active on LinkedIn and industry events, but my go to sources for keeping up on the industry is Software Testing Weekly, the Software Testing Round Up by Alan Richardson, the Engineering Quality podcast, and some Google/Reddit alerts I've set up.
To keep up with AI and the endless stream of news stories, I keep my inputs limited to trusted sources to focus my attention, and those are: Dagmar Monett, Emily M. Bender, Timnit Gebru, Charity Majors, Karen Hao, Fiona Charles, Michael Bolton and Maaike Brinkhof.
I've also outlined most of who and what I listen to on a regular basis that has influenced my thinking about my work on my Resources page, and more specifically for AI here.
Outside of the tech world, what's a hobby or passion you keep coming back to?
Well, I spend a lot of time at work so I take every chance I get to hang out with my family and travel. I hiked the South Downs in Surrey last year by myself and it was amazing and I'm hoping to do another one this year in Cornwall.
Keith is one of several seasoned voices bringing hard-earned perspective to Breakpoint 2026. He'll be joined by Jason Huggins (Founder, Selenium and Vibium), Marc Boroditsky (Technology Leader, Nebius), Avinash Ahuja (Manager Solution Architect, NVIDIA), Lena Nyström (CEO, Test Scouts AB), Brittany Stewart (Senior QA Specialist, QualityWorks Consulting Group), Julio de Lima (QA Manager, Capco), Pramod Yadav (Test and Automation Specialist, Power Tester), and more. It's a lineup built for practitioners who want signal over noise. Register here to catch his session.
