Nataliia Burmei

Nataliia Burmei profile image
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
Chapter Lead
Ambassador
Leaders Dinner - London Edition image
Our first Leaders Dinner, the London Edition. Sponsored by the wonderful TestMu AI
4 Oct
Motacon 2026 here I come! image
On the train bright and early travelling across country for Leading with Quality day 🥳
30 Sep
What a welcoming group in the Leaders Dinner (London Edition) image
Thanks to TestMu and Diana for organising this lovely bunch. Thoroughly enjoyed and now looking forward to what comes next in Birmingham!
29 Sep
MoTaCon festival week starts in London with Leaders Dinner image
Was such great start of the week with MotaCon festival week in London meeting few leaders from the community. A lot of great conversations around AI, leadership and quality engineering with de...
28 Sep
Think bigger: what's going on with the AI test case generation? image
How workflow thinking takes your AI use beyond test cases and bug reports
3 Aug
Are your AI efforts good enough? image
10 ideas to question your quality AI work.
10 Jul
Practical impact of AI on today’s engineering management image
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
Roundtable: AI Learnings and Demos image
How do we know AI is doing a good enough job?
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
14 Jun
portfolio
tester-s
01 Dec 25
quality-engineering
role-definition
23 Nov 25
quality-trends
21 Aug 25
women-in-tech
women-in-testing
Subscribe to our newsletter