Great technology is built by curious minds. Here, we prioritise people first, fuelling a culture where asking ‘why’ is just as important as knowing ‘how.’ Dive into our employer blog to find out what makes Monteers tick – both in and outside of the office.
Next up: Marlene Heinzle, our Senior QA Engineer in Copenhagen, with an academic background in human factors engineering and neuroscience. At Monta, Marlene ensures the reliability of our eMSP and driver product features by designing robust test strategies, validating integrations and proactively preventing issues before they impact customers.
Take us behind the scenes. What challenge are you working on right now that really excites you?”
Right now, I’m expanding Monta’s automated UI testing and doubling down on QA enablement for developers. My end goal is to make running automated end-to-end tests in the product as easy as clicking a button – which triggers the test. For example, if a developer makes a change which affects payments, they can click to run a test on the ‘pay charge flow’ – which triggers a workflow to execute the relevant UI tests and produce a results report back to the developer.
By embedding this into the developer workflow, it means that testing occurs much earlier – and becomes part of how we build – rather than something that is bolted on afterwards. As a result, we can catch issues earlier and ship products with high confidence, as the foundation of trust in our deliveries is built early on.
After this, my next step is to build an AI layer into these workflows, to identify which tests should be run based on code changes, and trigger those automatically.
When do you feel most supported by your team?
Definitely during large-scale feature deliveries, when we all need to roll-up our sleeves and shift into ‘war-room’ mode. That’s when we move really fast together. It’s deep testing and tight iterations with the engineers, and a shared laser focus on user outcomes.
Delivering entirely new, complex features also means surfacing complex problems, and I enjoy bringing structure and order to those messy parts. Being really structured and making a full testing plan exposes where expected behavior isn’t fully documented yet.Making the product testable, executing on it, and watching confidence increase with every passing test – that’s satisfying.
QA is a craft of deliberately trying to break things to make them stronger. I need to understand how systems behave under stress, where assumptions hide, and how real users might trip in unexpected ways.
QA isn’t just verifying that it does what it’s supposed to do – it’s verifying that it doesn’t do what it’s not supposed to do. It’s the bottom of the iceberg. And when there is a failure, ensuring it fails gracefully – showing error messages, guiding the user, preventing them from getting stuck.
Finding those business risks, edge cases, exposing fragile seams, smoothing out the user journey – that’s really satisfying. As I said before, it increases trust in the product and makes everything downstream more robust.
What fuels you when the laptop closes?
It’s hibernation season right now, so my evenings often involve my armchair, a book, and the ever-reliable “Fireplace for your home” on Netflix. Being Austrian-born and raised, I’m always pulled toward the mountains. I don’t know how I ended up in the flattest country there is.
I’m already counting down to heading home this winter – getting back on the ski slopes. In the mountains is where I feel most in touch with, and in awe of, nature because you feel so small in a good way. Beyond that, it’s quality time with my dear ones – oh and I also have a wedding to plan!
What are you most excited to build with your team over the next six months?
I’m excited to build driver experiences that feel clear and empowering. That means more visibility and control for our partners, smoother journeys for drivers, and the kind of polish that makes people sit back and think: “Huh, this was really easy,” or “This was smooth,” or even delightful – those good moments in the app and product.
Internally, I’m focused on refining our development workflow so quality checks happen naturally rather than as separate steps. That means tightening test coverage where it matters most, making automated tests a built-in step in every merge, and reducing manual overhead needed for reliable releases. These are small habits that help us move faster and build on a solid foundation.