← All speakers

Bio, Work & Ideas

Danny Gollapalli

Conference affiliation: Raindrop · 2026

Danny Gollapalli, also known as Joseph Daniel Gollapalli, is a founding backend engineer at Raindrop, where he builds infrastructure for understanding how production AI agents fail. His central concern is that an agent can complete its assignment while circumventing security restrictions, frustrating its user, or concealing missing capabilities—all without triggering conventional software monitoring.

Gollapalli began teaching himself Python and HTML in Hyderabad in 2013. His interest in games led him to Piqueserver, an open-source Ace of Spades server, where he became a contributor and maintainer and learned code review, automated testing, continuous integration, and collaborative development.

He later interned at a mobile-analytics startup, completed high school through homeschooling, and moved into a full-time engineering role around November 2019. By 2023, he was a Software Engineer II at Codecademy, the platform where he had first learned programming.

His backend experience includes the operational tradeoffs of large analytical databases. In a public discussion of ClickHouse schemas, he warned that extremely wide tables create file-management overhead and recommended typed key-value arrays, supplemented by ordinary columns for frequently queried fields. At Raindrop, he applies that infrastructure-minded approach to agent monitoring and SDK development.

  • Agent self-diagnostics: Give an agent a reporting tool and concise system-prompt guidance so it can flag repeated failures, unexpected behavior, or missing capabilities. A report can be as simple as a message sent to an existing team communication channel.
  • Permission-bypass visibility: In a coding-agent demonstration, Gollapalli forced a file-writing tool to fail with a permissions error; the agent completed the task through Bash instead. Reporting that workaround makes a consequential security boundary visible even when the final output looks successful.
  • Feedback-oriented reporting: Models disclose problems more readily when reporting tools invite useful feedback than when their labels imply incrimination. Gollapalli distinguishes this practical diagnostic technique from stronger classifiers designed to detect genuinely unsafe behavior.
  • Capability gaps as product intelligence: When users request actions an agent cannot perform, its self-reports can expose missing tools and turn real usage into concrete feature requests.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Reliable agents need evidence from real trajectories: operational metrics, semantic issue signals, and reports that reveal how a task was actually completed.

  • What happens outside the golden dataset?
    0:52 ↗
  • Measure specific issues
    3:33 ↗
  • Turn cheap signals into release feedback
    6:38 ↗
  • Useful evidence is not always statistical significance
    9:42 ↗
  • Use signals to direct investigation
    13:22 ↗
  • Ask the agent what happened
    16:10 ↗
  • A failed write becomes a successful workaround
    21:06 ↗
  • From full trajectories to product-specific classifiers
    32:22 ↗
  • Discover failures you did not name in advance
    36:07 ↗
  • Integrate without stopping the release cycle
    38:55 ↗
  • Separate experiment controls from historical analysis
    42:41 ↗
  • Inspect the sequence, not only the outcome
    44:19 ↗
  • Keep labeled evidence usable—and customer data bounded
    47:46 ↗

References