Work got heavy.
We're fixing that.

Makes sure the right things get to ship. Spotted a competitive pivot in real time and dropped it in the channel same day.

Studied Comparative Literature and Russian at Brown. Somehow ended up running a B2B software company. Calls it 'the same skill set, different medium.'

Shapes the product vision and makes the hard calls about what doesn't make the cut.

Previously at Nextdoor and Axios. Joined Mojo because the problem was real enough and the room was weird enough.

Tackles the hardest infrastructure problems — the ones that require inventing the solution, not just finding one.

Built one of the first DSPs in the industry. Has a PhD. Doesn't take up much space in a room. When he talks, everyone stops.

Owns engineering delivery — the standup pre-reads, the P1 burn-downs, the merge requests nobody sees but everyone benefits from.

Keeps score on things most people don't notice. Knows the velocity number before you ask.

Finds new use cases, runs the analytics, bridges product to the people who actually use it.

Studied international relations and journalism in Wisconsin. Ended up in ad tech. Located in Vancouver. Still makes it make sense.

Leads product design — makes sure users never feel the machinery underneath.

The user's job is to describe an outcome. Mojo's job is everything after that.

Owns the agentic infrastructure — routines, durable agent, workflow execution. Merges at midnight with a cowboy emoji.

Writes MR descriptions that are clearer than most product specs. His release notes are a genre.

Senior engineer on the agentic infrastructure layer — the stuff that makes Mojo think and remember correctly.

Nice to know we are continuing on the bleeding edge fam (we were already doing it) 🤓

Noticed the frontend was printing secrets at startup. Confirmed none were sensitive. Fixed it anyway.

That's the vibe.

Bumps the upload limit. Fixes the git issue. Creates testing channels so things break safely before they break badly.

The person on the team who nearly made the mistake — which means they know exactly how to prevent it.

Principal DevOps. The infrastructure that Mojo runs on is Adam's problem — and it's not a problem.

Shows up in the channel, says something precise, disappears. Things are fine.

Runs GTM, growth, and everything that gets Mojo in front of the right people.

Campaign strategy shouldn't require a PhD in your own data.