About The Role

Cinch is a Series-A startup making technology more accessible across Southeast Asia. People can subscribe to the devices they need instead of buying them outright — and we use circularity as the vehicle for aligning economic incentives with environmental impact. When devices flow through subscription, refresh, refurb, and redeployment cycles, we keep them out of landfill and make them more affordable in the same motion.

The model only works at scale if we can manage devices well across their entire lifecycle. That's where this role comes in.

Mobile Device Management (MDM) is the backbone of how we do that — device lifecycle management, configuration, and policy control. It safeguards the integrity of our asset book today, and it's the foundation for a B2B revenue line: offering MDM as a managed service to other operators in the region.

This role owns that surface.

Impact & Opportunity

Two phases, both required. The capability underneath is the same — fleet management infrastructure that secures, configures, and manages devices at scale. The end users are different: Phase 1 is for both our B2C customers and our own ops teams managing Cinch's subscription fleet; Phase 2 is external B2B customers using the same underlying tech for their own use cases (which won't look like ours).

Phase 1 — Immediate operational impact

Improve the on-the-ground leverage and systems around MDM orchestration. Strengthen device lifecycle workflows and policy enforcement. Build internal tooling so ops teams can manage MDM at scale without engineering involvement, while improving customer experience. Drive cost-per-device down.

Phase 2 — Build the commercial opportunity

Take what we've built internally and productize it as a managed-service MDM offering for B2B customers. Land an alpha customer. Define the abstraction layer that lets external partners use Cinch's MDM infrastructure without us re-architecting for every deal. Lay the foundation for a standalone B2B product unit.

What You'll Own

Across both phases, the shape of the work is the same: validate the need, design what the product offering actually is, then partner with engineering to build the tools that deliver it. Less "manage someone else's roadmap," more "figure out what we're building, why, and for whom — then ship it." Some projects will be new builds, while some will require heavy iteration and optimization.

Phase 1 anchors

• Device lifecycle workflows: configuration, policy enforcement, state transitions.
• MDM cost optimization: vendor utilization, license consolidation, infra spend.
• MDM orchestration automation: Improve and innovate on ways to automate MDM to improve operational processes and address customer painpoints.
• Internal admin tooling: self-serve control for ops without engineering tickets.
• The data contract between MDM events and downstream systems — billing, risk, logistics.
  
  

Phase 2 anchors

• Validate B2B need: discovery interviews, prospect conversations, sharpen what the offering actually solves and who it's for.
• Productize MDM-as-a-managed-service: SKU, pricing, integration model, positioning.
• Partner discovery and alpha customer onboarding alongside the commercial team.
• The abstraction between Cinch's internal MDM infrastructure and what external partners consume — admin portals, fleet dashboards, API surface.
  
  

Constant

• Cross-functional connective tissue across engineering, risk/collections, and B2B teams on anything touching device management.
• Multi-market product thinking — SG, MY, and upcoming markets each have their own regulatory, operational, and partner nuances.
  
  

Reporting & collaboration

• Reports to the Senior Director of Product.
• Close collaboration with engineering, risk, collections, asset-ops, and B2B teams.
• Operating model evolves with the phase — heavier risk/collections lean in Phase 1, heavier B2B lean in Phase 2.
  
  

You'll do well here if you have

Must-haves

• 5+ years in product management, with 2+ owning technically complex platform or infrastructure products.
• Comfort designing with engineers — API contracts, state machines, event-driven systems. No code, but real systems thinking.
• Track record of owning measurable business outcomes, not just shipping features.
• Crisp written communication. PRDs, decision docs, exec updates — clean and tight.
  
  

Strong tilts (preferential, not gating)

• Direct MDM experience — you've worked with MDM infrastructure and understand how enrollment, policy enforcement, and remote management actually work.
• Or fintech / lending / subscription credit background — you understand operational levers and recovery economics in credit-exposed businesses.
• Bonus: you've taken an internal tool and productized it as an external offering before.
  
  

Nice-to-haves

• Southeast Asia operational exposure.
• Experience with eKYC, risk, or lifecycle workflows where device events trigger downstream actions.
• Active use of AI tools in your product workflow.
  
  

What You'll Walk Away With

• Ownership of a domain that directly moves Cinch's P&L and unlocks a new B2B revenue line.
• The seat closest to the intersection of hardware, software, and financial services at Cinch — structurally rare at this stage.
• Direct involvement in commercial deal-making as Phase 2 ramps up.
• A clear pathway to building and leading a standalone product unit as the commercial opportunity materializes.