Remote job
Head of Product
Job details
About this role
Role overview
This role elevates product quality from an informal habit into a structured discipline inside a two-sided marketplace. The work blends hands-on testing of trust-bearing flows with product ownership, starting with acceptance criteria and release readiness before expanding into backlog strategy. It suits someone whose career has straddled QA and product, and the setup is hybrid with Portugal as the preferred home base, though remote work is open.
Responsibilities
- Draft detailed acceptance criteria and edge-case documentation before engineering work begins - Test the highest-stakes flows end to end, including campaign setup, matching, content delivery, revisions, and payment settlement across both sides of the marketplace - Run bug triage by reproducing issues, ranking them by real user impact, and keeping the fix queue transparent - Serve as the release gatekeeper, building checklists and regression coverage that make ship decisions calm and consistent - Collaborate with engineering and design to translate recurring customer friction into prioritized specs - Grow into broader ownership of backlog sequencing and how success gets measured
Requirements
- At least five years combining QA, product ownership, or a hybrid path, with senior-level judgment - A track record of evolving from bug hunting into shaping product direction - A structured mind for edge cases across states, permissions, currencies, and network failure modes - Strong writing skills for specs, acceptance criteria, and actionable bug reports - Fluent English as the working language
Nice to have
- Direct experience with marketplaces, payment systems, or other two-sided products - Practical test automation background or comfortable SQL for self-serve analysis - Portuguese or Spanish language ability
Benefits and work setup
- Remote-friendly culture with written async practices that make time zones workable - Equity that represents a meaningful share of the business - End-to-end ownership of whole problems rather than fragmented tickets - Transparent decision-making with input from the people closest to the work - An annual budget dedicated to learning and development - Paid time off that the team actively encourages using