← All speakers

Bio, Work & Ideas

Daniel Wirjo

Conference affiliation: Amazon Web Services (AWS) · 2026

Daniel Wirjo is a solutions architect at Amazon Web Services and former startup chief technology officer who helps AI, fintech, and software companies build production systems. His specialty is production-ready voice agents: conversational interfaces whose effectiveness depends on timing, streaming infrastructure, speech recognition, and operational control.

His earlier work addressed event-driven data architecture, safer software releases, and tenant routing for SaaS applications. In 2025, he co-authored technical accounts of AI-assisted lending at Rich Data Co and machine-learning workflows at Australian lender Lumi. He also helped introduce Amazon CloudFront SaaS Manager, explaining how multi-tenant edge delivery can support customer-specific domains and security settings on shared infrastructure.

By 2026, Wirjo was applying that production-oriented perspective to specialized speech recognition and Pipecat voice agents on Amazon Bedrock AgentCore. His approach centers on three practical questions:

  • Conversational turn-taking: An assistant must distinguish a completed thought from a hesitation. In a live voice-agent demonstration, Wirjo compared silence detection, speech-provider endpointing, and locally controlled turn classification, showing why combining classification with a silence-based safeguard prevents indefinite waiting.
  • Inspectable voice infrastructure: Local turn-detection models expose decisions through debugging output and give teams greater control over customization, deployment, and compliance. Production choices also encompass WebSockets, WebRTC, session isolation, scaling, and protected credentials.
  • Application-specific voice architecture: Wirjo has compared integrated speech-to-speech systems with cascaded pipelines that separately control transcription, language-model reasoning, and speech synthesis. Domain-adapted recognition becomes especially important when an agent must understand specialized vocabulary.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

A voice agent needs to know when to speak and when to stop. Three Pipecat configurations show how silence timers, provider events and local turn models make those decisions.

  • The same correction, two different conversations
    1:44 ↗
  • Why a short delay feels long
    2:37 ↗
  • Turn-taking surrounds the generation pipeline
    3:54 ↗
  • Level one: let silence end the turn
    5:17 ↗
  • Level two: let the STT provider signal completion
    8:27 ↗
  • Level three: a local model with a silence safety net
    9:55 ↗
  • Fast cancellation still needs an intent decision
    11:35 ↗
  • Three configurations of the same Python pipeline
    13:14 ↗
  • Where the response budget goes
    14:55 ↗
  • A fast median cannot hide a slow conversational turn
    18:16 ↗
  • Turn errors become operational problems
    19:56 ↗
  • A travel assistant makes the policy visible
    21:46 ↗
  • The silence timer mistakes hesitation for completion
    25:01 ↗
  • The provider waits for Sydney
    26:21 ↗
  • The logs distinguish model completion from a timeout
    29:30 ↗

References