Context

Companion platform for an adult audience. Launched in December 2024, we compete with products having 20M+ monthly visitors. The team has 20+ people, using microservices (PHP + Vue.js).

We are restructuring the development team into two streams. You will be responsible for the second stream — frontend, backend, design, QA. You will take tasks from the CEO, structure them, put them into sprints, and monitor their execution.

Role

You don't come up with what to build — the CEO does that. Your job is to ensure it gets built: on time, without rework, and without loss of context between the CEO and the developer.

Directly reporting to the CEO. You are his hands in the team — translating concepts into tasks, keeping the sprint alive, and removing blockers.

Tasks

Task Management

— Take concepts and directions from the CEO, break them down into specific tasks with acceptance criteria. — Keep the backlog populated and prioritized — the team never waits for what to do next. — Write task descriptions so that the developer doesn't ask clarifying questions. — Review designers' results for task compliance before handing them over to development. — Monitor competitors and document findings — grow your understanding of the market along with the product.

Sprint Management

— Planning, daily stand-ups, retrospectives — your responsibility. — Monitor team velocity, identify risks before they become problems. — Remove blockers: negotiate, clarify, escalate to the CEO only when necessary.

Communication

— Keep the CEO informed without unnecessary noise — concisely, to the point, with conclusions. — Ensure there's no broken telephone between the team and the CEO — accurately convey context in both directions. — Document decisions in writing, do not rely on memory or verbal agreements.

Quality

— Ensure QA is involved before development, not after. — Definition of Ready is followed — tasks without acceptance criteria do not enter the sprint. — Rework is your personal KPI. The less there is, the better you work.

Requirements

Must-have

— 3+ years as a Project Manager in a product IT team. — Confident work with Jira, Mixpanel, or similar tools. — Experience managing sprints using Scrum or Kanban. — Ability to write tasks that don't require re-asking. — Conversational English B2+. — Deep understanding of how web development works. — Experience working with a fast-paced team.

Nice-to-have

— Worked in a team of up to 20 people without established processes. — Ability to say no without conflict. — Willingness to build a product team under your management in the future. — Possibility of relocation to Cyprus for office-based work.

What We Offer

— Direct access to the CEO — decisions are made quickly, without bureaucracy. — A clear role with no blurred boundaries — you know what you are responsible for. — A live product with real users right now. — Async-first: results are more important than online presence. — Competitive compensation — discussed individually.

Not a Fit If

— You want to influence product decisions immediately — here, initially, you execute, not strategize. — You are uncomfortable working with adult content. — You need established processes — you will build some of them yourself. — You are used to working through long chains of approvals.