← All speakers

Bio, Work & Ideas

Banjo Obayomi

Conference affiliation: Amazon Web Services (AWS) · 2025

Banjo Obayomi is a software engineer, solutions architect, and developer advocate who builds AI systems that operate browsers, interpret cloud infrastructure, and turn natural-language instructions into practical software workflows. His work spans reproducible data engineering, cybersecurity research, reinforcement learning, and the emerging architecture of autonomous web agents.

Obayomi earned computer science degrees from the University of Maryland, College Park, in 2011 and Loyola University Maryland in 2015. At Two Six Labs, where he became a senior research engineer, he developed serverless machine-learning applications, experimented with reinforcement learning for Unity’s Obstacle Tower Challenge, and built an automated AWS knowledge graph from technical documentation.

He also coauthored Magicwand, a research framework for generating reproducible, labeled datasets of low-and-slow distributed denial-of-service attacks. His O’Reilly contribution to 97 Things Every Cloud Engineer Should Know advocated reproducible data infrastructure, applying software-engineering practices such as automation and versioning to data pipelines. He also cohosted the DataOps Podcast.

By 2021, Obayomi was a senior developer advocate at Amazon Web Services. His subsequent work on AI-assisted solutions architecture explored systems capable of answering cloud questions, retrieving documentation, and generating infrastructure diagrams. His independently developed ChatAWS applied conversational AI to creating websites and AWS Lambda functions.

How he builds agents that take action

  • Natural-language browser automation: Using Amazon Nova Act, Obayomi designs agents that identify visible interface elements and navigate websites from written instructions. Demonstrations have compared products across parallel browser sessions and located highly rated coffee shops near a particular hotel.
  • Portable browser tools through MCP: He created a Model Context Protocol server exposing browser sessions, actions, screenshots, and parallel tasks as reusable tools. An external language model handles planning while Nova Act executes browser interactions; the same server can connect to different AI clients.
  • Multi-agent cloud architecture: With Strands Agents, he combines specialized architecture, pricing, and presentation agents to assemble migration recommendations, current cost estimates, diagrams, and executive-ready slides. His approach favors concise, code-first orchestration and reusable tools.
  • Practical limits on autonomy: Obayomi openly demonstrates failures involving CAPTCHAs, ambiguous instructions, stalled navigation, and unexpected browser state. He emphasizes detailed tool descriptions, execution logs, human intervention when needed, and workflows that respect security controls.

At AI Engineer World’s Fair 2025, he and Du’An Lightfoot brought these ideas together in a hands-on workshop on Nova Act, MCP, and Strands Agents, showing how agent systems can move from a written request to observable action while exposing their operational limitations.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Follow a browser agent from its planning loop to coffee-maker searches, MCP integration, and a multi-agent migration workflow, including the live failures that reveal where control and verification belong.

  • When does a task need an agent?
    1:39 ↗
  • From a ready-made assistant to a programmable agent
    4:40 ↗
  • Add browser actions, then prepare the workshop
    7:19 ↗
  • Search for a coffee maker without writing selectors
    16:16 ↗
  • Parallel searches expose a different set of limits
    23:36 ↗
  • Let an MCP client choose the browser operations
    31:57 ↗
  • A Wi-Fi query gets stuck at reCAPTCHA
    34:24 ↗
  • Combine documentation and diagram tools in Strands
    41:53 ↗
  • Choose managed agents or code-first composition
    47:18 ↗
  • Specify dependencies without prescribing every tool call
    48:49 ↗
  • More ambitious browser tasks need more precise control
    55:15 ↗
  • Try draw.io, then move the same server to Cursor
    1:03:08 ↗
  • Separate the planner, browser process, and cloud model
    1:11:05 ↗
  • Make browser actions and their results inspectable
    1:14:09 ↗
  • Use specialist agents as tools for a migration plan
    1:20:19 ↗
  • Architecture trouble, pricing lookups, and a deck still in progress
    1:23:34 ↗

References