Product teamRemoteFull-timePart-time from 4 hours a day

Product Engineer / Full Stack

Qberry builds its own and client products: SaaS, marketplaces, AI automation. We are looking for a full stack developer who takes a product from the idea stage and brings it to release, with AI as the main working tool.

Apply All vacancies

About the role

You own the whole path from an idea to a working module, on Qberry's own and client products. You work from a description, Figma mock-ups and the team's materials rather than a detailed spec, find what is missing yourself and bring the module to release.

Honestly about the role: if you are more comfortable receiving ready tasks and only writing code, this vacancy will not suit you.

What you will do

Take a product apart from its description, Figma mock-ups and the team's materials; find the missing roles, flows and screens.
Propose a split into modules and the order to build them.
Lay down the architecture and build modules end to end: backend, frontend, integrations, deployment.
Add the missing screens within the existing style with the help of AI, and remove whatever extra the model adds.
Choose LLMs and integrations (for example through OpenRouter) by price and answer quality.
Check AI output before handing it over: review, tests, a manual run through the user's path.
Report status, questions and risks yourself, without waiting to be asked.

Requirements

We judge experience as a whole: what matters is how strong you are, not where exactly you worked.

1+ year of development — employed, freelance or in your own startups and pet projects — and at least one product you took from zero to release and can show and talk through.
Full stack: you confidently cover both the backend and the frontend.
AI every day: you work with Claude Code, Gemini or Codex daily and can explain how you check their code.
Mobile first: you think mobile first and have experience with PWAs or mobile apps.
UI from Figma: you build interfaces from ready-made components.
Communication: you write short, clear status updates and ask questions to the point.

Nice to have

LLM integrations: OpenRouter, voice input, document parsing.
Experience in a product company or a startup.
Basic DevOps: deployment, CI, monitoring.
Your own pet projects taken from an idea to a product.

Not a good fit if

You will not start without a detailed spec.
You refuse to build UI even in a ready-made style.
You want a raise before you have shown results.
You hand over code from a model without checking it.

Conditions

Format: remote, full-time, or part-time from 4 hours a day while staying online during the company's working hours.
Pay: $1,500–$3,000 a month, the range is known from the start.
Review after 3 months by three criteria: how many modules you closed on your own, how many came back for rework, and deadlines.
Test task: part A (product breakdown) is free, part B (a module) is paid, the amount is fixed in advance.
Tools: your own Claude or Codex for the test task; company accounts once you join a project.

Selection process

1. Screening, 20 minutes. We talk about a product you took to release, how you work with AI and whether the format suits you both. After it the materials of the test task come by e-mail.

2. Product breakdown, 1–2 days, free. You get the description of one of our products, a Figma link and exports from Claude, with no hints about what is missing. You describe the roles and their access rights, list the missing flows and screens and mark which of them block the MVP, propose modules and their order, and write your questions to the product owner.

3. Defence on a call. For the first 20 minutes you present what you found yourself; we do not prompt or retell the project.

4. Paid module. You build one module with AI on every layer, for example a missing flow with screens in the style of the existing interface, and hand over the repository, a working demo and a short note: what the AI did, what you fixed yourself and how you checked it.

5. Offer.

What we look at in the test task

Independence: you found gaps we did not name.
Product logic: roles, user paths and edge cases are connected.
Priorities: a clear line between the MVP and what comes later.
Work with AI: it is visible that you checked the output and removed what was extra.
Style: new screens stay within the design system.
Communication: you explain clearly and answer the question asked.

Rodika

Recruitment Lead

Join our team

Tell us about yourself

Send your CV to Qberry, and our recruiters will contact you in the shortest time.

Send your CV hr@qberry.com.ua

Ready to bring your project to life?

Let's talk about your project

$ qberry --how-we-work

→ scope_and_estimate/

# clear scope and estimate before we start

→ weekly_demo/

# you see working progress every week

→ one_pm_on_your_side/

# one contact who owns your project

$ launch && support ▶

no black box —you see every step

About the role

Honestly about the role: if you are more comfortable receiving ready tasks and only writing code, this vacancy will not suit you.

What you will do

Take a product apart from its description, Figma mock-ups and the team's materials; find the missing roles, flows and screens.

Propose a split into modules and the order to build them.

Lay down the architecture and build modules end to end: backend, frontend, integrations, deployment.

Add the missing screens within the existing style with the help of AI, and remove whatever extra the model adds.

Choose LLMs and integrations (for example through OpenRouter) by price and answer quality.

Check AI output before handing it over: review, tests, a manual run through the user's path.

Report status, questions and risks yourself, without waiting to be asked.

Requirements

We judge experience as a whole: what matters is how strong you are, not where exactly you worked.

1+ year of development — employed, freelance or in your own startups and pet projects — and at least one product you took from zero to release and can show and talk through.

Full stack: you confidently cover both the backend and the frontend.

AI every day: you work with Claude Code, Gemini or Codex daily and can explain how you check their code.

Mobile first: you think mobile first and have experience with PWAs or mobile apps.

UI from Figma: you build interfaces from ready-made components.

Communication: you write short, clear status updates and ask questions to the point.

Conditions

Format: remote, full-time, or part-time from 4 hours a day while staying online during the company's working hours.

Pay: $1,500–$3,000 a month, the range is known from the start.

Review after 3 months by three criteria: how many modules you closed on your own, how many came back for rework, and deadlines.

Test task: part A (product breakdown) is free, part B (a module) is paid, the amount is fixed in advance.

Tools: your own Claude or Codex for the test task; company accounts once you join a project.

Selection process

1. Screening, 20 minutes. We talk about a product you took to release, how you work with AI and whether the format suits you both. After it the materials of the test task come by e-mail.

3. Defence on a call. For the first 20 minutes you present what you found yourself; we do not prompt or retell the project.

5. Offer.

What we look at in the test task

Independence: you found gaps we did not name.

Product logic: roles, user paths and edge cases are connected.

Priorities: a clear line between the MVP and what comes later.

Work with AI: it is visible that you checked the output and removed what was extra.

Style: new screens stay within the design system.

Communication: you explain clearly and answer the question asked.