Senior Product Owner
Senior Product Owner<\/span>
<\/h1>Location:<\/span> Nairobi | <\/span>Department:<\/span> Product | <\/span>Reports to:<\/span> Head of Product | <\/span>Job type:<\/span> Permanent<\/span>
<\/p>About the Role<\/span>
<\/h3>Emalify is Roamtech's B2B communications platform (CPaaS), serving businesses across East Africa with omnichannel messaging and engagement tools. The platform enables enterprises to reach their customers through email, SMS, USSD, voice, WhatsApp, and surveys\u2014all via a unified interface and API. Launched in 2019, Emalify now serves major banks, retailers, and online merchants across Kenya, competing against global players and regional providers.<\/span>
<\/p>You will own product outcomes for Emalify, Roamtech's communications platform. This means you're accountable for solving real customer problems in ways that work for the business\u2014not just shipping features on schedule.<\/span>
<\/p>You'll lead continuous product discovery to identify the right problems to solve, validate solutions before committing engineering resources, and measure success by business impact rather than delivery velocity.<\/span>
<\/p>This is not a project management role. You'll work with an empowered engineering team, not direct them. You're expected to bring deep knowledge of customers, the market, and the business to inform what gets built.<\/span>
<\/p>Key Responsibilities<\/span>
<\/h3>Product Outcomes<\/span>
<\/p>Define and deliver against quarterly business outcomes (e.g., reduce churn by X%, increase ARPU by Y%) rather than feature lists<\/span>
<\/p><\/li>Accountable for Emalify's contribution to Roamtech's strategic objectives<\/span>
<\/p><\/li>Make hard prioritization calls based on impact, not stakeholder volume<\/span>
<\/p><\/li><\/ul>Continuous Discovery<\/span>
<\/p>Maintain weekly customer/user contact\u2014you cannot delegate understanding your customers<\/span>
<\/p><\/li>Run rapid experiments and prototypes to validate (or kill) ideas before they hit the backlog<\/span>
<\/p><\/li>Partner with design and engineering to explore solution space before committing to build<\/span>
<\/p><\/li>Continuously develop PRDs for validated opportunities, building a pipeline of ready candidates for quarterly roadmap planning<\/span>
<\/p><\/li><\/ul>Product Strategy<\/span>
<\/p>Define and communicate Emalify's product vision and how it connects to Roamtech's portfolio strategy<\/span>
<\/p><\/li>Own competitive and market intelligence for the communications/CPaaS space in East Africa<\/span>
<\/p><\/li>Identify new opportunities through market analysis, not just react to feature requests<\/span>
<\/p><\/li><\/ul>Team Collaboration<\/span>
<\/p>Partner with the Engineering Lead as co\-leaders of your product team<\/span>
<\/p><\/li>Maintain continuous communication and partnership with the Engineering team members while negotiating Sprint capacity in order to balance between Product and Engineering needs<\/span>
<\/p><\/li>Work with Design to ensure solutions are usable and desirable<\/span>
<\/p><\/li>Shield the team from distraction while keeping them connected to customer reality<\/span>
<\/p><\/li><\/ul>Stakeholder Management<\/span>
<\/p>Translate business needs into product strategy without becoming an order\-taker<\/span>
<\/p><\/li>Communicate roadmap as a strategy document, not a promise of features by dates<\/span>
<\/p><\/li>Say "no" with data and rationale when requests don't align with outcomes<\/span>
<\/p><\/li><\/ul>
<\/div>Key Performance Indicators<\/span>
<\/h3>Product Value & Impact (Primary)<\/span>
<\/p>ROI on Product Initiatives: Measured business impact vs. investment for shipped work<\/span>
<\/p><\/li>Feature Adoption: % of target users actively using new capabilities within 90 days<\/span>
<\/p><\/li>Churn Reduction / Retention Improvement: Measurable uplift attributable to product changes<\/span>
<\/p><\/li>Revenue Impact: Contribution to ARPU, new revenue streams, or cost reduction<\/span>
<\/p><\/li><\/ul>Discovery & Validation<\/span>
<\/p>Discovery Velocity: Number of customer problems validated or invalidated per quarter<\/span>
<\/p><\/li>Experiment Completion Rate: % of planned experiments/prototypes executed before full build<\/span>
<\/p><\/li>Customer Contact: Minimum weekly direct customer/user interactions maintained<\/span>
<\/p><\/li><\/ul>Delivery & Execution<\/span>
<\/p>Outcome and Roadmap Delivery Rate: % of quarterly outcome targets achieved and % of the roadmap items delivered<\/span>
<\/p><\/li>Time\-to\-Learning: Average time from hypothesis to validated insight<\/span>
<\/p><\/li>Release Quality: Post\-release defect rate and rollback frequency<\/span>
<\/p><\/li><\/ul>Stakeholder & Team Leadership<\/span>
<\/p>Stakeholder Alignment: Quarterly satisfaction rating from commercial, engineering, and executive peers<\/span>
<\/p><\/li>Team Clarity: Engineering team's self\-reported understanding of product direction (quarterly pulse)<\/span>
<\/p><\/li>PO Mentorship: Development progress of junior/mid POs under guidance<\/span>
<\/p><\/li><\/ul>Product Quality & Stability<\/span>
<\/p>Product Uptime / Reliability: % availability against SLOs<\/span>
<\/p><\/li>Technical Health: Trend in tech debt tickets (decreasing backlog, not % allocation)<\/span>
<\/p><\/li><\/ul>
<\/div>Requirements<\/span>
<\/h3>Must have:<\/span>
<\/p>5+ years in product roles with demonstrated ownership of business outcomes<\/span>
<\/p><\/li>Evidence of discovery work: customer research, experimentation, prototype validation<\/span>
<\/p><\/li>Experience with B2B or platform products (APIs, integrations, developer experience a plus)<\/span>
<\/p><\/li>Ability to articulate product strategy and defend prioritization decisions<\/span>
<\/p><\/li>Track record of working <\/span>with<\/span> engineering, not just handing off specs<\/span>
<\/p><\/li>Bachelor's degree in CS or a related field<\/span>
<\/p><\/li><\/ul>Strong preference:<\/span>
<\/p>Experience in communications, CPaaS, or adjacent fintech/telecom<\/span>
<\/p><\/li>Familiarity with East African or emerging market dynamics<\/span>
<\/p><\/li>Exposure to pricing strategy, packaging, or monetization decision<\/span>
<\/p><\/li>Experience in Design Thinking and modern product discovery frameworks<\/span>
<\/span><\/p><\/li><\/ul>Nice to have:<\/span>
<\/span><\/p>CSPO certification or any BA/PM\-related ones.<\/span>
<\/p><\/li>Certified Scrum Master<\/span>
<\/p><\/li><\/ul><\/span>
<\/p>
About the Role<\/span>
<\/h3>Emalify is Roamtech's B2B communications platform (CPaaS), serving businesses across East Africa with omnichannel messaging and engagement tools. The platform enables enterprises to reach their customers through email, SMS, USSD, voice, WhatsApp, and surveys\u2014all via a unified interface and API. Launched in 2019, Emalify now serves major banks, retailers, and online merchants across Kenya, competing against global players and regional providers.<\/span>
<\/p>You will own product outcomes for Emalify, Roamtech's communications platform. This means you're accountable for solving real customer problems in ways that work for the business\u2014not just shipping features on schedule.<\/span>
<\/p>You'll lead continuous product discovery to identify the right problems to solve, validate solutions before committing engineering resources, and measure success by business impact rather than delivery velocity.<\/span>
<\/p>This is not a project management role. You'll work with an empowered engineering team, not direct them. You're expected to bring deep knowledge of customers, the market, and the business to inform what gets built.<\/span>
<\/p>Key Responsibilities<\/span>
<\/h3>Product Outcomes<\/span>
<\/p>Define and deliver against quarterly business outcomes (e.g., reduce churn by X%, increase ARPU by Y%) rather than feature lists<\/span>
<\/p><\/li>Accountable for Emalify's contribution to Roamtech's strategic objectives<\/span>
<\/p><\/li>Make hard prioritization calls based on impact, not stakeholder volume<\/span>
<\/p><\/li><\/ul>Continuous Discovery<\/span>
<\/p>Maintain weekly customer/user contact\u2014you cannot delegate understanding your customers<\/span>
<\/p><\/li>Run rapid experiments and prototypes to validate (or kill) ideas before they hit the backlog<\/span>
<\/p><\/li>Partner with design and engineering to explore solution space before committing to build<\/span>
<\/p><\/li>Continuously develop PRDs for validated opportunities, building a pipeline of ready candidates for quarterly roadmap planning<\/span>
<\/p><\/li><\/ul>Product Strategy<\/span>
<\/p>Define and communicate Emalify's product vision and how it connects to Roamtech's portfolio strategy<\/span>
<\/p><\/li>Own competitive and market intelligence for the communications/CPaaS space in East Africa<\/span>
<\/p><\/li>Identify new opportunities through market analysis, not just react to feature requests<\/span>
<\/p><\/li><\/ul>Team Collaboration<\/span>
<\/p>Partner with the Engineering Lead as co\-leaders of your product team<\/span>
<\/p><\/li>Maintain continuous communication and partnership with the Engineering team members while negotiating Sprint capacity in order to balance between Product and Engineering needs<\/span>
<\/p><\/li>Work with Design to ensure solutions are usable and desirable<\/span>
<\/p><\/li>Shield the team from distraction while keeping them connected to customer reality<\/span>
<\/p><\/li><\/ul>Stakeholder Management<\/span>
<\/p>Translate business needs into product strategy without becoming an order\-taker<\/span>
<\/p><\/li>Communicate roadmap as a strategy document, not a promise of features by dates<\/span>
<\/p><\/li>Say "no" with data and rationale when requests don't align with outcomes<\/span>
<\/p><\/li><\/ul>
<\/div>Key Performance Indicators<\/span>
<\/h3>Product Value & Impact (Primary)<\/span>
<\/p>ROI on Product Initiatives: Measured business impact vs. investment for shipped work<\/span>
<\/p><\/li>Feature Adoption: % of target users actively using new capabilities within 90 days<\/span>
<\/p><\/li>Churn Reduction / Retention Improvement: Measurable uplift attributable to product changes<\/span>
<\/p><\/li>Revenue Impact: Contribution to ARPU, new revenue streams, or cost reduction<\/span>
<\/p><\/li><\/ul>Discovery & Validation<\/span>
<\/p>Discovery Velocity: Number of customer problems validated or invalidated per quarter<\/span>
<\/p><\/li>Experiment Completion Rate: % of planned experiments/prototypes executed before full build<\/span>
<\/p><\/li>Customer Contact: Minimum weekly direct customer/user interactions maintained<\/span>
<\/p><\/li><\/ul>Delivery & Execution<\/span>
<\/p>Outcome and Roadmap Delivery Rate: % of quarterly outcome targets achieved and % of the roadmap items delivered<\/span>
<\/p><\/li>Time\-to\-Learning: Average time from hypothesis to validated insight<\/span>
<\/p><\/li>Release Quality: Post\-release defect rate and rollback frequency<\/span>
<\/p><\/li><\/ul>Stakeholder & Team Leadership<\/span>
<\/p>Stakeholder Alignment: Quarterly satisfaction rating from commercial, engineering, and executive peers<\/span>
<\/p><\/li>Team Clarity: Engineering team's self\-reported understanding of product direction (quarterly pulse)<\/span>
<\/p><\/li>PO Mentorship: Development progress of junior/mid POs under guidance<\/span>
<\/p><\/li><\/ul>Product Quality & Stability<\/span>
<\/p>Product Uptime / Reliability: % availability against SLOs<\/span>
<\/p><\/li>Technical Health: Trend in tech debt tickets (decreasing backlog, not % allocation)<\/span>
<\/p><\/li><\/ul>
<\/div>Requirements<\/span>
<\/h3>Must have:<\/span>
<\/p>5+ years in product roles with demonstrated ownership of business outcomes<\/span>
<\/p><\/li>Evidence of discovery work: customer research, experimentation, prototype validation<\/span>
<\/p><\/li>Experience with B2B or platform products (APIs, integrations, developer experience a plus)<\/span>
<\/p><\/li>Ability to articulate product strategy and defend prioritization decisions<\/span>
<\/p><\/li>Track record of working <\/span>with<\/span> engineering, not just handing off specs<\/span>
<\/p><\/li>Bachelor's degree in CS or a related field<\/span>
<\/p><\/li><\/ul>Strong preference:<\/span>
<\/p>Experience in communications, CPaaS, or adjacent fintech/telecom<\/span>
<\/p><\/li>Familiarity with East African or emerging market dynamics<\/span>
<\/p><\/li>Exposure to pricing strategy, packaging, or monetization decision<\/span>
<\/p><\/li>Experience in Design Thinking and modern product discovery frameworks<\/span>
<\/span><\/p><\/li><\/ul>Nice to have:<\/span>
<\/span><\/p>CSPO certification or any BA/PM\-related ones.<\/span>
<\/p><\/li>Certified Scrum Master<\/span>
<\/p><\/li><\/ul><\/span>
<\/p>
You will own product outcomes for Emalify, Roamtech's communications platform. This means you're accountable for solving real customer problems in ways that work for the business\u2014not just shipping features on schedule.<\/span> You'll lead continuous product discovery to identify the right problems to solve, validate solutions before committing engineering resources, and measure success by business impact rather than delivery velocity.<\/span> This is not a project management role. You'll work with an empowered engineering team, not direct them. You're expected to bring deep knowledge of customers, the market, and the business to inform what gets built.<\/span> Product Outcomes<\/span> Define and deliver against quarterly business outcomes (e.g., reduce churn by X%, increase ARPU by Y%) rather than feature lists<\/span> Accountable for Emalify's contribution to Roamtech's strategic objectives<\/span> Make hard prioritization calls based on impact, not stakeholder volume<\/span> Continuous Discovery<\/span> Maintain weekly customer/user contact\u2014you cannot delegate understanding your customers<\/span> Run rapid experiments and prototypes to validate (or kill) ideas before they hit the backlog<\/span> Partner with design and engineering to explore solution space before committing to build<\/span> Continuously develop PRDs for validated opportunities, building a pipeline of ready candidates for quarterly roadmap planning<\/span> Product Strategy<\/span> Define and communicate Emalify's product vision and how it connects to Roamtech's portfolio strategy<\/span> Own competitive and market intelligence for the communications/CPaaS space in East Africa<\/span> Identify new opportunities through market analysis, not just react to feature requests<\/span> Team Collaboration<\/span> Partner with the Engineering Lead as co\-leaders of your product team<\/span> Maintain continuous communication and partnership with the Engineering team members while negotiating Sprint capacity in order to balance between Product and Engineering needs<\/span> Work with Design to ensure solutions are usable and desirable<\/span> Shield the team from distraction while keeping them connected to customer reality<\/span> Stakeholder Management<\/span> Translate business needs into product strategy without becoming an order\-taker<\/span> Communicate roadmap as a strategy document, not a promise of features by dates<\/span> Say "no" with data and rationale when requests don't align with outcomes<\/span> Product Value & Impact (Primary)<\/span> ROI on Product Initiatives: Measured business impact vs. investment for shipped work<\/span> Feature Adoption: % of target users actively using new capabilities within 90 days<\/span> Churn Reduction / Retention Improvement: Measurable uplift attributable to product changes<\/span> Revenue Impact: Contribution to ARPU, new revenue streams, or cost reduction<\/span> Discovery & Validation<\/span> Discovery Velocity: Number of customer problems validated or invalidated per quarter<\/span> Experiment Completion Rate: % of planned experiments/prototypes executed before full build<\/span> Customer Contact: Minimum weekly direct customer/user interactions maintained<\/span> Delivery & Execution<\/span> Outcome and Roadmap Delivery Rate: % of quarterly outcome targets achieved and % of the roadmap items delivered<\/span> Time\-to\-Learning: Average time from hypothesis to validated insight<\/span> Release Quality: Post\-release defect rate and rollback frequency<\/span> Stakeholder & Team Leadership<\/span> Stakeholder Alignment: Quarterly satisfaction rating from commercial, engineering, and executive peers<\/span> Team Clarity: Engineering team's self\-reported understanding of product direction (quarterly pulse)<\/span> PO Mentorship: Development progress of junior/mid POs under guidance<\/span> Product Quality & Stability<\/span> Product Uptime / Reliability: % availability against SLOs<\/span> Technical Health: Trend in tech debt tickets (decreasing backlog, not % allocation)<\/span> Must have:<\/span> 5+ years in product roles with demonstrated ownership of business outcomes<\/span> Evidence of discovery work: customer research, experimentation, prototype validation<\/span> Experience with B2B or platform products (APIs, integrations, developer experience a plus)<\/span> Ability to articulate product strategy and defend prioritization decisions<\/span> Track record of working <\/span>with<\/span> engineering, not just handing off specs<\/span> Bachelor's degree in CS or a related field<\/span> Strong preference:<\/span> Experience in communications, CPaaS, or adjacent fintech/telecom<\/span> Familiarity with East African or emerging market dynamics<\/span> Exposure to pricing strategy, packaging, or monetization decision<\/span> Experience in Design Thinking and modern product discovery frameworks<\/span> Nice to have:<\/span> CSPO certification or any BA/PM\-related ones.<\/span> Certified Scrum Master<\/span>
<\/p>
<\/p>
<\/p>Key Responsibilities<\/span>
<\/h3>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/div>Key Performance Indicators<\/span>
<\/h3>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/div>Requirements<\/span>
<\/h3>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li><\/ul>
<\/p>
<\/p><\/li>
<\/p><\/li>
<\/p><\/li>
<\/span><\/p><\/li><\/ul>
<\/span><\/p>
<\/p><\/li>
<\/p><\/li><\/ul><\/span>