Rosie Sherry
CEO & Founder at Ministry of Testing
She/Her
I am Open to Write, Teach, Speak, Mentor, CV Reviews, Podcasting, Meet at MoTaCon 2026
I've been working in the software testing and quality engineering space since the year 2000 whilst also combining it with my love for education and community. It turns out quality, community and education go nicely hand in hand.
🎓 MoT-STEC qualified
Achievements
Certificates
Awarded for:
Passing the exam with a score of 100%
Awarded for:
Achieving one or more Community Stars in five or more unique months
Activity
earned:
Member joined MoT London chapter
earned:
Member joined MoT Brighton chapter
awarded Myriam Peerbaccus for:
Thanks for reporting a bad link.
earned:
Member joined MoT London chapter
earned:
Changing the conversation changes the future
Contributions
In the MoTaverse, we believe in the collective knowledge of the community and are working on unlocking it to enable micro learning opportunities.How it works:
we surface insights and we do magic b...
Every question you ask during testing is the seed of the next one.
In TWiQ today, Aj raised the idea of self-service infrastructure and it got me thinking about how that is related to platform engineering. Something I realise I don't know enough about, but a recen...
Loop engineering is moving from prompting agents and towards designing the systems that prompt.And for what it's worth, no, I am not looping yet, I'm still happy prompting away.However, Addyo Osma...
Could borrowing a concept from cognitive science change the way we think about quality engineering?
Seventeen years in quality, rejections, then two offers. We did that.
We'll be in London next week and we hope you can join us.
👉 First up. MoT London Chapter on Thursday 18th. Over 80 people are registered. Save your place today, it's open to all.
🎟️ Leading With AI...
It passed last week. It passed last month. But the world it was built for no longer exists.
A software engineering approach where, instead of directly prompting an AI coding agent turn by turn, a developer designs an automated system (the loop) that discovers work, delegates tasks to agents, checks results, persists state, and decides the next action on a schedule or until a goal condition is met.So what? The leverage point shifts from writing good prompts to designing systems that do the prompting, which changes the nature of the engineer's role from operator to architect.Example: A morning automation that reads yesterday's CI failures and open issues, spawns sub-agents to draft fixes, runs a verifier against the results, opens a PR, and updates the issue tracker, all without the engineer typing a single prompt.Related term: Pilot Agent.
Most teams think they've handled dates. Most teams are wrong.
What if the tools we use to stay on top of things are quietly making us worse at our jobs?
And hot take: Don't let AI take notes for you
