PM/QA

Why this role exists

Two gaps are holding the team back. First, the CTO is absorbing too much coordination overhead: breaking down requirements, running syncs, unblocking developers. Second, testing coverage hasn't kept pace with shipping speed — bugs that automated tests would have caught are slipping through to production.

This role is designed to close both gaps at once. The PM side frees up the CTO by owning task creation and team coordination. The QA side builds an automated testing layer from scratch, with AI tooling at its core. Neither half of this role is a full-time job on its own — together, they're exactly one.

What we expect from an ideal candidate

• 3–5 years of total experience with at least 1.5 years in a project or product management role and at least 1.5 years in QA engineering
• At least 2 years of that experience must be at a product company
• Proven ability to break down product requirements into clear, structured technical tasks for a development team
• Experience running sprint planning and retrospectives, or working closely within that process
• Strong self-management and prioritization — able to hold multiple threads across PM and QA without dropping things or waiting to be told what's next
• Experience in QA engineering with a demonstrated shift toward automation — manual-only QA is not a fit for this role
• Solid understanding of regression testing and functional testing concepts
• Working knowledge of SQL sufficient to validate data at the database level (Postgres, Clickhouse a plus)
• Ability to distinguish frontend bugs from backend bugs quickly and describe them precisely
• You should be actively using AI tools to automate, build, and accelerate your own workflow
• English B1 or above — sufficient for written communication and technical documentation

Nice to have

• B2B SaaS background in a QA, PM, or hybrid role
• Prior experience with a marketing technology product (attribution, analytics, ad tech, CRM, or similar)
• Strong English (C1) — a plus for communication with native-speaking stakeholders