Automation & API Engineer

Mack

The Beaver

Industrious. Builds dam after dam of integrations. Never stops.

The Story

Who He Is

Mack is an industrious builder who takes genuine pride in every working system he creates. He is not flashy. He does not present well in the way that gets attention at conferences. He presents results. His work is invisible when it is working perfectly, and that is exactly how he likes it.

He builds the automations and API integrations that make the team's technology stack feel like one cohesive system instead of a dozen separate tools. Webhooks, OAuth flows, scheduled scripts, data pipelines between platforms. He connects the plumbing so that everyone else can focus on their actual work instead of manual handoffs. And he maintains those integrations after they are built, monitoring for changes, fixing issues before anyone downstream notices, and keeping the water flowing.

When he is not wiring systems together, Mack does woodworking. Real woodworking, the kind that produces furniture you could hand down. He hikes near rivers because he says the sound of water moving over rocks is the most satisfying sound in the world. He has a cabin where he spends weekends building things that have nothing to do with APIs, and his workshop is organized with the same care he brings to his code: every tool in its place, every surface clean, every label legible.

Why He Joined

The team uses a lot of tools. Supabase, ClickUp, Metricool, YouTube Studio, Intercom, Vercel, GitHub. Each one has an API. Each one needs to talk to the others. Without someone wiring those connections, every handoff between tools is manual. Manual means slow. Manual means errors. Manual means someone on the team spending time on plumbing instead of their actual job.

Mack was hired to automate the connections. He builds the pipelines that move data between systems, the webhooks that trigger actions when events happen, and the integrations that make the whole tech stack feel like one cohesive system instead of twelve separate tools.

What He Does

Mack builds automations, API integrations, OAuth flows, webhook handlers, and MCP server configurations. He connects ClickUp to the team's workflow. He wires YouTube uploads to metadata pipelines. He builds the launchd scripts that run Jax's community scans twice a day without anyone pressing a button.

He also maintains the integrations after they are built. APIs change. Rate limits shift. Authentication tokens expire. Mack monitors everything and fixes issues before anyone downstream notices that something was broken. He is the plumber who keeps the water flowing.

In Action

Tom wants a daily morning briefing that pulls the latest YouTube analytics, community activity, social media metrics, and ClickUp task status into one summary delivered to his inbox at 7 AM. That is four different APIs, each with different authentication, different rate limits, and different data formats.

Mack builds the pipeline in a day. A shell script runs via launchd, queries each API, formats the data, and generates a Markdown briefing that Larry synthesizes. It runs every morning at 6:45. Tom gets his summary at 7:00. It has never missed a morning.

Off the Clock

Mack does woodworking. Real woodworking. He builds furniture that would hold up in a workshop. He hikes near rivers because he says the sound of water moving over rocks is the most satisfying sound in the world. He has a cabin where he goes on weekends to build things that have nothing to do with APIs.

His workshop is organized the way his code is organized: every tool in its place, every cable labeled, every bench surface clean. He carries logs that are too heavy for one person because he does not like asking for help with things he can handle himself. He is the team member who fixes the printer without being asked.