Senior testers who treat your build like it's the only one.
"It's amazing how they are still finding bugs!" is the line we hear back from internal dev teams, and it's the closest thing to a mission statement we have. We're a manual functional QA studio for game devs and publishers, AAA-trained, staffed per project. If you want a team who treat one project as foundational instead of one slot in a rotation, we're built for that.
It started with a dream.
Alkotech Labs started in 2024 from a desk in Craiova, one laptop, and a list of former Ubisoft colleagues that our founder, Radu, trusted to call when real Quality needs to be delivered.
We run without the layers most QA vendors run on. No offshore subcontracting or bench rotations. No incentive to staff your build with anyone other than the people best matched to it. We started in 2024 and have hired against that operating shape every time since, which is why the bar holds when it grows.
The studios that work with us tend to want the same thing — a QA team that treats their game with the care and dedication it deserves. If that's the partner you're looking for, we'd like to hear from you.
How we actually work.
Carefully built teams
We staff each project with people whose backgrounds match the build: genre, platform, engine, live-ops cadence. No "whoever's free on Monday."
Direct ownership, no handoffs
The lead who scopes your project runs it start to finish. No account managers between you and the work. The person reading your build is the person writing the report.
Clarity first
Every issue has clean repro steps. Every week has a written report. A ticket isn't done until a developer who's never touched the build can act on it without asking us a question.
Exploratory testing is where the real bugs live
Test plans confirm stability. Exploration finds the things players will actually hit at 2am on a Tuesday. We do both, and you'll thank us for it.
We adapt to your pipeline
Your Jira, your Confluence, your tracker, your cadence. We embed in the dev team's daily flow.
Bugs tracked to root cause, then across builds
We don't submit tickets and forget them. We follow issues until the fix actually holds across the next builds. That's why we tend to hear "how are they still finding bugs?" from the dev side.
Radu Posoi
Founder & QA Lead
Radu started his QA career at Ubisoft, where he spent years learning what AAA standards look like from the inside. He's worked on 30+ shipped titles across console, PC, and mobile, with most of his hands-on experience in mobile and live-service titles.
Right now, Radu's focus is on pushing the QA craft further and further, beyond the traditional ways of doing things.
His core philosophy is simple: help people and make the world a better place, one step at the time.