Nataliia Burmei
Nataliia Burmei
Lead Quality Engineer
I am Nat, Lead Quality Engineer who loves travelling, running, quality coffee with a book on the side. Totally unbiased, I love quality.
🎂 MoTaBirthday | May 9, 2023
Open To
Write
Podcasting
Speak
Meet at MoTaCon 2026
A collection of what I snapped on the day of Leading With AI.I turned them into a Gif with a Claude Gif Maker Skill.
24 Jun
Meeting people in person feels different whom we talk online, share ideas and thoughts. It was a great catch up with Diana, Nat, Parveen and Madhuri!!See you all at MotaCon 2026!
24 Jun
This is what happens when every camera is ready to click pictures. Some fun clicks at MoT London with Parveen and Nat where Parveen is trying to understand what's happeing :)
21 Jun
I attended the Leading with AI MoT workshop today.What felt good was the reminder that we're all on a journey. It is an incredibly safe, open, and non-demanding space where people come together to ...
19 Jun
How workflow thinking takes your AI use beyond test cases and bug reports
3 Aug
A panel discussion exploring how AI is really affecting engineering teams today, from tool adoption and team confidence to testing, leadership, and the risk of over-relying on automation.
10 Jul
Stale Documentation
Documentation that was accurate at the time of writing but has since become outdated due to changes in the system, codebase, or process it describes. In testing, stale documentation is a significant risk because teams may test against expectations that no longer reflect actual system behaviour. Documentation stored in tools like Confluence is particularly vulnerable to going stale when it is disconnected from the development workflow and not actively maintained alongside code changes. The problem is often not that documentation was never written, but that there is no mechanism to keep it current.
Self-Serve Testing
An approach to quality in which teams without dedicated quality engineers are equipped with the knowledge, templates, and tooling to make sound testing decisions independently. Rather than requiring a specialist to be present for every significant project or incident, self-serve testing relies on well-designed prompts, charter libraries, and structured guidance that carry quality thinking into conversations and contexts where a quality engineer is not physically present. It is particularly relevant in organisations where quality engineers are significantly outnumbered by delivery teams.
Quality Assistance Model
As originally defined by Atlassian, the Quality Assistance Model promotes the ownership of quality and testing by every engineer on the team, regardless of their role. This allows each engineer to develop code, test it, and release it to production without gatekeeping by a quality team or quality engineer.
Then what do testers do? Under the Quality Assistance Model, you use your testing expertise to guide and educate the team, empowering and influencing them to produce high quality software.
Sharing quality and testing responsibilities across the team spreads the testing workload more evenly and gives testers time to:
Build testing infrastructure
Fill gaps in test automation
Explore new tools and techniques
Monitor production performance
Conduct exploratory testing, ensuring sapient investigation of your product that automated tests cannot provide
Support developers on their team, or even on other teams
Comments
(26)
Quality tooling silos
You expanded so well on my thought with practical examples and actions. Thanks for it, I have a complete picture now.
Wow moments in the software testing essentials course
I postponed STEQ and QTEC for too long. Need to increase priority. Thanks for reminder.
ALL the humans making MoTaCon 2026 happen
Very exciting. Looking forward to it.
Lots of one snack, mix two snacks or sample a full bowl of snacks?
I like pairing up food. I like Gherkin with running honey. Yes, it's delicious, savoury and sweet combo. Feta cheese and sweet fruit (peach, plum) in the oven. Plain yogurt and peanut butter. Can eat them as snacks ;)
In tech, we work in small iterations, why not approach learning the same?
I also think we humans don't always appreciate small learnings, we take it for granted. We are more impressed with big ones. If one does small learning every day (one article, one comment, one MCP command, one chat with PM that landed well) and make one learning continuously for a month, it will be significant progress at the end. It's similar to gym sessions, running trainings. Your brain muscle isn't different. (comment 2/2)
Beyond tasks list. Rethinking the role definition in the organisation
(theroundaboutcafe.com)
01 Dec 25
She Codes Quality: Women in Tech Speak Up | Gary Shannon & Nataliia Burmei | Ep.9
(garytshannon.podbean.com)
21 Aug 25
