Plivo runs a messaging platform moving over 10,000 messages per second across 226 countries and 1,600 carriers. You will lead the team behind the messaging APIs: SMS, MMS, WhatsApp, RCS and Verify. This is a hands-on role - roughly 70 percent coding, architecture first, mentoring 3-5 engineers second.
What you will do: own the architecture of high-throughput message pipelines (API ingestion, routing, queuing, rate limiting, retries, DLR processing); own carrier and aggregator integrations over SMPP and HTTP including failover, routing logic and delivery-quality instrumentation; set technical direction through design reviews and service contracts; own operational health - SLOs, alerting, capacity planning, on-call and RCA; build for carrier and regulatory compliance (10DLC, toll-free, DLT, sender IDs, opt-out handling) and traffic quality against spam and SMS pumping; mentor 3-5 engineers through code and design reviews.
What we are looking for: 4-7 years building large-scale distributed backend systems with demonstrated technical leadership or mentoring; proficiency in Python or Golang (strong Java or Node.js considered); RESTful, high-throughput, highly available microservices; async messaging infrastructure (Kafka, SQS, RabbitMQ) plus idempotency, backpressure, rate limiting and retries; good concurrency aptitude; solid PostgreSQL or MySQL with caching or NoSQL exposure (Redis, DynamoDB); hands-on AWS (EC2, S3, RDS, SQS, ECS, Lambda) and containerised deployments, Git and one CI/CD system; strong production ownership - observability, tracing, debugging live systems, leading on-call.
Good to have: CPaaS, telecom or A2P messaging domain experience (SMPP, WhatsApp Business API, RCS, 10DLC, DLT); least-cost routing, deliverability analytics, or fraud and traffic-quality systems.
_1548133325694.png){kind=logo}