Product Manager

At Miquido, AI isn't a gadget bolted onto the process - it's the bet we've built the company around.

For most of history, a building lived entirely in the master builder's head - they stood on site and told each mason what to do, stone by stone. Then came the drawing: intent set down precisely enough on paper that a whole crew could build from it, without the architect ever touching a brick. The craft moved from laying stone to getting the intent right.

For us, AI is that shift for product work: you write the spec clearly enough that agents and the team can build from it, and you spend your attention on the intent - what we're making, for whom, and why - not on pushing every pixel or chasing every task.

We hire for where you're heading, not how many years are behind you. If that's you, keep reading.

What you'll do

• Shape the product - the flow, the feel, how it all hangs together - for things real people actually use, from the first rough idea to what ships.
• Own the spec that drives the build. You write the intent down clearly enough - in a living set of markdown docs - that agents, engineers, and the client can all build from the same page, and you use AI to track and follow up on every product thread, so you get real answers out of the client, not just replies.
• Run the work, not just the design: delegate execution to AI and people, edit what comes back, and keep everyone pointed at the same thing.

What you should bring

• Real curiosity. You try new tools before anyone tells you to, you follow where product and AI are heading, and you get a kick out of figuring out how people actually use things. Plus enough English - min. B2 - to work with our clients.
• A real eye for product done right - flows, interfaces, how a thing should feel - and the judgment to tell good from good-enough.
• Sharp writing. You can turn a messy idea into a spec someone - or something - can build from: clear, structured, no room to misread it. This is half the job.
• Technical enough to run a markdown repo yourself: comfortable in git - branches, commits, pull requests - and happy keeping a project's knowledge as .md, not trapped in your head or buried in Figma comments.
• Real fluency with AI in your work - you already use Claude, Cursor or the like to draft, explore, and move faster, and you keep up as the tools change every month. This isn't a "nice to have" for us; it's the job.

How we actually work (AI-first)

• Agentic work is our default - Claude Code, Cursor, Codex, whatever's best that week. This is genuinely how we build, not a box we tick to sound current.
• We're a company that keeps testing new things. 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 decide actually shows.

Skip the boring bit

Let's be honest: a CV is boring. It says almost nothing about you - nobody gets to know a designer 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

A spec or PRD you wrote. A requirements doc, a product brief, a Living Intent: something that drove a project. Good sources are a side project, open source, volunteering, university work or anything that was already public. You can also take a real document and fully anonymise it (no names, numbers or business details that could identify the company). If none of that works, write a short doc from scratch for a made-up product.

A markdown repo you ran. Show us how you keep a project’s knowledge in git: the structure, the docs, and how you organise intent so a team can build from it. A private or side project is perfect. A skeleton works too: just the folder structure and sample files with made-up content.

A 2-3 minute video. Walk us through how you run a project with AI: how you split the work between agents and people, and how you check that what comes back is actually right. Keep it general or use your own project as an example. Please don’t show client data or your company’s internal tools.

Used AI to make any of it? Good. That's how the job works now - it counts in your favour, not against you.

If you're more senior

Same bar on craft - the difference is what you own.

What we ask: several years shaping products that reached real users, not just concepts in a portfolio; the ability to set a product's direction and defend your calls on their trade-offs (time, quality, cost, complexity); owning the spec and the project end to end, keeping a team and a client aligned without anyone holding your hand; mentoring regulars and juniors; surfacing risks early with options, not just problems; and representing the product 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 - We follow a flexible "work your way" approach and do not have a strict office or hybrid work policy.
• However, we are looking for someone who can easily attend workshops and in-person meetings when needed in our office in Kraków.

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 Kraków, Zabłocie 43A, 30-701 Kraków, Poland ("Miquido", "We", "Our" or "Us").