Can you tell us about your journey from architectural engineering to becoming a QA Engineer? What inspired this transition?
It was a pure coincidence. After seeing on LinkedIn that one of my colleagues (now my work colleague) from the faculty started working in Walter Code as QA for Revit. Having used Revit extensively and developed a strong interest in BIM (Building Information Modeling), curiosity led to exploring further. A visit to Walter’s website revealed an open call for the current position. The rest is history.
How does your background in architecture influence your approach to quality assurance in software development?
As an architect, an eye for detail was essential, knowing that even small mistakes could have a big impact on a building. This mindset directly translates to software quality assurance, where precision is equally important. Additionally, working with numerous software programs over time developed the ability to quickly understand and adapt to new tools, which has proven invaluable in QA.
What’s unique about the current project you are working on, and how does it relate to your architectural expertise?
The project I’m working on addresses issues that used to be the bane of my existence as an architect. Being part of the solution now makes me incredibly enthusiastic. Since our target users are mostly architects and construction specialists, my familiarity with how they think, and work gives me an advantage in testing the software from their perspective.
How do you measure the success of a QA process? What metrics do you use to ensure high-quality outcomes?
The primary measure of success is ensuring the end user experiences as few bugs as possible. I aim for clean and smooth functionality with minimal interruptions to user experience.
How do you collaborate with developers and product owners when there are differing views on quality or functionality?
I’m fortunate to be part of a great team where communication flows easily. We’ve been able to discuss differing opinions openly and always find common ground, so differing views have never been an issue.
What role does agile methodology play in your work as a QA Engineer? Can you share an example of how it helped improve product quality?
When I started my career as a QA, agile was one of the challenges. It was my first contact with mature methodology. As someone who aspires to have his work organized, agile was a huge revelation. Review and planning sessions are great way of keeping a project on track. I appreciate the use of structured methodology since I did not have an opportunity to use the same methodology in my previous job when my stress level was raised due to short deadlines caused by bad planning.
Outside of work, how do you stay connected to your architectural roots, and what hobbies or activities do you enjoy?
In my free time, I like to partake in hobbies like drawing and photography, which are in a way my connection to architecture. You could say that architecture became my hobby, where I use drawing to explore ideas that I could not if the client was involved. Photography is a side effect of being an architect, we like to take photos of buildings. Also I’m trying to get back to rock climbing which I love to do, as it keeps both mind and body healthy.
What excites you most about working at Walter Code?
Since coming to Walter, I had to leave my comfort zone multiple times, which made me learn a lot, and opened new horizons, never thought possible before. I see a lot of possibilities to learn and grow, and that’s what I find most exciting.