← All speakers

Bio, Work & Ideas

Angie Jones

Conference affiliation: Agentic AI Foundation · 2026

Angie Jones is vice president of developer experience at the Agentic AI Foundation, where she advances open standards and practical engineering methods for autonomous software. An IBM Master Inventor with more than 25 patented inventions, she created Test Automation University and now applies decades of experience in software reliability, developer education, and organizational change to agentic systems.

From automation engineer to agentic infrastructure

Jones initially studied business at Tennessee State University before a programming course redirected her toward computer science. She began her engineering career at IBM, earned its Master Inventor designation, and later worked in automation roles at companies including Teradata, LexisNexis, and Twitter. Her patents span virtual worlds, collaboration software, social networking, and software-development processes.

At Applitools, she moved into developer advocacy and created Test Automation University, a free platform teaching programming and automated testing. Her public Java programming exercises and hybrid automation framework extend that educational work into inspectable, reusable code.

At Block, Jones led company-wide AI enablement across functions including engineering, marketing, design, finance, and legal. Confronting the gap between widespread coding-assistant use and actual delivery improvements, she established an AI champions program of approximately 50 engineers. Participants prepared repositories with context files, guardrails, reusable workflows, automated review, and attribution practices tailored to different engineering environments. Those foundations enabled teams to delegate work through Slack and issue trackers, run agents in isolated cloud workspaces, and coordinate changes across repositories. Her account of scaling agent adoption emphasizes organizational readiness over raw tool usage.

At the Linux Foundation-hosted Agentic AI Foundation, Jones supports open agent interoperability across technologies including the Model Context Protocol, AGENTS.md, and goose. Her mcp-selenium project connects that mission to her automation background by making Selenium WebDriver available to AI agents.

  • Systems before prompts. Jones designs agents as components within larger systems of tools, workflows, data, and human oversight. Her Relocation Scout house-hunting agent separates listing normalization, neighborhood research, commute calculations, structured output, and approval decisions; explicit state tracking and idempotent retries help interrupted workflows recover safely.
  • Deterministic code, model judgment, human authority. Exact calculations belong in conventional scripts, ambiguous interpretation can go to models, and consequential actions require human approval. Jones treats outside content as untrusted input and restricts agent permissions to limit potential harm.
  • Structured, persistent agent memory. Her agent-memory architecture adapts Andrej Karpathy’s LLM-wiki pattern into queryable knowledge, durable action histories, and schema-governed updates that survive individual sessions.
  • Agent evaluation grounded in testing discipline. Her test pyramid for AI agents combines deterministic unit tests, recorded interactions, repeated benchmarks, and rubric-based assessment to make nondeterministic behavior measurable without turning ordinary continuous integration into unstable live-model testing.

Jones also examines automation’s human consequences: engineering gains and increasingly autonomous delivery cannot be evaluated independently of their effects on workers.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

A house-hunting agent shows where software engineering moves when models write the code: workflows, component boundaries, durable memory, safe retries, and human authority.

  • Finding the pleasure of building again
    0:00 ↗
  • A house search outlasts a prompt
    1:15 ↗
  • Give the goal a path
    2:57 ↗
  • Find the jobs hiding in the prompt
    4:06 ↗
  • Reuse the capability, not every instruction
    7:50 ↗
  • Assign determinism, judgment, and authority
    9:26 ↗
  • Turn an assessment into a durable contract
    11:04 ↗
  • Retry only the unfinished work
    13:01 ↗
  • Separate evidence from permission
    15:30 ↗
  • Make the system understandable from a cold start
    17:07 ↗

Key ideas

Scroll to read ↓

Block’s engineers were already using AI, but features were not reaching customers faster. Changing that required repository preparation, native delegation, review automation, and shared context across services.

  • High adoption without faster delivery
    0:00 ↗
  • From assistance to directing work
    1:52 ↗
  • Give a small group the time to build shared practices
    4:18 ↗
  • Make repositories ready for delegation
    6:44 ↗
  • Delegate where the work already arrives
    9:54 ↗
  • Bring agents into the sprint
    11:37 ↗
  • Parallel agents expose the review bottleneck
    12:49 ↗
  • Give each agent an isolated workspace
    14:18 ↗
  • Plan across repositories with a company world model
    15:07 ↗
  • What is the organization becoming?
    16:47 ↗

References