Testing the Limits: Alkis Kotsas, Senior QA Automation Engineer

Let’s start from the beginning — who is Alkis when he’s not deep in code or testing frameworks? 
I have a strong background in test automation, CI/CD integration, and building scalable quality processes. Over the years, I’ve focused on delivering robust, maintainable test frameworks for web and backend platforms, always aiming to bridge the gap between developers and QA through collaboration and automation. Outside of tech, I’m also a passionate music producer with a long-standing career as a DJ, specializing in various genres and live performances. Additionally, I have a deep background in Latin Dancesport — I’ve proudly represented Greece in international competitions and have built a parallel career as a skilled Latin dance teacher. These experiences have shaped my discipline, creativity, and teamwork — qualities I carry into my engineering work as well.  

You’ve had quite the QA tour. What’s one lesson you’ve carried with you across all these experiences? 
It’s the importance of truly understanding the purpose and usability of the end product. When I grasp what we’re building and why, I can think more effectively about how to test it — not just functionally, but in ways that align with real user expectations and risks. 

Over time, I’ve realized that while methodologies, architectures, and technologies vary from project to project, the core principles of good testing remain consistent. If you start with solid fundamentals and adapt them based on context, you can build a strong, flexible quality strategy. It’s this mindset — combining product understanding with adaptable principles — that ensures I’ve done everything possible to safeguard the product’s quality. 

That mindset of blending understanding with adaptability really resonates. Was that part of what made you choose Cegeka — or did something else draw you in? 
I was drawn by the chance to step into something new—technologies, domains, and ways of working. Cegeka’s international culture also stood out. Working with colleagues from different countries brings fresh perspectives and pushes me to think more creatively. 

With so many tools and trends out there, how do you decide what to dive into next? 
“A rolling stone gathers no moss, but it gains a certain polish.” 

That quote perfectly sums up my mindset toward growth and learning. What keeps me moving forward is the constant search for opportunities — whether that’s a new technology, a business challenge, or a way to improve myself. I don’t follow a fixed path — instead, I focus on where I can add the most value and grow at the same time. For example, right now I’m diving deeper into API testing because that’s where I can sharpen my technical edge. Next, I plan to focusmore on soft skills, like mentoring and team collaboration, to complement that growth. The cycle I follow is simple: I learn, I perform, I share, I help — and then I repeat. 

You mentioned growth comes from the environment, too. In your hybrid role, what helps you feel connected and collaborative with your team? 
For me, staying connected starts with clarity — knowing my responsibilities, where they begin and end, and who to reach out to for what. At Cegeka, our hybrid working setup really supports this by giving us the flexibility to work from different locations while staying aligned as a team. When roles are clearly defined and communication flows through the right channels, collaboration comes naturally — whether we’re at home or in the office. What really makes the difference, though, is the team culture we have here: built on shared values, trust, and open dialogue. That’s what helps me feel part of the team, no matter where I’m working from.

Is there a specific project at Cegeka that’s made you feel especially proud or excited? 
It’s actually the one I’ve been involved with since my very first days here - building a backend test automation framework from scratch, using TypeScript and Playwright. The framework is designed to test both REST and gRPC cloud microservices, making it flexible and powerful for modern backend architectures. It’s fully integrated into our CI pipeline with nightly runs, alerting, and automated reporting to Tricentis/Jira. Maintaining and evolving this setup has not only been technically rewarding, but also a key part of ensuring quality across the platform. 

Share with us what you wish you knew when you were just starting out. 
‘’Before you act, make sure you understand.’’ It’s tempting to jump straight into writing test cases or building a strategy the moment a feature or service lands — and yes, speed matters. But if you don’t take the time to understand the bigger picture — the business context, the purpose behind the product, and the actual user needs — you risk solving only today’s problem, not tomorrow’s. So, my advice to anyone starting out in QA automation is to spend time up front to deeply understand the product and its goals. That knowledge will guide everything — from how you approach testing to how you prioritize your efforts. And it’s what transforms a tester into a true quality advocate.

I’m curious, if your test scripts could talk back, what do you think they’d say about you? 
“Look, I get it — most people test the obvious paths… but...there's nothing left to test!  

I think my scripts would say that I leave no stone unturned. I aim to cover not just the happy paths, but the weird, unexpected, edge-case scenarios too. If my tests could talk, they’d probably ask me to give them a break — because I’ve already pushed them through every situation a curious or unlucky user might stumble into! 

Lastly, on May 20th you will join WeTest and talk about: ‘’Beyond Frontend: Leveraging Playwright for gRPC Cloud Backend Testing’’. Why did you choose this topic? 
I chose this topic because it perfectly aligns with the cycle I live by: “I learn, I perform, I share, I help.” When I spoke with other QA Automation Engineers, I was surprised to hear how many had never worked with gRPC, or didn’t know how to approach testing it — especially when it comes to integrating it with modern tools like Playwright. So, I saw this as a great opportunity to share what I’ve learned. I’m not a fan of gatekeeping knowledge — if something works well, I believe it should be shared. That’s how our community grows. 

You shouldn’t miss this talk because it bridges the gap between modern frontend tooling and complex backend testing — in a way that’s practical, clear, and ready to use. If you’re testing APIs and want to expand your toolkit beyond REST, this session will open a new door. Plus, you’ll walk away with real examples, lessons learned, and maybe a few “aha!” moments.