Job Opening: Operations Lead (hands-on)
We're building PLAI Cube — a voice-first AI cube with an intentionally simple pixel screen, speaker, and input interfaces that turns children's ideas into games and scenarios: "Imagine. Prompt. Play." No code, no phone, no "call an adult."
And yes: we're not "wrapping GPT in a teddy bear." We're building a new class of devices — an AI toy as a creative sandbox that develops AI readiness in children: formulating tasks for neural networks, evaluating results, iteratively improving them.
| Why this is a global thing, not "just another startup"
There's almost no AI toy market yet in the true sense of play + agency, where a child creates rather than consumes. We believe in AI as an exoskeleton for imagination (not a prosthesis that "thinks for you"). We want children to enter the age of AI interfaces not as passive users, but as creators.
— TRL 6, working prototype v2, v3 in preparation
— We've done hundreds of demos and attended 3 major exhibitions with booths and live play (and yes, the interest was very real)
— Invested €50k in prototyping, we have manufacturing capacity and experience thanks to parent company Galo Group, plus patent pending in Europe
— Next step: school pilots (targeting MENA region) + small device batch + teacher guide / curriculum pack (not just hardware, but how to live with it in the classroom)
| Who we're looking for (spoiler: not "just a PM")
We need a core team member. The role sits between project, product, and operations — but the key thing: this is a hands-on position where a significant part of the work is done by you directly, not just through coordination.
Separately: we have quarterly OKR planning, and this role owns OKR execution. That means you're responsible for keeping the team moving on OKRs, ensuring tasks get done, and key results are achieved (through rhythm, transparency, prioritization, unblocking, and driving tasks to completion).
— Handles "a lot of everything" and can turn it into a system
— Can do things hands-on, not just "organize," and isn't afraid of routine repetitive tasks (outreach, follow-ups, status updates)
— Helps the team move faster: maintains rhythm, focus, and clear agreements
— Can argue constructively and suggest improvements — while working toward the shared goal
This is a role where: we rapidly test hypotheses and move at high tempo — so tasks vary, but they're not random. Today — a mailing, tomorrow — LinkedIn content plan and outreach, day after — "which CRM do we pick for school outreach," then — organizing a demo and analyzing its results, and somewhere in between — finding a contractor for presentation design or helping finalize a brief for an external executor. And in parallel — keeping the overall project rhythm so experiments don't scatter but form a system and drive OKRs.
| What you'll be doing (roughly, but honestly)
1) OKR Execution: rhythm, clarity, progress tracking
— Collect "what's happening" across all streams and tie it to OKRs / KRs
— Turn task chaos into clear priorities, dependencies, deadlines
— Run regular status meetings with the team, document decisions and next steps
— Ensure OKR tasks don't "get lost" and are closed to completion
2) Operations + hands-on (outreach / LinkedIn / mailings / schools)
— Hands-on launch and drive to completion: mailings, LinkedIn outreach, follow-ups, initial pipeline
— Find schools and contacts, qualify, maintain database and statuses (spreadsheet/CRM)
— Schedule calls and demos, confirm, manage communication
— When needed — select and implement simple tools for this process (CRM, mailer, tracking)
3) Demos: preparation, refinement, analysis
— Prepare demos: scenario, materials, checklist, logistics
— "Polish" demos together with the team: document what doesn't work/unclear, and drive to fixes
— Collect and structure feedback after demos, draw conclusions and next steps
4) Contractors and artifacts
— Find contractors where delegation makes sense (e.g., presentation design), set briefs and control results
— Prepare concise working artifacts: one-pagers, status summaries, weekly/sprint plans — so they help action
| What success looks like (without the magic)
— After 2–3 weeks: you hold the project "map," there's a transparent status rhythm, and it's visible how current tasks connect to OKRs/KRs
— After 1–2 months: OKR tasks don't get lost, school/demo pipeline runs regularly, follow-ups reach conclusions, decisions are documented
— After 3–6 months: the project becomes more manageable and predictable — less manual "firefighting," more sustainable KR progress
— We're fine with family, pet projects, and life, but: if this is full-time, then PLAI is your only full-time, not one of several
— Time zone: around UTC+2 (give or take)
— Autonomy is high. Trust is high. Responsibility matches
Experience working with European and/or international startups, projects, or companies is a big plus — especially if it's systematic, long-term experience, not a one-off.
— Participation in a project that (in our humble opinion) rarely happens: a new class of devices + a new culture of children's interaction with AI
— Salary: €1,500–€2,000 to start (depending on experience and role fit)
— Equity — if we click and you become part of the core
— A team that's held together for 1.5 years and gets things done
Fill out the form. Take your time.
1. Send a link to your CV
*
2. Write your messenger contacts
*
In your application, describe one case:
— What was the deadline
— What was the team size
— What you had to manage simultaneously
— What needed to be done hands-on, what you did personally
— What decisions you made
— How you set up control (backlog/rhythm/DoD)
— How it ended (result, timing, metrics)
