Telephony Engineer

Job Description

MyOperator's Telephony platform powers call handling, IVR routing, number/DID provisioning, and outbound dialer campaigns for over 12,000 businesses. We're looking for a Product Manager to own this domain - someone with genuine technical depth in telephony and voice systems, who can translate how these systems actually work into a clear, well-sequenced roadmap and partner closely with engineering to ship it.

This is a technical, hands-on role suited to a PM who understands the mechanics of telephony infrastructure - call routing strategies, IVR state machines, DID lifecycle management, SIP/Asterisk-based call systems and can write specs that hold up against how these systems are actually built, not just how they appear on the surface.

About MyOperator

MyOperator is a Business AI Operator platform that allows businesses, teams, and AI Agents to work in tandem for customer operations, i.e., handle Sales, Support, Escalation, Feedback, and Refund processes. With over 12,000+ businesses using our platform, we are the largest in the space.

MyOperator is built for people who want to work on ambitious problems at a meaningful scale. We value ownership, speed, critical thinking, and a bias for building things that create real customer and business outcomes. This is a high-expectation, high-learning environment where people are trusted to think independently, challenge ideas openly, move with urgency, and keep raising the bar as we build for long-term impact.

Key Responsibility Areas

• Own the Telephony product roadmap end-to-end - call handling, IVR/routing, DID provisioning, and outbound dialer campaigns - writing specs grounded in real system architecture and partnering closely with engineering to ship them.
• Maintain delivery visibility and alignment across the roadmap, using tools like Jira to track progress, sequence dependencies, and keep priorities clear for engineering.

Requirements — Must Have

• Strong technical understanding of telephony and voice infrastructure - IVR call flows and state machines, call routing strategies (round robin, simultaneous, sequential), SIP/Asterisk-based call systems, and DID/number provisioning and lifecycle management.
• 4+ years as a Product Manager/Product Owner on a technical or infrastructure-heavy product (telephony, VoIP, messaging/CPaaS, or a comparably systems-heavy backend domain), with end-to-end ownership of a roadmap you can speak to in specifics.
• Demonstrable ability to read and reason about backend system design - can point to specs/PRDs you've written that account for real constraints like state machines, REST APIs, webhooks, or rate limits, not just UI/wireframe-level requirements.
• Comfortable working within engineering's own tooling (e.g., Jira) to track delivery progress and dependencies as part of the regular workflow.
• Demonstrated ownership of predictable, high-throughput delivery on a technical roadmap, with clear outcomes you can speak to.

Requirements — Good to Have

• Experience working with voice agents/voicebots (e.g., AI-driven call handling, IVR-to-bot handoff, conversational voice systems) — a strong plus given where our roadmap is headed.
• Experience with WhatsApp Business API or other messaging platforms.
• Prior exposure to outbound dialer / campaign-calling systems (OBD).
• SQL or basic scripting ability to work directly with product/ticket data.
• Prior experience at a CPaaS, UCaaS, or contact-center software company.

This profile is not for

• Candidates who prefer to operate purely at the conceptual/strategy level without engaging with system architecture or engineering-level detail.
• Candidates who aren't comfortable using ticket-tracking tools as part of their regular workflow to track delivery and dependencies.
• Candidates without genuine, hands-on exposure to telephony systems or comparably complex technical infrastructure