From QA to Product Owner: A Career Journey in Fintech

Moving from software testing into product strategy, Vita Dzon discovered that the role of Product Owner is less about documentation and more about people, communication, and human-centric design. From navigating high-level stakeholder management to utilizing AI as a daily productivity boost, in this interview, Vita shares how she builds impactful products by focusing on the "why" behind code decisions.

How did you get into Product Management and Product Ownership? What were the biggest challenges along the way?

I began my journey at the company as a QA engineer. Even then, I found myself drawn to the logic behind the product. I wanted to understand why something worked the way it did and whether there might be a better solution, often sharing these insights with my team. My background in Software Engineering further fueled this curiosity.

After about two and a half years in QA, I felt I needed a broader challenge. I was torn between becoming a developer and moving into product management. Ultimately, the product route appealed to me most because it offered a deeper look into product development, business strategy, UX, and market dynamics.

I mentioned to our PM that I’d like to try my hand at this role, and eventually an opportunity came up to transition into Product Ownership on the same project. I accepted, and found myself working in the Fintech domain.

It was challenging at first. As a QA engineer, I could analyze and contribute ideas, but the final decisions were made by someone else. As a Product Owner, I had to take ownership of those decisions. I was prioritizing the backlog, communicating with multiple stakeholders, attending countless meetings, and ultimately becoming accountable for product outcomes. At the same time, I genuinely enjoyed it. I like solving problems and helping teams move forward.

What principles guide your approach to managing a product and working with development teams?

First and foremost, you have to stay solution-oriented. Earlier in my career, I also worked as a problem-solving ambassador alongside my accounting responsibilities. That experience taught me to focus on finding a solution, rather than someone to blame. For Product Owners, it's vital not to get stuck on the problem itself.

Another thing I strongly believe in is being a true part of the team rather than a "big boss" who just hands out tasks. I never think, "I'm a Product Owner, so testing isn't my responsibility." If needed, I'll test features myself because I’m simply interested in it, plus it keeps me connected to how the product works and allows me to answer user questions confidently.

I'm in the same boat as my team, and I set the course for that boat, but at the same time, I'm ready to listen to their suggestions — like, maybe there's a storm coming, and we need to head in a different direction. And that ability to listen to them in time is what allows us to steer back toward where we need to go.

What drives you and brings you the most satisfaction as a Product Owner?

I truly enjoy communication, both with the team and with end users. We work on a B2B platform, and our customers are business owners, so they come to us with their challenges, and we find solutions for them. Being able to hear their challenges firsthand, understand what they need, and approach those conversations with empathy is something I value a lot.

The absolute best moment is when you present a new feature and see that it genuinely improves their work. When customers tell me that a feature made their process ten times easier, those moments are meaningful. They remind me that we're not building things simply for the sake of building them. We're creating something actually valuable for the users.

Another thing that drives me is my love of learning. Continuous growth gives me energy, and a big reason I moved into Product Ownership was the variety of learning horizons it covers. You can dive into UX, master business logic, and gain a much deeper understanding of market dynamics and business operations. Those are powerful skills, not just for this role, but for my career overall.

What do you value most about Softjourn's culture?

Without a doubt, the people. From my immediate team to the company as a whole,  there is a warm, supportive atmosphere here, which I truly appreciate. I love our team-building activities, hiking trips, and getting together to play volleyball.

Another big advantage is that we have genuinely good professionals. When I first joined, they were actually a huge source of motivation for me. I remember thinking,

"They're so smart. They talk about things with such confidence and expertise. I want to be able to do that too."

They inspired me to keep learning, so I could match that level of professionalism.

I’m also grateful to the company for the opportunity to transition into a new role and for supporting me throughout that journey. And I appreciate the company’s social responsibility, including its support for the military and other community initiatives. That kind of involvement really resonates with me. 

What is the biggest misconception people have about the Product Owner role?

People often think this role is purely about the product or just writing documentation. But a product cannot exist without the team, and a huge part of the job is people and stakeholder management.

A team is such a dynamic environment full of diverse people, and you have to communicate differently with everyone. This realization actually inspired me to enroll in psychology studies; It`s a big plus for a manager to understand how the human mind works.

Furthermore, you often deal with high-level stakeholders. And they, too, may have different opinions. Because you cannot implement a single feature in two different ways, you have to balance these perspectives while ensuring everyone feels valued.

And that means being open and honest with people. Whether with clients or end users, when you’re on a call, it’s important to show empathy, to be sincere, and honest. 

In other words, it’s important to me to show humanity. Great business and great humanity aren't opposites — motivated, valued people are the engine behind any business that lasts.

How would you describe the Product Owner role in just three words?

Drive. Management. Support

How has AI changed the requirements for Product Owners? Do you personally use it?

For me, it’s a day-to-day productivity booster. I use it for writing tickets, generating documentation, producing support materials, and speeding up feature research. 

The key is learning how to use it effectively and verify everything it produces. If you write good prompts and use them thoughtfully, it can significantly increase your productivity and help you accomplish much more with less effort.

In many ways, knowing how to use AI today is what basic computer literacy was for us decades ago. However, I wouldn't say prior AI experience is a strict requirement for entering the field, but I do think it's important not to be afraid of using it. Once people try it a few times and see how effective it can be, they usually start incorporating it naturally into their work. It's simply a powerful tool that helps you work more effectively.

What skills are most critical for someone looking to move into Product Management?

• Be proactive. If you want to transition into a new role, whether it's Product Ownership or something else, you need to demonstrate it before you officially have the title. Just wanting isn’t gonna do much; you have to communicate your ambitions. Let your manager and your company know where you want to grow. 
• Expect the extra load and responsibility. In my experience, Product Ownership involves significantly more responsibility than QA. You're communicating with stakeholders, working with executive leadership, and taking ownership of what ultimately reaches the customer. In other words, you make sure the team has done what’s necessary to deliver the product to users exactly as they requested it. 
• Assess your fit. Even before taking courses or formal training, you can begin demonstrating the mindset and skills required for the position, ask for feedback, identify zones of improvement, and test if you’d actually like to do it. 

If you’re someone who dislikes constant communication, avoids tough discussions, or shies away from taking responsibility for final decisions, you likely won't enjoy this role in the long run.

Once you’ve decided this is the path you want to take, don't be afraid. Believe in yourself and learn from both mistakes and successes.

FAQ: Product Owner vs Product Manager vs Project Manager

A Project Manager is primarily focused on the team and the delivery process. They typically don't go as deep into specific features or product strategy. Instead, they manage the team, coordinate workflows, oversee internal processes, and ensure the team is not blocked or overloaded.

The distinction between a Product Manager and a Product Owner can vary from company to company, but generally, the Product Manager is responsible for defining the product strategy and vision. For example, they might say: “I want users to be able to generate a report showing their spending.”

The Product Owner then takes that vision and figures out how to make it happen. Is it technically feasible? What requirements need to be defined? What should the report look like? How quickly should it generate?

In practice, the Product Manager looks outward. They analyze the market, study competitors, identify opportunities, and decide what the product should offer. They might say, “Our competitors have this feature, and we need something similar.” A Product Owner translates that vision into execution. They define requirements, manage the backlog, collaborate with the development team, and ensure the product is delivered successfully to production.