About Flo
I have tested software since 2008 and written requirements since 2013. Today I also build the automation and AI systems I test.
A bit about me
I have spent 18 years making sure software does what the business needs. I started as a tester, became a test lead and test manager, and spent years as a business analyst writing the requirements other people build from.
I like messy problems. Give me scattered notes, unclear requirements and decisions nobody wrote down, and I will turn them into something people can follow and check. I don't take a requirement as given. I ask whether it can be true and what is missing, because a wrong assumption costs far less to fix on paper than in production.
AI is the part of my work I enjoy most right now. I spend a lot of my own time with it, building with Claude Code, trying new agents and tools, and finding out where they help and where they fail. At OIC Architects, the Sydney practice I co-founded, the systems I build run real work every day, and I test them the way I would test anything a business relies on.
I write up what I learn in my Thoughts and on LinkedIn, because the field changes fast and practical notes help more people when they are shared. Colleagues get the same. When I find a faster way to do something, I show the team how to do it too.
I grew up in Germany and have called Sydney home since 2018.
How I work
The same four steps, whether the work is a test strategy, a requirements change or an AI automation.
Understand
I start with the people who do the work and the rules they work under, and I write down what correct looks like before anything is built.
Improve
Then I look for the slow and error-prone steps, and decide which ones a process change, an automation or an AI step should take over.
Deliver
I build it with the team in small steps people can check, using tools such as Power Automate, Copilot Studio, Claude Code and Playwright.
Verify
I test it against that definition of correct before the team relies on it, and I keep the evidence.
Qualifications
- Bachelor of Business AdministrationUniversity of Applied Sciences Erfurt, 2009
- ISTQB Certified TesterInternational Software Testing Qualifications Board
- ISTQB Advanced Level Test ManagerInternational Software Testing Qualifications Board
Questions people ask
What kinds of roles and projects do you work on?
I work across quality engineering, software testing, test automation, business analysis and AI automation. Depending on the project, that might mean clarifying requirements, improving testing, building automation or helping a team deliver a solution. The common thread is understanding what needs to be done and making sure the outcome works. I'm based in Sydney and open to contract opportunities across Australia, including remote work where suitable.
Which technologies do you work with?
My work includes SQL, Python, Playwright and Postman for software testing and technical problem-solving, alongside Claude Code, GitHub Copilot, Microsoft Power Automate and Copilot Studio for AI-assisted engineering and workflow automation. I choose tools based on the problem, the environment they'll run in and how reliably the result can be maintained and tested.
How do you approach testing AI systems and automations?
I start by defining what a correct outcome looks like, then deliberately look for where the solution might fail. I use techniques such as red teaming, pre-mortems and failure-mode analysis to challenge assumptions, uncover edge cases and identify risks before they become problems. I validate results against business rules and build in guardrails, logging and human oversight where reliability matters.
How do you approach business analysis?
I start by understanding the business problem and how people actually do the work. I challenge assumptions, clarify requirements and identify gaps before they become expensive problems later. I use structured requirements, acceptance criteria and process mapping to help teams agree on what needs to be delivered and how we'll know it works.
Have you led teams or mentored colleagues?
Yes. I've worked as a test lead and test manager, supported colleagues and helped teams improve their ways of working. I believe useful knowledge should be shared. When I develop a better process, automation or testing approach, I document what I've learned and help others use it rather than keeping it to myself.
Every role, with what I did in it, is in my CV.