▶ Watch ↗AI Engineer World's Fair 202616:23
Conference affiliation: Twilio · 2026
Kanish Manuja builds production LLM gateways and conversational-AI infrastructure for customer-facing applications. A principal engineer at Twilio at the time of AI Engineer World’s Fair 2026, he focuses on the engineering choices that keep those applications useful when models are slow, providers fail, or safeguards become unavailable. His work connects distributed systems with the practical demands of conversation: responsiveness, reliable instructions, retained context, and manageable cost.
Manuja studied computer science and engineering at the Indian Institute of Technology Kanpur, graduating in its 2015 dual-degree cohort. That year, he co-authored research on social connections in recommendation systems with Arnab Bhattacharya. Their approach incorporated friendship and trust relationships into matrix-factorization-based collaborative filtering, examining whether social relationships could improve rating predictions beyond conventional preference matching.
By August 2019, he was a software engineer at Microsoft, working on OData developer infrastructure. His writing on continuation-token pagination addressed a subtle reliability problem: offset-based pagination can repeat records when deletions change a dataset between requests. Continuation tokens preserve ordering information so the next request can resume from the preceding page’s position. He also described how developers could customize token generation and application.
His later work at Twilio brought language models into customer-service workflows. Manuja is one of eight named inventors on a patent application for asynchronously generated customer summaries, filed in 2024 and published in 2025. The proposed system retrieves customer traits and event history, generates a concise summary with a language model, and supplies that context to a human agent alongside an incoming communication request. It addresses how generated information reaches an agent within an existing service interaction; the application describes a proposed system rather than an established deployment.
A restaurant voice-agent prototype gave Manuja a concrete way to examine the tradeoffs in conversational AI. In his account of the experiment, a realtime approach improved response latency, but instruction adherence and conversational-context behavior were weaker, and cost was higher. Drawing on that experience, he recommended separate speech-to-text, language-model, and text-to-speech stages for most production use cases and advised avoiding realtime voice-native models for the time being. His recommendation extended beyond the prototype: faster responses did not, in his assessment, outweigh the difficulties of maintaining consistent behavior and context at higher cost. This was his time-bound judgment about production readiness, rather than an established verdict on every realtime voice system.
Manuja treats a gateway as middleware between applications and model providers, responsible for routing, authentication, fallbacks, rate limits, and governance. His approach to gateway architecture revolves around four competing objectives: availability, latency, guardrails, and cost. When a dependency degrades, teams cannot maximize all four. Gateway designers should give applications the controls to choose an acceptable response for their particular use case.
Across his voice-agent experiments and gateway designs, Manuja pays attention to what happens when an apparently attractive technical choice meets an actual workload. Lower latency can come with weaker conversational behavior; provider redundancy can fail without tested backup capacity; a safeguard can become the service that holds up every request. His work makes those consequences explicit so application teams can choose the behavior their customers need.
▶ Watch ↗AI Engineer World's Fair 202616:23
Loading more talks and highlights…