Andrew Byrd
Brief Resume Email me

Product engineer in Raleigh, North Carolina

AndrewByrd

I take ideas from a working prototype to deployed software: the interface people use, the services and data behind it, and the tools agents use to work with it.

An exploded drawing of a product in four layers: interface, services and MCP, data, and operations. People connect to the interface and agents connect to the services. D Operations Deploys, monitoring, a home lab C Data PostgreSQL, Prisma, analytics B Services & MCP APIs, OAuth scopes, MCP tools agents A Interface React, Next.js, accessibility people
Drawing Selected work, and what I build at home
Currently Senior Frontend Engineer, Pendo
Drawn by A. Byrd
Checked by
Revised October 2026

Products I designed, built, and still run

All three are live on massivenerds.com. I designed each one, wrote the frontend and backend, deployed it, and kept improving it after people started using it.

An agent connects to the Soma app over MCP with OAuth. It can read training history and readiness and write plans, but cannot log sets or edit history. Codex or Claude agent MCP over OAuth reads history and readiness, writes plans can't log sets or edit history 82 readiness Today's plan one person's data, scoped by OAuth
1Agent handoff in SomaNot to scale

Soma

A workout tracker with an AI workout builder and an OAuth-protected MCP server. Agents read my training data and create plans. I open those plans in the app, start a session, and log what I actually do.

My roleProduct design and full-stack development
Built withNext.js, TypeScript, Prisma, PostgreSQL
Agent and AI workMCP, OAuth scopes, structured model output
Story: Export the retro board as CSV Try a round

Pick a card to estimate the story. Your teammates will vote too.

Your card

Planning Poker

Real-time sprint estimation for Agile teams. Create a room and share the link. Everyone votes on story points privately, then the cards flip together, so the first number spoken doesn't anchor the rest of the team. Dev teams at several companies used it for years in their Scrum planning sessions.

My roleDesign and full-stack development
Running sinceOctober 2020
Built withReact, Socket.IO, Express on Fly.io
FeaturesFibonacci voting, moderators, a simultaneous reveal, and a celebration when everyone agrees
A retrospective board with three columns: went well, to improve, and actions. Teammates' cursors show live collaboration. Sprint retro 5 online Went well To improve Actions 3 typing
2A RetroMatic board, mid-retroNot to scale

RetroMatic

A real-time retrospective board for distributed teams. Everyone adds what went well, what to improve, and the actions to take, and the whole team sees each card the moment it's written. At its peak, more than 50 people used it every week.

My roleDesign and full-stack development
Running sinceSeptember 2017
Built withAngular, Firebase Realtime Database
UsageMore than 50 weekly active users at its peak

Used by teams at

  • Blackboard
  • BB&T
  • Cengage
  • Citrix
  • Dude Solutions
  • ImageQuix
  • Live Oak Bank
  • PayScale
  • Pendo
  • Skillsoft
  • thinQ
  • UserVoice

Making the connections work at Pendo

I build interfaces and integration systems, and I help explore how AI agents fit into everyday engineering, from investigation to reviewed, tested changes.

Engineering with AI agents

Use AI agents to plan, implement, review, and validate production work, and check their output myself. Led an engineering session on this workflow, including how to steer agents and use Codex harness features.

1

Data Sync to Snowflake

Build Pendo Data Sync's frontend as the integrations team's lead frontend engineer, including the direct connection to Snowflake. Make backend changes when needed.

About the product
2

Integrations in Japan

Drove the migration and deployment work that brought Pendo's Tray-powered integrations to Japan, after earlier setting up Tray environments for other regions.

Launch announcement
3

HubSpot integration reliability

Diagnosed and fixed a HubSpot sync problem that consumed excess Tray tasks. Corrected the sync's behavior and reduced its task usage.

About the product

Building for agents, and with them

There are three different jobs here: giving agents an interface they can use, putting a model inside the product, and using coding agents to do the engineering. The notes below are keyed to the drawing.

People use the product through its interface. Agents use it through scoped MCP tools (note 1). A model runs inside the product (note 2). I build the product with Claude Code and Codex (note 3). People interface Product model Agents MCP tools, scoped 1 2 Me, with Claude Code and Codex 3
1

Give agents useful tools

Soma exposes scoped MCP tools for reading training history and creating workout plans. Codex and Claude work with the same product data that powers the app.

2

Make model output usable

Soma's AI builder turns training context into a structured proposal. Application code validates it, and the user reviews and accepts it before it becomes a plan.

3

Keep ownership of the result

I use Claude Code, Codex, and Cursor for scoped engineering work, then check the code, the tests, and the product behavior myself.

Toolkit: MCP, model integration, TypeScript, React and Next.js, PostgreSQL, Claude Code and Codex

Seventeen years, measured

