QA Engineer
At Miquido, AI isn't a gadget bolted onto the process - it's the bet we've built the company around.
Before Gutenberg, every book was copied out by hand - a scribe bent over a desk for months to make a single copy. The printing press didn't end careful work with words; it just took the mind-numbing copying off the human and handed it to the machine, so people could spend themselves on what the words actually said.
For us, AI is that press for testing: agents take the repetitive work of writing and maintaining the suites, you spend your attention on what's actually worth testing and whether the product can be trusted.
What you'll do
Build and maintain real automated test suites - the kind that guard products people actually use - across API, web, and mobile. Not test plans that sit in a wiki and never run.
Work with the most modern AI testing tooling out there - and expect it to shift month to month. We'll keep handing you new things and asking you to put them to the test.
Help decide what's worth testing and whether we can trust what we ship, working shoulder to shoulder with engineers, the product manager, and the client - not just running someone else's checklist.
What you should bring
Real curiosity. You try new tools before anyone tells you to, you follow where testing and AI are heading, and you get a kick out of figuring out how things break. Plus enough English - min. B2 - to work with our clients.
The testing basics done right: a sharp sense of what to test and why, REST API testing, a solid grip on HTTP/HTML/CSS, and the analytical instinct to catch the bug nobody else spotted.
Enough coding to stand on your own - a programming language (JavaScript or Java/Kotlin preferred) and a working automation framework (Playwright, Appium, RestAssured or similar) - so you can read and shape what the tools produce.
The know-how to set up autonomous testing tools from scratch: taking the agentic tools that test on their own, configuring them, wiring them into CI, and getting a pipeline running against real builds without hand-holding.
Real fluency using those tools day to day - the autonomous testing tools alongside Claude, Codex or Cursor - to generate, run, and maintain tests, plus the habit of keeping up as the category shifts every month. This isn't a "nice to have" for us; it's the job.
How we actually work (AI-first)
Agentic coding is our default - Claude Code, Codex, Cursor, whatever's best that week. This is genuinely how we build and test, not a box we tick to sound current.
We're a company that keeps testing new things - fitting, for a QA team. No processes carved in stone: we assume the ground keeps shifting, so we try things, measure them, and keep what works.
Lately we work a lot in small, tight teams: 3 to 5 people, properly multidisciplinary, all on one project. Your responsibility is bigger - but so is your impact. What you flag actually changes what ships.
Skip the boring bit
Let's be honest: a CV is boring. It says almost nothing about you - nobody gets to know a tester from a bullet list. We'd rather be the kind of company that, instead of grinding through hundreds of CVs, actually sees what you've got and bets on real, human contact over paperwork.
So come and show us what you have. Pick one of these - and yes, all three are about AI, because that's the part we care about:
Ready to show us something? In the application form you'll find a required question asking you to confirm and share your AI-built test, tool, or video - paste your link there (not in the generic 'Website, Blog or Portfolio' field).
An automated test or suite you built with AI. A repo, a demo, a link - something you generated and shaped with Claude, Codex or Cursor and are actually happy with. Show us the path from prompt to passing test if you can.
Askill, script, or setup that makes AI do the grunt work. A custom skill, an agents.md, a test harness, a prompt library - whatever you built to get the tools testing for you instead of you doing it by hand.
A 2-3 minute video. Walk us through how you test with AI: how you decide what to automate, how you get an agent to write a test, and how you check it's testing the right thing. Rough and honest beats polished and empty.
We're not looking for someone to hand-write the same test cases they wrote five years ago - we want people who test like the tools have changed. Because they have.
But if that's you? Then we're curious about you - really. Here's our
Discord
- where two guys named Łukasz are hanging out: one's our AI Engineering Lead, the other our QA Lead. Come say hi, show them what you've been building, and just talk it through. No exam, no trick questions - two people who love this stuff, wondering what you've got.
If you're more senior
Same technical bar - the difference is what you own.
What we ask: several years testing products that reached real users, with real time spent on automation, not just manual passes; the ability to set a test strategy and stand it up from scratch - repos, frameworks, CI - and defend your choices on their trade-offs (time, quality, cost, complexity); automation leadership, from code reviews to unblocking the rest of the QA team; accountability for quality measured on metrics that mean something, like stability and coverage; mentoring regulars and juniors; and representing the quality side directly with clients (English min. C1).
What do we offer?
Be part of a talented, creative, and experienced team
Contribute to projects for clients around the world
Work with a schedule that fits your lifestyle
Private health insurance, MultiSport card, HearMe platform, and more
Work your way - remotely or from our Kraków office
We value your trust in providing us your data, thus we are striving to use commercially acceptable means of protecting it. Below you will find the necessary information about the data we collect and process when you send us your CV.
The controller of your personal data is Miquido Spółka z ograniczoną odpowiedzialnością sp. k. with its seat in Krakow, Zabłocie 43a, 30-701 Kraków, Poland ("Miquido", "We", "Our" or "Us").