You will work closely with development teams to execute the product roadmap defined by our CPO (Commercial Product Demand), maintain high quality standards, track team performance metrics, and ensure on‑schedule release delivery without delays.
This is an execution-focused role. You’ll translate business requirements into technical specifications, manage the delivery process, minimize bugs and incidents, and ensure our customers receive high-quality features on time.
Time Allocation:
- 50% — Feature delivery execution (backlog, user stories, sprint management)
- 20% — Technical documentation (BRD, PRD preparation)
- 15% — Quality & metrics (bug reduction, incident management, team performance tracking)
-
15% — Stakeholder coordination (customers, sales, support)
Report To: Chief Product Officer (CPO)
Location: Remote (Europe/US time zones preferred for team overlap)
Key Responsibilities & Expected Outcomes:
- FeatureDelivery Execution (50%)
- Technical Documentation (BRD & PRD) (20%)
- Quality Management & Bug Reduction (15%)
- Team Performance Metrics & Tracking (Integrated into above)
- Stakeholder Coordination (15%)
Must-Have Qualifications:
- Experience 3-5+ years as Product Owner or Product Manager in B2B SaaS, cloud software, or CRM solutions
- Proven track record of on-time delivery: Be ready to share specific metrics (e.g., “Achieved 95% on-time release rate over 12 months”)
- BRD/PRD writing experience: At least 2 years writing technical specifications for engineering teams
- Agile/Scrum mastery: 3+ years managing backlogs, writing user stories, leading sprint ceremonies
- Quality focus: Experience reducing bug rates and managing incident response
- Technical proficiency: Understanding of APIs, cloud platforms, CRM integrations, data models
Skills:
- Execution Excellence: Ability to drive features to completion on schedule, removing blockers proactively
- Technical Documentation: Strong writing skills for BRD/PRD with clarity and detail
- Analytical: Can track and present team performance metrics (velocity, cycle time, bug rates)
- Quality Mindset: Obsessed with reducing bugs, improving processes, preventing incidents
- Communication: Fluent English (C1/C2), able to explain requirements to technical and non-technical audiences
- Prioritization: Can make quick trade-off decisions to keep releases on track
- Incident Management: Experience triaging and coordinating response to production issues
Tools Proficiency:
- Jira/Linear: Advanced backlog management, sprint planning, reporting
- Confluence: Documentation, BRD/PRD templates, knowledge management
- Analytics: Mixpanel, Amplitude, Google Analytics for feature tracking
- Design: Figma collaboration for UI/UX specifications
- Communication: Slack, Zoom, async documentation practices
Mindset:
- Delivery-focused: Obsessed with hitting release dates and shipping quality features
- Detail-oriented: Catches edge cases, writes comprehensive acceptance criteria
- Proactive problem-solver: Removes blockers before they impact timelines
- Quality-driven: Won’t ship until it’s right, balances speed with quality
- Team player: Supports engineering, collaborates with cross-functional teams
- Customer-centric: Understands impact of delays and bugs on customer experience
Nice-to-Have (Bonus Qualifications):
Experience
- 5-7+ years product ownership experience (for Senior-level consideration)
- Previous experience in CRM industry (Salesforce, HubSpot, Pipedrive ecosystem)
- Background as Business Analyst, Solutions Engineer, or QA Lead (strong documentation skills)
- Experience with DevOps practices (CI/CD, release automation, monitoring)
- Incident management training (ITIL, SRE practices)
- Experience managing API products or developer-facing features
Skills & Knowledge
- SQL proficiency: Can write queries to analyze feature usage and performance
- Scripting/automation: Python, JavaScript for data analysis or tooling
- Advanced Jira: Custom workflows, automation rules, dashboard creation
- API documentation: Swagger/OpenAPI specification writing
- Performance testing: Understanding of load testing and scalability considerations