Gary Hawkes | Comments
ACCELQ builds tests in plain English, no code, cuts maintenance 70%. Book a demo to see it across your entire stack!
Yesterday I decided to sort out my collections. I'd started with a collection of "Influential Content" and it had become too big 😂. So I've no broken them all down into smaller collections focused on reuse.
Truly fascinating conversation, thank you both for sharing!
Thank you so much for the mention! That really means a lot, it can't be understated how much me sharing with everyone helps me package up my learning and process any anxieties I've had around them. If you and the community take value from it, its a beautiful bonus. ❤️
A lovely heartwarming story. Thank you for sharing! 🫶
Thanks Ujjwal! 🙏
Thanks everyone, really appreciate your support and being a part of this journey 🙏
This maybe 2022, but I found this really useful for today. Our team is getting smaller, we need to work differently and get more testing done earlier and from developers. Thanks Clare 🙏
Very useful talk as we will be in the coming months I think starting to be testing AI enabled chat features in our products. Thanks for doing it!
Is there any chance you can share the presentation as I can't see the slides on the video. Obviously, happy if you'd want remove the martial arts slides 😁
Thanks so much for this call for insights. I had a skim read of the capabilities model and then compared it to our AI policy document that was written in 2024 and there is a massive gulf. So this is on my list to fix as a result of watch this brilliant discussion. 🙏
Thanks for sharing this Megan. I don't often spend time reading around performance testing as I've often viewed it as a speciality. e.g. "We don't have a performance tester on our team" distorts my perception.
So this is the first article I've read that has explained this needs to change. It sounds like a great talk.
Good question Pedro! Well in our interview process, we have a 2 stage interview process. The first interview is a no pressure chat to find out about them as a person, how they like to work, what they enjoy and what they don't enjoy. Giving them the freedom to ask questions of us in the same style.
That interview to be honest is the most powerful as I can imagine how they would fit in the team, who they'd work well with and where they could make their biggest positive impact to us and to themselves.
The 2nd interview is about skills and the role they need to fill. If we need to evaluate their skills, no timed or live tests, we give them an exercise to do in their own time and access to the team to ask questions. They don't have to complete it, but be able to talk about their experience.
The first interview and their style of questioning of the team really gives an insight into their character. Hope that helps 🙏
Gary Hawkes
Head of Engineering
He/Him
Software QA Lead and tester who loves to see people grow, processes continuously improve and help organisations understand and support Quality Engineering. Recently promoted to Head of Engineering (Jul 2026).
Open To
Write
Mentor
Podcasting
CV Reviews