I started in data integration and production support. Since then I've spent my career making complicated software easier to use.

  1. 4 yr 2009–2013 Blackboard Connect Data Integration Analyst, then Production Support Engineer
  2. 3 yr 2013–2016 Citrix Software Engineer 1, then Software Engineer 2
  3. 2 yr 2016–2018 Dude Solutions Senior Software Engineer III
  4. 2 yr 8 mo 2019–2021 PayScale Senior Software Engineer
  5. 5 yr, ongoing 2021–now Pendo.io Senior Frontend Engineer

Off the clock

I'm a dad, and most of what I build outside work is for the people at home: my kids, their friends, and occasionally the dog. It all runs on hardware I put together myself.

Command Block on a phone: a server switcher, six large buttons (To Base, Always day, Find village, plus 10 minutes, Megaphone, Give kit), and a command history. Command Block Survival is live To Base Always day Find village +10 min Megaphone Give kit History
3Command Block, phone viewNot to scale

My toughest users

My kids and their friends play on three Minecraft servers I run at home. Their feature requests arrive loudly, in person, and without a ticket. Command Block is how I keep up.

Request log
RequestedShipped
"Can you bring me to where they are?"Teleports to other players, saved places like Base, or coordinates
"Make it daytime. Forever."An always-day toggle, plus time and weather controls
"Where's the nearest village?"A structure finder that can hop onward to find another
"Five more minutes!"Play timers with warnings and a +10 button
"Is the server even on?"servers.massivenerds.com

Command Block is a phone-first web app written in plain Node and vanilla JavaScript, with no dependencies. It sends commands to the servers over RCON and sits behind Cloudflare Zero Trust, so only I can use it.

The public servers page shows which world is live and where the players are gathered around a 3D pixel campfire. Their name tags light up when they're online. It also lists every mod and links the modpacks and a live map of each world.

Traffic from the internet reaches the home NAS only through Cloudflare Tunnel and Zero Trust. The NAS is a Synology DS920+ with four drive bays. Internet Cloudflare Tunnel Zero Trust DS920+ 4 bays, SHR, about 10.9 TB usable
4Home lab, how traffic gets inNot to scale

The server in the closet

A Synology NAS in my network closet runs everything I self-host. Gitea holds my source code, including this site. Immich keeps the family photos. It also runs the three Minecraft servers, their live maps, and Command Block.

Public pages reach it through Cloudflare Tunnel, and private tools sit behind Zero Trust sign-in, so nothing on the home network is exposed directly. The closet itself is a slower project: turning a tangle of cables into something r/homelab would approve of.

HardwareSynology DS920+, 8 GB RAM, SSD cache
StorageFour drives in SHR, about 10.9 TB usable
RunsGitea, Immich, three Minecraft servers, world maps, Command Block, uptime monitoring
AccessCloudflare Tunnel, Zero Trust, Tailscale
Side view of the desktop with labeled parts: processor, motherboard, memory, graphics card, storage, liquid cooler, power supply, and case. H F B A C D E G
5The desktop, side elevationNot to scale

The desktop

I like building PCs for the same reason I like building software: choose the parts, route everything cleanly, then confirm the memory actually runs at its rated speed. This AM5 build is my daily machine. Its RTX 3080 recently made way for a Radeon RX 9070 XT.

Bill of materials. Point at or focus a row to pull that part out of the drawing.
KeyPartModel
AProcessorAMD Ryzen 7 9800X3D
BMotherboardASUS ROG Strix X870E-E Gaming WiFi
CMemory64 GB DDR5-6000 CL36, G.Skill Ripjaws S5
DGraphicsGigabyte Radeon RX 9070 XT
EStorageSamsung 990 Pro 1 TB, 960 EVO 250 GB, WD Red 8 TB
FCoolingCooler Master 360 mm liquid cooler
GPowerCorsair RM750x, 750 W Gold
HCaseLian Li Lancool 217, black and walnut
A line drawing of Luna, a French Bulldog with broad bat ears, a wide face, and a short muzzle.
6Luna, front elevation1:1, roughly

Luna, site supervisor

Luna is a lilac French Bulldog, born September 25, 2025. She joined the family that December and has signed off on every sheet in this set, mostly from the floor.

BreedFrench Bulldog
ColorLilac
ResponsibilitiesFloor-level inspection, napping near the desk

An engineer who still likes to tinker

I'm based in the Raleigh area and work on frontend and integration experiences at Pendo. Outside work, I build software for my own ideas, experiment with agents and new models, and keep the home lab running. I like work where thoughtful design and reliable engineering meet.

  1. Find the actual problemStart with the people and workflow behind the request. Good interfaces come from getting the model right.
  2. Build for the long runMake the system understandable, accessible, and fast enough to stay useful as it grows.
  3. Ship and learnWork across design and engineering, put real software in people's hands, and improve it from evidence.

Have something in mind? Let's talk it through.

Revisions to this site
RevDateDescription
C2026-10Blueprint edition
B2026-09River edition
A2026-09Editorial edition