Senior Solution Architect
Location: USA, Remote
Duration: 12 months
Key Skills: Twilio Platform Expertise, .NET (C# / ASP.NET Core), AWS, Healthcare Domain
We are seeking a Principal Voice Platform Engineer to serve as our primary subject matter expert (SME) for Twilio-based telephony architecture on enterprise healthcare communication programs. This is a senior individual-contributor and technical leadership role — you will not just build systems, you will define the architecture that all migration engineers follow.
You will be the go-to expert for designing, validating, and governing Twilio Voice SDK, Twilio Studio, WebHooks and TwiML orchestration solutions at scale — including patterns and techniques that go well beyond what is documented in Twilio''s public SDK guides. Your work directly enables healthcare organizations to migrate off end-of-life telephony infrastructure (Genesys PureConnect, Cisco, Avaya) onto modern cloud-native Twilio+.NET platforms without clinical disruption.
What You''ll Do
Architecture & Design (Primary):
- Own the end-to-end Twilio platform architecture for healthcare communication migration programs, including inbound call path design, Studio Flow topology, TwiML webhook orchestration, and carrier-layer configuration
- Define and enforce the "Thin Studio, Smart API" architectural pattern — governing which logic lives in Twilio Studio vs. the .NET Voice API backend — across all delivery teams
- Design the shared infrastructure services that all milestone teams consume: Redis-backed Call Session Store, CloudFront CDN audio serving, carrier redundancy configurations, and Twilio webhook reliability patterns
- Architect Twilio solutions for complex multi-tenant IVR systems with 500+ simultaneous call flows, including multi-level DTMF menus, ASR (speech recognition) workflows, on-call routing chains, and call transfer sequences
What We''re Looking For
Required — Twilio Platform Expertise
- 5+ years hands-on production experience with Twilio Programmable Voice, Twilio Studio, and TwiML — at enterprise scale (not just POC or sandbox)
- Deep, working knowledge of Twilio Studio Flow design: execution model, widget types, HTTP Request widget limitations, execution step limits, and the conditions under which Studio is and is not the right tool for a given problem
- Expert-level TwiML authoring and the interaction between TwiML verbs and Twilio''s execution model under load
- Production experience with Twilio Webhook architecture: signature validation, async response patterns (to handle the 15-second hard timeout), status callbacks, recording callbacks, and idempotent webhook handlers
Required — Architecture & Engineering
- 3+ production Twilio migrations led from end-of-life on-premises telephony (Genesys, Cisco, Avaya, or equivalent) to Twilio-based cloud architecture — you have personally designed and delivered the target-state architecture, not just contributed to one
- Strong proficiency in .NET (C# / ASP.NET Core) for Twilio Voice API backend services: webhook controllers, TwiML response generation, Twilio SDK usage, and integration with Redis for call session state
- Experience designing and operating Redis-backed distributed state management for stateless webhook systems — specifically maintaining call context (ANI, DNIS, IVR selections, transfer history) across multiple webhook hops within a single call
- Familiarity with AWS audio serving patterns for IVR: S3 object hosting, CloudFront CDN configuration, cache-warming strategies, and pre-signed URL generation for HIPAA-compliant prompt file access
- Experience with multi-tenant IVR architecture at scale: 500+ simultaneous call flows, shared routing infrastructure, per-tenant configuration, and isolation patterns
Required — Healthcare Domain
- Healthcare communications experience — you understand the unique requirements of clinical telephony: on-call escalation chains, provider routing (not just ACD), clinical SLA expectations, and the patient safety implications of call routing failures
- Working knowledge of HIPAA requirements as they apply to telephony: PHI in call metadata, call recording consent workflows (HITECH), audit trail requirements, and the difference between a HIPAA-compliant architecture and a compliant implementation
- Experience designing for 24/7 mission-critical uptime in clinical environments — where a routing failure is not a business inconvenience but a potential patient safety event
Never miss an opportunity! Create an alert based on the job you applied for.
