eneba - Product Manager
Requirements
• 3+ years running delivery for a team of 3-5 engineers — planning, estimation, release management, incident response. • A track record shipping integration-heavy or transactional systems: marketplaces, payments, trading, logistics, or platforms with real external dependencies. • Ownership of outcome metrics, not just output — you can give baseline, target and actual on releases you’ve personally driven. • Comfort working directly with engineers: can read an architecture trade-off, challenge an estimate, tell a two-sprint problem from a five-sprint one. • Experience turning ambiguous priorities into a scoped plan without waiting for someone else to hand you a finished roadmap. • What it’s like to work at Eneba • Opportunity to join our Employee Stock Options program. • Opportunity to help scale a unique product. • Various bonus systems: performance-based, referral, additional paid leave, personal learning budget. • Paid volunteering opportunities. • Work location of your choice: office, remote, opportunity to work and travel. • Personal and professional growth at an exponential rate supported by well-defined feedback and promotion processes. • Please attach CV's in English. • To find out about how we handle your personal data, make sure to check out our Candidate Privacy Notice https://www.eneba.com/candidate-privacy-notice
Responsibilities
• Own delivery end-to-end for your product area — turn prioritized problems into scoped, sequenced releases your team can actually hit. • Scope ambiguous priorities into a clear v1: explicit in/out, non-goals, acceptance criteria, dependencies and risks called out before a line of code is written. • Build a realistic plan grounded in team capacity, estimates and dependencies — separate committed from aspirational, and re-plan calmly when things shift. • Keep delivery on track day to day: know what every engineer is working on, spot risk early from leading signals rather than the deadline, and unblock the team before small slips become big ones. • Define success metrics, guardrails and kill criteria before build; instrument what you ship; roll out in stages with a clear decision point at each one. • Communicate progress honestly, including when something slips — with options, not just status. • Work with engineering as a peer: understand trade-offs, challenge estimates and technical approaches with substance, know when to stay out of the “how.” • Partner across stakeholders to align priorities and push back on scope or timeline with data when it’s warranted.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT