Senior engineer and tech leadChicagoOpen to remote roles

I build AI agents and the tools around them. One of them is running in my apartment right now.

– requests from my AI apps this week, – answered without an error. The last one came in –.

Now · Nov 2026 I wrapped up four years at Beacons AI in October. This month I split my Home Server into separate memory, mail and ops servers behind one gateway. Next I'm looking for a senior engineer or tech lead role on AI agents or developer tooling.

About. Short version or long.

I'm a senior engineer and tech lead. For the last four years I worked at Beacons AI, most recently on Beam, the creator AI agent, which grew about 12× in one summer, and on the Beacons MCP, which I built from scratch so Claude and ChatGPT can work with Beacons directly. Before that I led and then managed a frontend team at Riviera Partners. TypeScript by default.

Selected work. Agents in production, and the tools I build to work alongside them.

  1. Beacons AI · 2025–26

    Beam

    The creator AI agent. I built its link-in-bio editing tools, and one parameterized analytics tool in place of many per-metric ones. Showing the agent a rendered view of the page, not just its style settings, made its edits much better.

    About 1,000 → 12,495 weekly active creators over summer 2026

    12,495~1,000
  2. Beacons AI · 2025–26

    Beacons MCP

    Built from scratch, so any Beacons user can work with their own data in Claude and ChatGPT. It shares its tools with Beam, so the agent and the MCP stay at parity.

    Built 0 → 1 · works in Claude and ChatGPT

  3. Side project · running now

    Home Server

    One memory shared by every AI app I use, served from a 2018 MacBook Pro. One gateway and one sign-in in front of separate memory, mail and ops servers, with zero open ports and deploys by asking in chat.

    Read the deep dive

  4. Automation

    clautopilot

    Headless Claude Code automation that takes a ticket to a pull request, then keeps answering review comments until it's ready to merge. Works across GitHub, GitLab and Linear.

    ticket → branch → pull request → review answered → ready to merge

  5. Agent setup as code

    dotclaude

    My agent setup as code: one operating brief for every agent, hooks for guard rails and auto-sync, a memory that's git-synced across machines, configs for Claude Code, Cursor, Codex and Kilo, and evals that check the agents actually use it.

    CLAUDE.md · hooks/ · memory/ · harness/ · evals/

Where I've worked. Eight years shipping web products, four of them leading or managing engineers.

  1. 2022 – 2026

    Beacons AI remote

    Senior Software Engineer and Tech LeadApr 2025 – Oct 2026

    Helped grow Beam, the creator AI agent, about 12× in weekly active creators. Built the Beacons MCP from scratch and shared its tools with Beam to keep the two at parity. Tech lead for Beacons for Brands: architecture, tickets, code review, and delegating to engineers and AI agents.

    Software EngineerJun 2022 – Apr 2025

    Built the React and TypeScript frontend and Python APIs for branded email, which grew adoption 750%. Ran onboarding and checkout A/B tests with LaunchDarkly and Amplitude.

  2. 2018 – 2022

    Riviera Partners San Francisco

    Engineering ManagerSep 2021 – May 2022

    Managed three frontend engineers on the core recruiting app, reporting to the CTO.

    Engineering Team LeadJan 2020 – Aug 2021

    Led the team and architected its work, including a real-time sourcing interface that points recruiters to unreviewed candidates.

    Software EngineerAug 2018 – Dec 2019

    React and Ruby across the recruiting app, including a client-facing KPI dashboard.

  3. 2018

    University of Michigan

    B.S.E. Computer Science
Full history on LinkedIn

Hiring for AI agents or developer tooling? Let's talk.