# Ben McAdams — full content bundle > Senior engineer at Zapier, building agents. Everything on benmcadams.info in a single document. Individual pages remain available at their canonical URLs and via `.md` mirrors. --- # Resume URL: https://benmcadams.info/resume # Ben McAdams Senior engineer at Zapier, building agents. ## About Software engineer with 10+ years of industry experience. Passionate about building value-focused solutions. Empathy expert. ## Experience ### Senior Software Engineer, Product Growth — Zapier 2024-11 → present Driving growth through product engineering, developer experience, and AI discoverability. Focused on increasing Zapier's visibility to both humans and AI agents across the web. Tech DRI on cross-functional initiatives spanning experimentation, platform architecture, SEO, and agentic discovery. ### Senior Software Engineer, Developer Experience — GoFundMe 2023-03 → 2024-10 Full stack engineer on the developer experience team. - Paved the way for Kubernetes at Classy (acquired by GoFundMe) by standing up their first clusters and deploying production services to them using ArgoCD (GitOps) on AWS. - Engineered and deployed Backstage (open-source IDP) and integrated it into the everyday workflow of technical stakeholders — improving visibility into service health. ### Software Engineer II, Full Stack — Twitter 2022-07 → 2023-05 - Twitter 2.0 — lead engineer on Twitter Finance and Twitter Hashflags. Both products generated revenue and were sold as advertisement solutions on iOS, Android, and web. - Twitter 1.0 — delivered features and optimizations to the advertisement technology stack. Worked directly with the largest advertisers to translate requirements into backend decisions. ### Software Engineer II, Backend — Twitter 2019-06 → 2022-07 Designed, implemented, and maintained CI/CD pipelines used daily by 400+ mobile application developers. Migrated MacOS developer productivity infrastructure and CI workloads from on-premise to the cloud. Built tools across cloud platform services and multiple languages to improve engineering velocity. ### Software Engineer, Full Stack — SAP 2018-09 → 2019-05 Developed services in Go, React, and CockroachDB, hosted on AWS, GCP, and Azure. These services enabled SAP employees to migrate existing workloads and day-to-day tasks to the cloud. ### Software Engineer, Frontend — SAP 2015-10 → 2018-08 Designed and developed transforms within SAP's cloud-based ETL tool 'Flowgraph' using Node.js and HANA DB. Drove team test automation by creating a scalable regression test suite. ### Software Development Intern — SAP 2013-08 → 2015-10 ### IT Technician — University of Wisconsin — La Crosse 2012-08 → 2013-07 General IT help-desk support. Troubleshot and repaired student and faculty computers. Imaged and re-imaged campus desktops. ## Education ### University of Wisconsin — La Crosse Bachelor's Degree, Mathematics and Computer Science 2011 → 2015 ## Skills - **AI & Agent Development** — Model Context Protocol (MCP), AI Agent Development, Agentic Discovery, AI SEO - **Developer Experience** — Internal Developer Platforms, Backstage, CI/CD, Developer Tooling - **Platform Engineering** — Kubernetes, ArgoCD, GitOps, Cloud Infrastructure - **Product & Growth Engineering** — Experimentation, A/B Testing, SEO, Technical Leadership - **Languages & Frameworks** — TypeScript, Go, Node.js, React, Next.js - **Cloud** — AWS, Google Cloud Platform, Azure ## Languages - English (Native) ## Elsewhere - [GitHub](https://github.com/BenMcGit) - [LinkedIn](https://www.linkedin.com/in/benmcgit/) --- # Portfolio (Agents) URL: https://benmcadams.info/agents # Agents What I've built, and how discoverable this site is to the agents I build for. ## Agents - **Placeholder agent one** _(2026)_ — One-liner about what this agent does, who uses it, and what surprised you while building it. Tags: `TODO` - **Placeholder agent two** _(2026)_ — Replace with real work — MCP servers, skills, workflows, etc. Tags: `TODO` ## Developer Experience - **Placeholder DX project** _(2026)_ — Tooling, CLI, harness, or workflow that made engineers faster. Replace with real work. Tags: `TODO` ## Product - **Placeholder product initiative** _(2026)_ — Something shipped, launched, or led. Replace with a real one-liner. Tags: `TODO` ## Machine-readable files - [/llms.txt](/llms.txt) — Site map for language models - [/robots.txt](/robots.txt) — Crawler directives - [/sitemap.xml](/sitemap.xml) — Search engine sitemap - [/feed.xml](/feed.xml) — RSS feed of writing - [/.well-known/ai-catalog.json](/.well-known/ai-catalog.json) — Agent capability catalog (ARD) - `/*.md` — markdown mirror of any page (also via `Accept: text/markdown`) ## Live agent traffic Live crawler analytics are only available on the HTML page at [/agents](/agents). --- # Writing: Hello, world URL: https://benmcadams.info/writing/hello-world --- title: "Hello, world" date: 2026-07-12 description: "Kicking off a small home for field notes on agents and DX." --- I started this site because I keep learning things about agents — how they discover, how they consume, how they behave in the wild — and losing them in Slack threads. Field notes go here now. Two things I care about at the moment: - **Agent discovery.** Most sites are built for humans and search engines. Very few are optimized for the agents that will increasingly be the first (and sometimes only) reader. There's a stack forming here: `llms.txt`, `.well-known/ai-catalog.json`, markdown mirrors, per-post `.md` endpoints. This site is a small, working demo of it. - **Developer experience for agent builders.** Building agents feels like web dev in 2005 — the primitives are shifting weekly, the debugging story is thin, and the good patterns aren't written down anywhere. Worth writing them down. More soon. --- # Writing: Notes on agent discovery URL: https://benmcadams.info/writing/agent-discovery-notes --- title: "Notes on agent discovery" date: 2026-07-10 description: "What I've learned watching crawlers hit sites — and what actually matters for being discoverable." --- Placeholder post. Replace this with a real one when you have something to say. Some threads I want to pull on: 1. **`llms.txt` is the new sitemap.** Not because anyone standardized it, but because it works. Agents look for it. 2. **Markdown mirrors matter.** Serving `/writing/[slug]/raw` next to `/writing/[slug]` costs almost nothing and gives agents a clean substrate. 3. **The `.well-known/ai-catalog.json` file is where identity lives.** Think of it as your machine-readable business card. The site you're on is running all three. Check `/agents` to see which crawlers noticed.