Balancing quality and innovation, Dan’s journey at MOCA System.

Meet Dan, our QA Manager who dedicates his day to guaranteeing that our products not only meet quality standards but also delivering the best user experience. His role includes testing, collaborative work with developers, and a continuous commitment to improving our products.

If you are curious about the life and the role of a QA Manager, we’ve got you covered. We found Dan at a desk piled high with test equipment, and he had plenty of interesting experiences and insights to share.


But here’s the charm of teamwork—his trusty teammates at MOCA always have his back, filling in the gaps and working together to make the products shine.

The mystery of access control.

One of the most exciting aspects of Dan’s work at MOCA is his involvement with Access Control. It’s one of MOCA System’s core technologies but the technology can be difficult to learn about unless you are in the industry. That is what makes it intriguing for him. For Dan, the arcane nature of access control makes it intriguing and good basis for furthering his career and knowledge.

Finding motivation: Improving services.

An employee’s motivation is quite important and we wondered what motivates Dan. He is fueled by the satisfaction of improving the quality of MOCA’s services. With the mantra “there are no issues behind me,” he approaches his role with the mindset that no issues should be left unresolved, striving for excellence every day.

A team player.

As a QA manager, Dan is the bridge between the business end of the company, the developers, and the market. When we asked Dan who he messages the most from MOCA, he couldn’t really pinpoint one individual, as he communicates with lots of people. Dan often finds himself communicating with developers, focusing on solving issues.

Process of QA.

Quality Assurance or QA… It’s a crucial process in software development. But what does a QA manager do or what does the process entail?

To start, the QA manager has to participate in meetings for planning new projects to understand specifications from both a QA and user perspective. Based on the meeting, the manager designs and writes test cases during development.

After development is complete, the QA manager performs validation checks to identify issues during the QA validation period. The development then fixes the identified issues. Once those are fixed, the QA will test the fixes to ensure stability. At the end of the process, the QA manager verifies that all features are deployed correctly in the production environment.

QA managers will continue to monitor field issues reported by users and work with the development team to fix them. The QA process is an essential process overall to ensure that the software is of high quality and meets the end user’s expectations.

How others describe Dan.

In the eyes of his colleagues, Dan is the “closing pitcher” of the Development Department. When the project managers lead with innovative ideas, and developers craft technically excellent products, Dan steps up to ensure that everything is in perfect shape before launching the product into the market. He’s not just an issue-finder; he strives to represent the customer and offers opinions on improving usability from the user’s perspective.

Random fact about Dan.

Here’s an interesting fact about Dan that might surprise his co-workers: he initially wanted to be a developer. He even landed his first job as a developer. But a twist of fate brought him into the world of QA, more than a decade ago. Despite taking a different path, he still finds himself engaging in conversations with developers, catching up on development lingo, and keeping an eye on what’s happening behind the scenes.

The man beyond work.

Dan used to be the president of a table tennis club and participated in soccer clubs. However, now his interests primarily revolve around his family, he has two children—one is two years old, and the other is just 200 days old not too long ago. After a day of work, it’s all about childcare and household chores.

My go-to software.

For work-related tasks, Dan relies heavily on JIRA and Confluence. JIRA is used for development and field issue management, and he enjoys customizing it to suit the company’s evolving needs. His habit of documenting project details in Confluence ensures that important information is never lost.

If I could swap jobs for a day.

We wondered who Dan would choose if he could switch roles with anyone at MOCA for a day. (Not) to our surprise, he would choose Fayoz, our project manager with a unique background.

Fayoz hails from Uzbekistan and completed his Ph.D. in Korea and is now working at MOCA, a company in Korea. Dan reveals his own experience of working in the Vietnam branch of his previous company. He believes that Fayoz’s deep understanding of cultural differences between countries and his adeptness at project management make him an interesting choice for a job swap. It would allow Dan to better empathize with Fayoz’s challenges and perspective.

That’s a glimpse into the life of a QA Manager at MOCA System. Dan’s journey is a blend of curiosity, teamwork, and a commitment to delivering top-notch services. His story is a testament to the vibrant, supportive, and ever-evolving work culture at MOCA Systems. So, next time you hear the term “QA Manager,” you’ll know it’s not just about finding issues; it’s about making sure every product that reaches the market is a home run. Thank you to Dan who always makes sure our portals and apps are in the best shape!