Engineering Manager II - Phone Core

HighLevel is an AI-powered business operating system that gives agencies, entrepreneurs and SMBs the infrastructure to build, automate and scale. With 2,000+ team members across 10+ countries, the company operates as a global, remote-first organization supporting over 1 million businesses across 150+ countries. The platform processes over 15 billion API hits and 2.5 billion message events daily, powering more than 1.5 billion messages, 200 million leads and 20 million conversations monthly. Behind this, the architecture includes 250+ microservices, 250 terabytes of distributed data, and 1+ million domain names. We're proud to be a part of helping real people build independence, expand opportunity and create measurable impact. We're looking for an Engineering Manager to lead our Phone Core teams—the mission-critical foundation of HighLevel's communication stack. This group owns the CPaaS platform layer, Phone Billing, Trust & Compliance, and phone number provisioning, serving as the substrate every other channel team builds upon. The platform handles 100M+ events daily across 15+ services, with LC Phone being a major contributor to HighLevel's revenue where uptime and reliability are paramount. As an Engineering Manager, you'll lead multiple squads (10+ engineers) across these domains, own architecture and delivery for the CPaaS platform layer, and partner with PMs and Staff Engineers to keep a revenue-critical system correct, compliant, and exceptionally fast at a scale few companies ever reach. Two areas carry outsized leverage: Phone Billing meters and monetises usage for the entire Phone and WhatsApp business—every call, message and number rides through it, so correctness, idempotency and reconciliation are not optional; a rating bug is a revenue and trust incident at the same time. Trust & Compliance is the gate that determines whether customers can send at all: 10DLC and toll-free registration, brand and campaign vetting, carrier filtering, DLT and regional regimes. Regulators and carriers change the rules continuously, so the real engineering problem is designing flexible, rules-driven systems that absorb policy change without a rewrite each time.