Browse current jobs

Senior Technical Product Manager

Exotel Techcom Pvt Ltd · Bangalore

Apply on employer website

Collected role description

Role overview

Senior Technical Product Manager at Exotel Techcom Pvt Ltd

This Role May Be a Strong Fit If You Are A senior or staff engineer considering a product move.

Responsibilities

  • Build ground-up product stories from customer signals, QBR data, competitive analysis and platform reality.

Employment details

  • Location: Bengaluru [Karnataka] [India]

Application details

  • If your technical depth is real and your appetite for product craft is genuine, apply and tell us how you are thinking about the transition.

About the employer

  • About Exotel Exotel is the operating system for business communications in emerging markets.

Additional role details

  • Every day, our platform powers the calls, messages and Voice AI interactions that connect a Bajaj agent to a customer, a Zomato delivery partner to a household, a HDFC banker to a borrower, and a Bolna voicebot to millions of end users.
  • We process billions of minutes and messages annually across India, Southeast Asia, the Middle East and Africa.
  • We are the substrate underneath one of the fastest-scaling contact centre and Voice AI ecosystems in the world.
  • Own the largest surface we run Voice powers thousands of enterprise deployments including HDFC, RBL and international BFSI accounts, and sits underneath the fastest-growing segment of our business: Voice AI.
  • It is also the most complex product surface we operate - ExoML APIs, the voice platform, throttling and traffic management, LeadAssist, recording infrastructure, K8S-based enterprise deployments and real-time telephony reliability across geographies.
  • This role is the product owner for that surface.
  • You define what gets built, why it matters and how success is measured, in close partnership with our Engineering leadership and the go-to-market team.
  • If you want an environment where technical depth is respected, product craft is expected, and the roadmap has real revenue and enterprise weight behind it, this is that seat.
  • What You Will Own Platform strategy and roadmap - outcomes, sequencing, and trade-offs across a 12-18 month horizon.
  • You are not processing inbound requests.
  • Platform APIs and payload surface - including AMD, recording status callbacks, disconnectedBy, throttling APIs, and the next generation of programmable platform primitives.
  • Enterprise platform deployments Cross-product platform integrations - with platformbot, CQA, contact centre, and streaming.
  • The developer and enterprise customer experience - including QBR ownership on top 20 accounts and Developer NPS >45 across the API surface.
  • Build ground-up product stories from customer signals, QBR data, competitive analysis, and platform reality - not just processing inbound requests.
  • What We’re Looking For We care more about what you have actually owned than your previous title.
  • You have ideally: Built real systems as an engineer, and now want to own the product decisions behind them.
  • Spent at least 3-4 years operating in technically complex domains - CPaaS, telephony, developer platforms, API-first products, data infrastructure or equivalent.
  • Read system design docs, held your own in a review with a staff engineer, and known when an engineering estimate is soft.
  • Written PRDs engineers actually reference.
  • Done real discovery and built user stories from first principles.
  • Defended prioritisation with data.
  • Taken vague mandates and converted them into executable roadmaps without heavy hand-holding.
  • Committed publicly and held yourself accountable, including to slips.
  • Known when to move fast and when to wait, when to be direct and when to be diplomatic, when to hold a scope and when to renegotiate.
  • We have seen this path produce some of the best technical PMs in our space.
  • A product manager from a CPaaS-adjacent developer platform - auth, messaging, payments, analytics infrastructure.
  • The domain-specific telephony knowledge can be built.
  • The platform thinking and API-product craft cannot.
  • This is probably not the right role if: Your experience is primarily roadmap execution and processing inbound requests.
  • You have not worked in a technically complex domain and do not want to start.
  • You need a well-defined mandate and close supervision to make progress.

Collected experience requirement

3-4 years